Yesterday's Windows update causes IPv4 to be default

Dan Wing dwing at
Thu Nov 15 18:00:24 CET 2012

> -----Original Message-----
> From: at [mailto:ipv6-
> at] On Behalf Of Olivier MJ
> Crepin-Leblond
> Sent: Thursday, November 15, 2012 4:58 AM
> To: ipv6-ops at
> Subject: Re: Yesterday's Windows update causes IPv4 to be default
> On 15/11/2012 12:38, Nick Hilliard wrote:
> > sounds bizarre that windows is assuming that protocol stability
> > operates on a 30 day basis.  What if ipv6 is tweaked up on day 1, then
> > ipv6 goes down on day 2 because the corporate lan IT people doesn't
> > know and doesn't care about ipv6, and the W8 end users find themselves
> > experiencing 29 days of irritating timeouts?
> I am both concerned and confused about this. What about people like me
> who use a device called a *laptop* and travel around, connecting to all
> sorts of networks in conferences, some being single stack and some dual
> stack?

A new network will earn a new probe.  When it connects to a previously-seen
network, it doesn't issue a new probe.  Windows has long used several 
mechanisms to determine if it has connected to a previously-seen network,
most of those mechanisms are outlined in
(and the corresponding RFC for DNAv6, RFC6059).


More information about the ipv6-ops mailing list