Am 02.10.2012 23:09, schrieb Simon Kelley: > On 02/10/12 21:53, e9hack wrote: >> Am 02.10.2012 21:52, schrieb Simon Kelley: >>> On 02/10/12 14:56, Dan Williams wrote: >>>> So you really want to reconfigure either dnsmasq or radvd to set the >>>> "M" (Managed) flag, which will tell the clients to get their address >>>> from DHCPv6, not generate one from the RA prefix option. >>> >>> Dan is right, and the way to do this in dnsmasq is to define a dhcp-range, >>> and set the >>> global enable-ra flag. That will send RA (for the default route) with the M >>> flag set (no >>> SLAAC address). If you want SLAAC addresses _as_well_ as DHCPv6 assigned >>> ones, add the >>> "slaac" keyword to the dhcp-range. That clears the M flag. >> >> That's wrong. The M flag is for DHCPv6 only. It says nothing about SLAAC. >> SLAAC is >> available, if a prefix is advertise. >> > > I'm going from memory of experiments months ago, but I'm sure that the Linux > kernel IPv6 > autoconfiguration code, at least, does not assign SLAAC addresses if it gets > RAs with the > M bit set.
I'm using radvd and dnsmasq. Dnsmasq is used for DHCPv6 but not for RA. If I disable the M flag at the radvd side, linux and windows 7 clients doesn't ask for a DHCPv6 lease, but they are using a SLAAC address. If I enable the M flag, both clients are using the SLAAC address and asking for a DHCPv6 lease. I'm using DHCPv6 (and a ULA prefix with RA) to configure site-local address. RA is used for global addresses to access the internet over a 6to4 auto tunnel with a prefix of 2002:aaaa:bbbb::/64. Regards, Hartmut _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss