[Dnsmasq-discuss] Win7 does not lease an IPv6-Address

Simon Kelley simon at thekelleys.org.uk
Sat Feb 18 21:54:17 GMT 2012


On 18/02/12 20:36, Conrad Kostecki wrote:
> Am 14.02.2012 22:18, schrieb Simon Kelley:
>> I've just released dnsmasq-2.60test11 available now from
>> [...]
>> Please give it a whirl and let me know hoe it goes.
>>
>> Simon.
>>
>>
>
> Hi guys,
> i also tried to test dnsmasq 2.60test13, but it seems, that my Win7
> workstation does not get any ipv6-address.
>
> I've added these options to my dnsmasq.conf:
> dhcp-range=2a01:AAA:BBB:0::10,2a01:AAA:BBB:0::49,24h
> dhcp-option=option6:dns-server,[2a01:AAA:BBB:0::1]
>
> When now my Win7 workstation tries to get an ipv6 adress, I see this in
> my log:
> Feb 18 21:25:58 [dnsmasq-dhcp] DHCPSOLICIT(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX
> Feb 18 21:25:58 [dnsmasq-dhcp] DHCPADVERTISE(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX 2a01:AAA:BBB::2b
> Feb 18 21:25:59 [dnsmasq-dhcp] DHCPSOLICIT(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX
> Feb 18 21:25:59 [dnsmasq-dhcp] DHCPADVERTISE(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX 2a01:AAA:BBB::2b
> Feb 18 21:26:01 [dnsmasq-dhcp] DHCPSOLICIT(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX
> Feb 18 21:26:01 [dnsmasq-dhcp] DHCPADVERTISE(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX 2a01:AAA:BBB::2b
> Feb 18 21:26:05 [dnsmasq-dhcp] DHCPSOLICIT(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX
> Feb 18 21:26:05 [dnsmasq-dhcp] DHCPADVERTISE(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX 2a01:AAA:BBB::2b
> Feb 18 21:26:13 [dnsmasq-dhcp] DHCPSOLICIT(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX
> Feb 18 21:26:13 [dnsmasq-dhcp] DHCPADVERTISE(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX 2a01:AAA:BBB::2b
> Feb 18 21:26:29 [dnsmasq-dhcp] DHCPSOLICIT(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX
> Feb 18 21:26:29 [dnsmasq-dhcp] DHCPADVERTISE(eth0)
> 00:01:00:01:15:e9:74:8c:XX:XX:XX:XX:XX:XX 2a01:AAA:BBB::2b
>
> After about a minute, Win7 says:The semaphore timeout period has been
> reached. (tried with ipconfig /renew6)
>
> Any ideas, why? Thanks!

Either there's something in the DHCPADVERTISE message that dnsmasq sends 
which win7 doesn't like, so it ignores it, or the ADVERTISE message it 
not getting to the win7 client. (Maybe a firewall problem)

All the testing I've done so far has used Linux clients, so this is not 
totally unexpected. I'll try to get hold of a Win 7 box to work out 
what's going on.


Thanks for taking the time to test.

Simon.




More information about the Dnsmasq-discuss mailing list