On Tue, Oct 2, 2012 at 4:52 PM, Simon Kelley <si...@thekelleys.org.uk> wrote: > On 02/10/12 14:56, Dan Williams wrote: >> >> On Mon, 2012-10-01 at 21:49 +0200, Sean Boran wrote: >>> >>> >>> >>> Perhaps you clients are getting their addresses from router >>> advertisement, and not DHCP. So disable RA first in dnsmasq (and make >>> sure no router or other host is publishing one) >> >> >> You don't want to disable RA, you want to tell clients to use "managed" >> configuration in the RA. If you disable RA, then nothing on that link >> will have a default router and thus no way to get packets to anything >> that's not in the broadcast domain. DHCPv6 does not have any facility >> to provide a "default gateway" like IPv4, since that's precisely the >> functionality of RAs. >> >> 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.
I tried all this, yet it still won't work. It used to work when I used radvd + the WIDE DHCP daemon. I'm at a loss here... Thanks for all the help, though. _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss