[Dnsmasq-discuss] Win10 Dhcpv6 issue?

[Xander Victory]

I'm having some trouble getting windows 10 to keep its v6 lease, it seem
to fail to renew.

From packet sniffing it seems to just be ignoring DNSMasq's replies to
the renew packets, and then falls back to soliciting continuously,
despite being replied to.

I've attached the pcap files (hopefully). Shows that it acquires it on
reboot, but fails after the lease time is (about to?) expire - set at 2
hours because of issues with the xbox one getting a new address each
boot (you can see in the 2nd pcap that it renews its address just fine).

Is windows 10 borked or is it something with my config? I'm unsure if
this is a recent development or not to be honest.

Not exactly related, but I've noticed that DNSMasq sends its v6 packets
(router advertisements and dhcpv6) from the full link local address,
even though the default address is a manually configured fe80::1

relevant config:

dhcp-host=id:00:01:00:01:1a:1b:af:8c:bc:5f:f4:d8:41:bc,[::3],bc:5f:f4:d8:41:bc,10.1.2.6,xander
dhcp-range=br0,10.1.2.100,10.1.2.249,255.255.255.0,12h
dhcp-range=br0,2001:44b8:610e:3c00::4,2001:44b8:610e:3c00::ffff,2h
enable-ra

[Xander Victory]

No, dnsmasq was one version below current, even updating to current (gentoo
patches) nothing changed

Hi, Xander
Not exactly related to Windows 10 ignorance, but according pcap, dnsmasq
doesn’t reply to REBIND requests.
So, you version seems older than 2.72 where it was fixed, is it?
If so, it’s desirable to update to the current latest 2.76.
Best Regards, Vladislav Grishenko
Victory
*Sent:* Friday, June 24, 2016 4:21 PM
*Subject:* [Dnsmasq-discuss] Win10 Dhcpv6 issue?
I'm having some trouble getting windows 10 to keep its v6 lease, it seem
to fail to renew.
From packet sniffing it seems to just be ignoring DNSMasq's replies to the
renew packets, and then falls back to soliciting continuously, despite
being replied to.
I've attached the pcap files (hopefully). Shows that it acquires it on
reboot, but fails after the lease time is (about to?) expire - set at 2
hours because of issues with the xbox one getting a new address each boot
(you can see in the 2nd pcap that it renews its address just fine).
Is windows 10 borked or is it something with my config? I'm unsure if this
is a recent development or not to be honest.
Not exactly related, but I've noticed that DNSMasq sends its v6 packets
(router advertisements and dhcpv6) from the full link local address, even
though the default address is a manually configured fe80::1
dhcp-host=id:00:01:00:01:1a:1b:af:8c:bc:5f:f4:d8:41:bc,[::3],bc:5f:f4:d8:41:bc,10.1.2.6,xander
dhcp-range=br0,10.1.2.100,10.1.2.249,255.255.255.0,12h
dhcp-range=br0,2001:44b8:610e:3c00::4,2001:44b8:610e:3c00::ffff,2h
enable-ra

[Xander Victory]

To clarify , dnsmasq version is 2.76.

Dnsmasq version 2.76 Copyright (c) 2000-2016 Simon Kelley
Compile time options: IPv6 GNU-getopt no-DBus i18n IDN DHCP DHCPv6
no-Lua no-TFTP no-conntrack ipset no-auth no-DNSSEC loop-detect inotify

Win10 seems to try to fall back to Rebind anyway, it tries Renew a few
times first. It just doesnt seem to like the reply like the xbox does
[::b0c5]

My bad, it was wrong assumption, sorry.
Just checked, dnsmasq doesn’t really support REBIND at all at the
moment, fix in 2.72 actually fixed nothing.
Best Regards, Vladislav Grishenko
*Sent:* Saturday, June 25, 2016 5:21 PM
*Subject:* RE: [Dnsmasq-discuss] Win10 Dhcpv6 issue?
No, dnsmasq was one version below current, even updating to current
(gentoo patches) nothing changed
Hi, Xander
Not exactly related to Windows 10 ignorance, but according pcap,
dnsmasq doesn’t reply to REBIND requests.
So, you version seems older than 2.72 where it was fixed, is it?
If so, it’s desirable to update to the current latest 2.76.
Best Regards, Vladislav Grishenko
*From:*Dnsmasq-discuss
Behalf Of *Xander Victory
*Sent:* Friday, June 24, 2016 4:21 PM
*Subject:* [Dnsmasq-discuss] Win10 Dhcpv6 issue?
I'm having some trouble getting windows 10 to keep its v6 lease,
it seem to fail to renew.
From packet sniffing it seems to just be ignoring DNSMasq's
replies to the renew packets, and then falls back to soliciting
continuously, despite being replied to.
I've attached the pcap files (hopefully). Shows that it acquires
it on reboot, but fails after the lease time is (about to?) expire
- set at 2 hours because of issues with the xbox one getting a new
address each boot (you can see in the 2nd pcap that it renews its
address just fine).
Is windows 10 borked or is it something with my config? I'm unsure
if this is a recent development or not to be honest.
Not exactly related, but I've noticed that DNSMasq sends its v6
packets (router advertisements and dhcpv6) from the full link
local address, even though the default address is a manually
configured fe80::1
dhcp-host=id:00:01:00:01:1a:1b:af:8c:bc:5f:f4:d8:41:bc,[::3],bc:5f:f4:d8:41:bc,10.1.2.6,xander
dhcp-range=br0,10.1.2.100,10.1.2.249,255.255.255.0,12h
dhcp-range=br0,2001:44b8:610e:3c00::4,2001:44b8:610e:3c00::ffff,2h
enable-ra

[Xander Victory]

This seems to have just been another Windows 10 Stupid (I thought I'd
gotten away with not having any).

I followed this article and deleted both DUID keys in the registry and
it seems to be able to maintain a lease.
https://support.microsoft.com/en-us/kb/2711727

Support page appears to apply to non-updated 7/8/Server 2008R2/Server
2012 too.

My bad, it was wrong assumption, sorry.
Just checked, dnsmasq doesn’t really support REBIND at all at the
moment, fix in 2.72 actually fixed nothing.
Best Regards, Vladislav Grishenko
*Sent:* Saturday, June 25, 2016 5:21 PM
*Subject:* RE: [Dnsmasq-discuss] Win10 Dhcpv6 issue?
No, dnsmasq was one version below current, even updating to current
(gentoo patches) nothing changed
Hi, Xander
Not exactly related to Windows 10 ignorance, but according pcap,
dnsmasq doesn’t reply to REBIND requests.
So, you version seems older than 2.72 where it was fixed, is it?
If so, it’s desirable to update to the current latest 2.76.
Best Regards, Vladislav Grishenko
*From:*Dnsmasq-discuss
Behalf Of *Xander Victory
*Sent:* Friday, June 24, 2016 4:21 PM
*Subject:* [Dnsmasq-discuss] Win10 Dhcpv6 issue?
I'm having some trouble getting windows 10 to keep its v6 lease,
it seem to fail to renew.
From packet sniffing it seems to just be ignoring DNSMasq's
replies to the renew packets, and then falls back to soliciting
continuously, despite being replied to.
I've attached the pcap files (hopefully). Shows that it acquires
it on reboot, but fails after the lease time is (about to?) expire
- set at 2 hours because of issues with the xbox one getting a new
address each boot (you can see in the 2nd pcap that it renews its
address just fine).
Is windows 10 borked or is it something with my config? I'm unsure
if this is a recent development or not to be honest.
Not exactly related, but I've noticed that DNSMasq sends its v6
packets (router advertisements and dhcpv6) from the full link
local address, even though the default address is a manually
configured fe80::1
dhcp-host=id:00:01:00:01:1a:1b:af:8c:bc:5f:f4:d8:41:bc,[::3],bc:5f:f4:d8:41:bc,10.1.2.6,xander
dhcp-range=br0,10.1.2.100,10.1.2.249,255.255.255.0,12h
dhcp-range=br0,2001:44b8:610e:3c00::4,2001:44b8:610e:3c00::ffff,2h
enable-ra