yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #45437
[Bug 1531093] Re: radvd config should have a prefix section when subnet's ipv6_ra_mode is DHCPV6_STATEFUL
Reviewed: https://review.openstack.org/262962
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=629d86d480c06569ba6bd5d9cd55a543dbf6221b
Submitter: Jenkins
Branch: master
commit 629d86d480c06569ba6bd5d9cd55a543dbf6221b
Author: Wenxin Wang <stieizc.33@xxxxxxxxx>
Date: Sat Jan 2 18:29:21 2016 +0800
radvd prefix configuration for DHCPV6_Stateful RA
When an IPv6 subnet's ipv6_ra_mode is set to DHCPV6_STATEFUL,
the hosts on that subnet rely on router advertisement for the
prefix length. This is important for subnets where the lengths
of the prefixes are not 64.
Closes-Bug: #1531093
Change-Id: Ied8d390a05ee1a2e544e39e887abf11c8a56abc3
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1531093
Title:
radvd config should have a prefix section when subnet's ipv6_ra_mode
is DHCPV6_STATEFUL
Status in neutron:
Fix Released
Bug description:
Currently, when an IPv6 subnet has ipv6_ra_mode set to
DHCPV6_STATEFUL, there will be no section in the relevant radvd config
file about its prefix. However, instances on that subnet still relies
on RA for settings that DHCPv6 does not provide, like prefix length,
and the M bit. As of the prefix length, it seems that currently
neutron assumes a /64 prefix (correct me if I'm wrong), but future
version may need to handle prefixes with different lengths.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1531093/+subscriptions
References