I hate IPv6 - Skuzzy signal

[Vulcan]

I decided to enable IPv6 on my network for someone unknown masochistic reason. I had played with it before but decided it had a negative performance impact for some CDNs.

Yesterday I turned it back on. But when I do IPv6 tests AND according to my IPvFoo plugin the laptop is sticking with IPv4. But all my NSLOOKUPs, PINGs, and TRACERTs indicate the underlying v6 is just fine. In fact another PC with a static v6 address is just fine (older Server 2k8) and everything works as expected. Same happens for Win 10 gaming PC. I'm stumped, I've tried DHCPv6 and Static v6 for both, no difference. I've forced disable the windows auto-generated-random-private addresses as well.

My browser insists v6 doesn't work but when I check the chrome net-internals the DNS table looks like this:

Hostname   Family   Addresses   TTL   Expires   Network changes
18.client-channel.google.com   UNSPECIFIED   
108.177.125.189
2404:6800:4008:c01::bd
-1000   2018-05-25 14:57:09.767 [Expired]   93
21.client-channel.google.com   UNSPECIFIED   
108.177.125.189
2404:6800:4008:c01::bd
-1000   2018-05-25 14:57:45.035 [Expired]   93
22.client-channel.google.com   UNSPECIFIED   
108.177.125.189
2404:6800:4008:c00::bd
-1000   2018-05-25 14:42:54.276 [Expired]   93
6232247.fls.doubleclick.net   UNSPECIFIED   
216.58.203.102
-1000   2018-05-25 14:44:02.229 [Expired]   93
6950718.fls.doubleclick.net   UNSPECIFIED   
216.58.203.102
-1000   2018-05-25 14:44:02.228 [Expired]   93
accounts.google.com   UNSPECIFIED   
216.58.203.109
2404:6800:4006:809::200d
-1000   2018-05-25 14:57:07.463 [Expired]   93

...and I can see my browser sending out v6 requests and getting responses.

[Skuzzy]

It could be the network paths are not all IPv6 enabled, which could force the stack back to IPv4.

You know the IPv6 stack in Windows is not exactly up to the standard.  Of course, the IPv4 stack is messed up too.  It is amazing any of it works at all.

I have dabbled in IPv6 and gave up on it.  Does not seem to be well supported across the Internet.

[save]

Pretty much the only companies using IPV6 extensively it are the telecom operators, they use it for customer cell phone internet usage for NAT/PAT it into Ipv4.
Companies i've have contact with, use F5's or A10 ADC's for the IPv4-IPv6 translation.

It could be the network paths are not all IPv6 enabled, which could force the stack back to IPv4.

You know the IPv6 stack in Windows is not exactly up to the standard.  Of course, the IPv4 stack is messed up too.  It is amazing any of it works at all.

I have dabbled in IPv6 and gave up on it.  Does not seem to be well supported across the Internet.

[Vulcan]

Network paths are fully enabled and all. IPv6 is working in the network just fine, it's just a couple of PCs browsers that refuse to use it.

Lots of people are starting to use v6, plenty of CDNs as well. My real interest is in experience for business/enterprise work, there is nothing like getting your hands dirty to learn.

For example, did you know that in there is a mode windows automatically operates in called privacy mode. Each application can get a different IPv6 address, the idea being it is hard for trackers to follow you. It's insanely stupid, a single PC can end up with dozens and dozens of v6 addresses. Trying to integrate that with corporate security is a nightmare - but it can be turned off thankfully. It screws with things like Single Sign On and imagine NDP table size explosions (NDP is the v6 equivalent of ARP tables) potentially hitting device limits.

OK apparently one of the recent Windows Updates screwed things, you have to reinstall your NIC driver. So Windows now shows IPv6 Internet but Chrome is sticking with v4 

[Skuzzy]

I wonder if Chrome is doing something, at the network API level, they should not be doing.

[ACE]

I wonder if Chrome is doing something, at the network API level, they should not be doing.

Well yes, of course.

[twistedtechmike]

Well, you can always use prefix policies to prioritize IPv6 and on which networks...delete the existing and add the new one with modified priority.

netsh interface ipv6 add prefixpolicy ::ffff:0:0/96 70 4