[ipv6hackers] Windows 10 has random issues with temporary IPv6 addresses staying at Pref Life 0s

Fernando Gont fgont at si6networks.com
Wed Jan 9 18:37:25 CET 2019

On 2/11/18 00:10, fireballiso wrote:
> Hi! I've been using a /64 tunnel from Hurricane for a few years to test
> IPv6 connectivity until my ISP offers native service.
> Linux works well with IPv6. However, recently I've isolated a problem in
> Windows 10 (version 1803, build 17134.345) where the Preferred Lifetime
> of *temporary* IPv6 addresses don't seem to be renewed properly
> sometimes. When the Valid Life reaches 0, it will start counting down
> again from 24 hours, but the Pref Life will stay at 0s; in this
> condition, the temporary addresses don't work on that interface until I
> disable and then re-enable it.

Just doublecheking:
In your scenario, Valid Lifetime > Prefered Lifetime.

1) Prefered becomes 0
2) Then eventually, Valid becomes 0.
3) Then Preferred stays at 0, but valid starts counting down from 24 hs?

How did you let the Preferred/Valid lifetimes expire? Just have the
local router stop sending RAs? Or did you craft an RA packet and sent it
on the network? -- If so, how did your packet look like?

> output of "netsh int ipv6 show addr":
> Addr Type      DAD State       Valid Life         Pref. Life     Address
> ---------          -----------             ---------- -        ---------
>         ------------------------
> Public             Preferred        23h58m22s   3h58m22s
> 2001:470:XXXX:XXXX:XXXX:53c0:9af2:7a20
> Temporary      Deprecated   23h58m22s         0s        
> 2001:470:XXXX:XXXX:bc72:8f4:7d98:3445
> Public             Preferred        23h58m22s   3h58m22s
> fd00:XXXX::XXXX:53c0:9af2:7a20
> Temporary      Deprecated   23h58m22s         0s        
> fd00:XXXX::bc72:8f4:7d98:3445
> Other             Preferred          infinite           infinite     
> fe80::XXXX:53c0:9af2:7a20%13
> Sometimes this problem doesn't happen, and as expected, after Pref Life
> reaches 0 it is reset to start counting down from 4 hours again.

That's not what should happen:
FOr temporary addresses, both timers should eventually expire. WHen
"Preferred Lifetime" expires, the address in question should not be
employed for new connections. Additionally, Windows should configure
another temporary address. When "Valid Lifetime" expires, the address
should be removed.

> Has anyone else seen this bug? Any idea whether there's a fix or
> workaround, other than an interface disable/re-enable?

Please let me know the above. I'd like to reproduce it and try to help.

Fernando Gont
SI6 Networks
e-mail: fgont at si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492

More information about the Ipv6hackers mailing list