[Dnsmasq-discuss] IPv6 stateless and stateful together?

Simon Kelley simon at thekelleys.org.uk
Wed Apr 24 09:49:40 BST 2013

On 23/04/13 14:50, Conrad Kostecki wrote:
> Am 23.04.2013 11:03, schrieb Simon Kelley:
>> On 22/04/13 21:46, Conrad Kostecki wrote:
>>> Hi,
>>> i am running with DNSMasq 2.66 so far without any problems DHCP and
>>> DHCPv6. DHCPv6 is only stateful at the moment in my LAN.
>>> I've now some older clients (Windows XP, Android), which do not support
>>> stateful but stateless. But how do I configure this? Can DNSMasq serve
>>> both options? Do I have to run radvd additionally?
>> There are two functions involved. Giving IPv6 addresses to machines, and
>> telling them of other configuration, such is DNS servers, hostnames, NTP
>> servers, etc.
>> Giving addresses to machines happens either by using manually configured
>> addresses, SLAAC (stateless autoconfiguration - NOT THE SAME as
>> stateless DHCP) or stateful DHCP.
>> Providing other configuration can again be done manually, via SLAAC (to
>> a limited extent) or via DHCPv6 - either stateless or stateful.
>> A DHCPv6 server which is stateful is always also capable of being
>> stateless.
>> Android clients (at least the ones I have) don't support DHCPv6 at all.
>> They get IPv6 addresses and limited configuration via SLAAC. You can add
>> a router advertisement server to your network to support SLAAC either by
>> running radvd, or by using dnsmasq and configuring it with the some
>> combination of ra-only, slaac, ra-names, ra-stateless in the dhcp-range
>> configuration.
>> If you already have DHCPv6 configured, just added the slaac keyword to
>> the existing dhcp-range is probably all you need.
>> Cheers,
>> Simon.
> Hi Simon,
> thanks for you explanation! :) Setting slaac works now for me.
> Just a side question, can I ignore the second ip leased by slaac on a
> dhcpv6 client?

Yes. the natural state for IPv6 is for clients to have multiple 
addresses. The only functional difference between the two addresses is 
that the DHCPv6 one will be in the DNS, whilst the SLAAC one won't. If 
you want to remedy that one, configure the dnsmasq dhcp-range with 
ra-names as will as slaac.



More information about the Dnsmasq-discuss mailing list