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: http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq.conf.example 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. #enable-ra 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.cl...@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@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev