[Dnsmasq-discuss] DHCPv6

[Simon Kelley]

On 08/04/13 19:17, Christof Meerwald wrote:
> On Mon, 08 Apr 2013 14:49:36 +0100, Simon Kelley wrote:
>> On 07/04/13 21:28, Christof Meerwald wrote:
>>> On Fri, 22 Mar 2013 10:02:13 +0000, Simon Kelley wrote:
>>>> http://www.thekelleys.org.uk/dnsmasq/release-candidates/dnsmasq-2.66rc1.tar.gz
>>>>
>>>> For IPv4 users, there are not many changes, but IPv6, and specifically
>>>> DHCPv6, has seen much development. I'd like as many people as possible
>>>> to check out that I've not broken your DHCPv6 installations.
>>>
>>> Brilliant, DHCPv6 is now working fine on my Raspberry Pi - I had
>>> problems with dnsmasq 2.62 not picking up a statically configured IPv6
>>> address, but with 2.66rc1 that's working fine now.
>> Good stuff. I think that DHCPv6 is starting to mature nicely now.
>
> I am afraid I spoke too soon - behaviour seems to be a bit random.
>
> So, my dnsmasq configuration is available at
> http://svn.cmeerw.net/cfg/fruity.cmeerw.net/etc/dnsmasq.conf
>
> What seems to be happening is that only sometimes the statically
> configured IPv6 is returned to that client (in addition to a dynamic
> one). Sometimes (just after startup), only the statically configured
> IPv6 address is returned to that client.
>
>> From the syslog:
>
> Apr  8 06:28:38 localhost dnsmasq-dhcp[1896]: DHCPSOLICIT(eth0)
> 00:01:00:01:18:f3:5c:6c:00:26:9e:38:e5:fb
> Apr  8 06:28:38 localhost dnsmasq-dhcp[1896]: DHCPADVERTISE(eth0)
> 2a01:348:236:feed::da3b 00:01:00:01:18:f3:5c:6c:00:26:9e:38:e5:fb
>
> no ::13 this time, but later:
>
> Apr  8 17:48:18 localhost dnsmasq-dhcp[1896]: DHCPSOLICIT(eth0)
> 00:01:00:01:18:f3:5c:6c:00:26:9e:38:e5:fb
> Apr  8 17:48:18 localhost dnsmasq-dhcp[1896]: DHCPADVERTISE(eth0)
> 2a01:348:236:feed::13 00:01:00:01:18:f3:5c:6c:00:26:9e:38:e5:fb
> Apr  8 17:48:18 localhost dnsmasq-dhcp[1896]: DHCPADVERTISE(eth0)
> 2a01:348:236:feed::da3b 00:01:00:01:18:f3:5c:6c:00:26:9e:38:e5:fb
>
>
> Any ideas?

There's at least one possible explanation that doesn't involve a dnsmasq 
bug, and several that do. The first thing to do is to turn on verbose 
DHCP logging by adding

log-dhcp

to the config. If we can get log dumps of the same events with that 
switched on, it will be a lot easier to see what's going on.


Cheers,

Simon.
>
>
> Christof
>