Re: DHCPv6 client in Windows 10 broken after anniversary update

[Mikael Abrahamsson]

So I did some more investigation. I had missed that I needed to use 
/renew6 and /release6 before.


Now I have 10 minute lease time.

5 minutes into the lease time, I can /renew6 the lease successfully and 
get 10 more minutes leasetime.


around 2-3 minutes before the lease-time expires I see that Win10 has 
marked the IA_NA as (deprecated), I try to do "/renew6" I get the 
following error:


"An error has occured while renewing interface Ethernet: The semaphore 
timeout period has expired".


This renew fails. If I now ctrl-c this /renew6 and run /renew6 again, the 
renew succeeds and the address is back again as (preferred) and the lease 
time is 10 minutes.


I also have a Ubuntu 16.04 box that won't keep its lease either... so I 
don't know what's going on. Will look further.


Harald, what DHCPv6 server are you using?

--
Mikael Abrahamssonemail: swm...@swm.pp.se

Re: DHCPv6 client in Windows 10 broken after anniversary update

[Harald F. Karlsen]

On 10.10.2016 15:29, Mikael Abrahamsson wrote:


So I did some more investigation. I had missed that I needed to use 
/renew6 and /release6 before.


Now I have 10 minute lease time.

5 minutes into the lease time, I can /renew6 the lease successfully 
and get 10 more minutes leasetime.


around 2-3 minutes before the lease-time expires I see that Win10 has 
marked the IA_NA as (deprecated), I try to do "/renew6" I get the 
following error:


"An error has occured while renewing interface Ethernet: The semaphore 
timeout period has expired".


This renew fails. If I now ctrl-c this /renew6 and run /renew6 again, 
the renew succeeds and the address is back again as (preferred) and 
the lease time is 10 minutes.

These are the exact same obervations I have done so far.


I also have a Ubuntu 16.04 box that won't keep its lease either... so 
I don't know what's going on. Will look further.


Harald, what DHCPv6 server are you using?


I run my DHCPv6 server on a Juniper SRX220 with Junos 12.1X46-D55.

--
Harald

Re: DHCPv6 client in Windows 10 broken after anniversary update

[Henri Wahl]

Hi,

same here on a Windows 10 Pro 1607 with stateful DHCPv6. Only takes
addresses when being forced by /renew6 but seems to forget them soon too.
I first suspected a problem with the DHCPv6 server dhcpy6d but when I
read you mails this seems to be a more global problem.

Regards

-- 
Henri Wahl

IT Department
Leibniz-Institut fuer Festkoerper- u.
Werkstoffforschung Dresden

tel: +49 (3 51) 46 59 - 797
email: h.w...@ifw-dresden.de
https://www.ifw-dresden.de

Nagios status monitor Nagstamon: https://nagstamon.ifw-dresden.de

DHCPv6 server dhcpy6d: https://dhcpy6d.ifw-dresden.de

S/MIME: https://nagstamon.ifw-dresden.de/pubkeys/smime.pem
PGP: https://nagstamon.ifw-dresden.de/pubkeys/pgp.asc

IFW Dresden e.V., Helmholtzstrasse 20, D-01069 Dresden
VR Dresden Nr. 1369
Vorstand: Prof. Dr. Burkard Hillebrands, Dr. Doreen Kirmse


0x83E6CEC2.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: DHCPv6 client in Windows 10 broken after anniversary update

[Michael Oghia]

Hi everyone,

Does anyone know if Microsoft is aware of this issue? Perhaps it can be
forwarded to someone who can pass it along to the engineers.

Best,
-Michael


On Mon, Oct 10, 2016 at 11:28 AM, Trevor Warwick  wrote:

> I've think I've also seen this. To work around a bug in my Ubiquiti router
> at home, I can't use SLAAC, so need to rely on DHCPv6 for address
> assignment.  This weekend, a recently upgraded Windows 10 Anniversary
> machine wasn't successfully getting an IPv6 address. Looking at it with
> wireshark,IIRC, the client sent a Solicit, the server sent an Advertise,
> but there was no Request from the client after that.
>
> On 10 October 2016 at 09:14, Harald F. Karlsen  wrote:
>
>> Hi,
>>
>> It seems like Microsoft somehow broke DHCPv6 client functionality in the
>> Windows 10 anniversary update and now neither stateful nor stateless DHCPv6
>> functionality works unless you manually issue "ipconfig /renew6" (for
>> stateful DHCPv6 this will only give you IPv6-connectivity untill the lease
>> expires).
>>
>> This is generally not a big issue for dual-stacked residential customers
>> as most CPEs does SLAAC on the LAN-side, but the Win10 clients will not
>> recieve DNS from DHCP if the CPE is configured for that. For enterprise
>> networks on the other hand this can be a big issue. Especially when running
>> FHS and no SLAAC.
>>
>> Have anyone on the list experienced issues with this yet? If so, have you
>> contacted Microsoft and what did they say? I've found reports on this issue
>> dating back from early august so it's strange that Microsoft have not yet
>> issued a fix for it.
>>
>> --
>> Harald
>>
>
>

DHCPv6 client in Windows 10 broken after anniversary update

[Harald F. Karlsen]

Hi,

It seems like Microsoft somehow broke DHCPv6 client functionality in the 
Windows 10 anniversary update and now neither stateful nor stateless 
DHCPv6 functionality works unless you manually issue "ipconfig /renew6" 
(for stateful DHCPv6 this will only give you IPv6-connectivity untill 
the lease expires).


This is generally not a big issue for dual-stacked residential customers 
as most CPEs does SLAAC on the LAN-side, but the Win10 clients will not 
recieve DNS from DHCP if the CPE is configured for that. For enterprise 
networks on the other hand this can be a big issue. Especially when 
running FHS and no SLAAC.


Have anyone on the list experienced issues with this yet? If so, have 
you contacted Microsoft and what did they say? I've found reports on 
this issue dating back from early august so it's strange that Microsoft 
have not yet issued a fix for it.


--
Harald

Re: DHCPv6 client in Windows 10 broken after anniversary update

[Thomas Schäfer]

Am 10.10.2016 um 10:14 schrieb Harald F. Karlsen:

Hi,



Have anyone on the list experienced issues with this yet? If so, have
you contacted Microsoft and what did they say? I've found reports on
this issue dating back from early august so it's strange that Microsoft
have not yet issued a fix for it.




I can confirm the behavior for stateless DHCP with missing IPv6-DNS-entries.
After "ipconfig /renew6" they appear.

Regards,
Thomas




--

There’s no place like ::1

Thomas Schäfer (Systemverwaltung)
Ludwig-Maximilians-Universität
Centrum für Informations- und Sprachverarbeitung
Oettingenstraße 67 Raum C109
80538 München ☎ +49/89/2180-9706  ℻ +49/89/2180-9701

Re: DHCPv6 client in Windows 10 broken after anniversary update

[Harald F. Karlsen]

On 10.10.2016 10:47, Thomas Schäfer wrote:

A Question:

Have you a pure Windows?
I have seen, there is third party network management software on my 
device. (Fujitsu Plugfree Network).
I experience the issue on three different devices I tested on (one of 
which is a completely original Microsoft Surface Pro 3) so I highly 
doubt it's related to any third party software.


--
Harald

SV: BBWF Beer meetup

[erik.taraldsen]

For those not yet killed, I've gotten this suggestion off-list
http://www.foxbars.com/foxexcel/excel-bars/

"... our Warehouse Bar is the go to place for post-exhibition goers."

-Erik



Fra: Gert Doering 
Sendt: 8. oktober 2016 12:22
Til: Eric Wisner
Kopi: Anfinsen, Ragnar; Taraldsen Erik; ipv6-ops@lists.cluenet.de
Emne: Re: BBWF Beer meetup

Hi,

On Sat, Oct 08, 2016 at 09:17:53PM +1100, Eric Wisner wrote:
> KILL ME

I take the beer was good, and lots of it?  :-)

Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?

SpaceNet AGVorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14  Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444   USt-IdNr.: DE813185279