[openstack-dev] [Neutron][IPv6] Change I5b2313ff: Create a new attribute for subnets, to store v6 dhcp options

Xuhan Peng pengxuhan at gmail.com
Tue Dec 17 15:52:50 UTC 2013

I think slaac was original excluded to make --enable-ra not specified when
only slaac is given to an subnet's dhcp mode.

However, when I checked the example conf file of dnsmasq:


enable-ra is explained as:

# Do router advertisements for all subnets where we're doing DHCPv6
# Unless overriden by ra-stateless, ra-names, et al, the router
# advertisements will have the M and O bits set, so that the clients
# get addresses and configuration from DHCPv6, and the A bit reset, so the
# clients don't use SLAAC addresses.

are we using --enable-ra and ra-stateless, ra-names at the same time correctly?

On Tue, Dec 17, 2013 at 8:27 PM, Shixiong Shang <
sparkofwisdom.cloud at gmail.com> wrote:

> Hi, guys:
> I am reading the code in “constants.py” file as part of "Change I5b2313ff:
> Create a new attribute for subnets, to store v6 dhcp options”. One thing
> captured my eyes is the definition of “RA_MODES”, which excluded “slaac”
> mode. If my understanding of “RA_MODES” is correct, i.e. the modes leverage
> RA, then “slaac” mode should be included. Am I correct?
> Thanks!
> Shixiong
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131217/23cbb02e/attachment.html>

More information about the OpenStack-dev mailing list