Netgate SG-1000 microFirewall

Author Topic: IPv6 weirdness on Windows after 24 hours  (Read 824 times)

0 Members and 1 Guest are viewing this topic.

Offline virgiliomi

  • Sr. Member
  • ****
  • Posts: 563
  • Karma: +74/-4
    • View Profile
IPv6 weirdness on Windows after 24 hours
« on: March 17, 2016, 10:56:46 pm »
So I've seen this for a couple of days now... and it's a unique one.

I'll turn on my Windows system... desktop, laptop, it doesn't matter. IPv6 RA is Stateless DHCP (since Windows doesn't use RDNSS to get DNS server info). Computer receives the RA, determines a SLAAC IP address with privacy extensions, etc.

IPv6 works great. Sites load using IPv6 (as determined by the IPvFoo extension to Chrome). I can ping hosts using hostname and an IPv6 address is used. IPv6 test sites pass wonderfully.

24 hours pass... this is the default valid lifetime of the RA. All of a sudden, sites load using IPv4. Pinging a hostname results in the IPv4 address being pinged. IPv6 is no longer preferred over IPv4. BUT... it DOES still work. If I ping -6 google.com, I get replies. IPv6 test sites show IPv6 works, but that IPv4 is preferred.

Not sure if this is a Windows issue. None of my other devices - Apple (iOS and OS X) or Android, that I can see/tell - have an issue like this. But this issue only just started happening, and the only thing that's changed is the 2.3 snapshots on my pfSense box. I can reboot the computer and IPv6 works great again... for the next 24 hours.

Thoughts?

marjohh

  • Guest
Re: IPv6 weirdness on Windows after 24 hours
« Reply #1 on: March 19, 2016, 03:58:14 am »
Definitely sounds like a windows issue; which version of windows?

Offline virgiliomi

  • Sr. Member
  • ****
  • Posts: 563
  • Karma: +74/-4
    • View Profile
Re: IPv6 weirdness on Windows after 24 hours
« Reply #2 on: March 19, 2016, 07:20:51 am »
I'm thinking it is too now... after leaving a couple of my systems on for a couple of days, it seems like only one is really having IPv6 issues after a while, the others must have been temporary issues before. It's Windows 10 on all. I don't think this is a pfSense issue at this point.