Re: DHCPv6 client in Windows 10 broken after anniversary update

[Harald F. Karlsen]

On 10.10.2016 10: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.


If looks like this was finally resolved in the 2017 March cumulative 
update for Windows. I have verified it on Windows 10 Home and Pro, but I 
also got one report claiming it was not resolved in Windows 10 
Enterprise, can someone confirm this?


--
Harald

Re: Rev'ed IETF I-Ds on Security/Privacy of IPv6 addresses

[Fernando Gont]

On 03/15/2017 05:27 AM, Bjørn Mork wrote:
> Fernando Gont  writes:
> 
>> * "IPv6 Address Usage Recommendations" 
>> * "Recommendation on Temporary IPv6 Interface Identifiers"
>> 
> 
> Following arbitrary URLs from an email is considered unwise.  There is
> nothing in those URLs telling me that they are redirected to a site I
> consider safe.

In a sense, I sympathize with your view. These are the expanded URLs:

* "IPv6 Address Usage Recommendations"


* "Recommendation on Temporary IPv6 Interface Identifiers"


Thanks!

Cheers,
-- 
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fingerprint:  31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492