Enabling IPv6 on Windows

provels

This has nothing to do with pfSense, other than it works GREAT with IP_v6 on all my clients except one and I've been running with you guys since v1.2.3 on a gmirror RAID my Nokia ip530. So I thought I'd ask here since you're such a friendly bunch...! No doubt it's something I broke, but I have a 2012 R2 Windows host that does not think IPv6 is enabled even though it's turned on in the adapter properties. When I connect to https://ipv6-test.com , every client is happy (Hyper-V or physical) except the Hyper-V host. So obvs it's not pf or another network stack. I've tried en/disabling, removing adapter, etc. w/o benefit. Latest driver installed, etc. I've Googled some regedits to no benefit. It's an Intel/IBM i-340 4-port with adapter defaults. Any thoughts? Thanks much.

bmeeks

Try one of these registry fixes from the Microsoft KB site: https://support.microsoft.com/en-us/help/929852/guidance-for-configuring-ipv6-in-windows-for-advanced-users. There are ways to disable IPv6 support within the registry. Perhaps one of those scripts got executed on your non-IPv6 host at some point in the past?

provels

@bmeeks Thanks for your reply. Yes, I ran over that link yesterday and still couldn't get it to work. Now I have a Win10 wireless laptop that will arbitrarily work/not work on IPv6 test sites. Thought it might have something to do with my access points, as one would work, the other wouldn't, but then the first one stopped working, too. Would be nice if it was at least consistent. I'm running the same av/av version on all clients and disabling it doesn't seem to help, so I don't think that's it. Maybe just something in the Windows TCP/IP stack. Going to try removing and adding back if I can still do that. Do I need IPv6? Of course not. But I'm a control freak. LOL I find broken stuff annoying.

Any idea WTH the providers at top and bottom here are? Win10 box.

johnpoz

my guess would be having to do with the windows linux system.. Do you have wsl enabled?

provels

@johnpoz No I don't and never have. My other Win10 VM (which works for IPv6) and my H-V host (which doesn't) just show this:

Neither Win10 box (phy/vm) have the Adapters and Bindings tab so that must be normal. Googling the Plan 9 and RemediationNP providers get me nothing. Possibly Dell Remote Assist, since a Dell laptop? Dunno. Possibly something to do with TAP/OpenVPN (client is installed)?

EDIT: Could be something for my Windows phone hacking. Some SDK or tool.
But probably not something affecting IPv6. I'm a mess.

EDIT2: Yes it does have WSL. Probably something for the phone. Sorry.

provels

I was thinking this may be a browser issue, but... On my Win10 laptop, Edge works (most times). For example, today it didn't work at first, so I bounced to my other AP where it did work. Bounced back to the first AP, still worked. Go figure. But IE, Chrome or Opera would not. I did notice that Edge used IPv6 as the default with IPv4 fallback, but the other browsers use IPv4 as default. But then I checked IE on my Win10 VM and that worked fine. So go figure x2. Back in olden times, I used to be able to remove TCP/IP and add it back to reset it, but doesn't appear to be the case anymore. Maybe I can try exporting a reg setting from a working box.

johnpoz

So does windows show a link local address? what does the output of ipconfig /all show?

I turn ipv6 on and off all the time on windows 10 machine..

Here it is off

$ ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : i5-win
   Primary Dns Suffix  . . . . . . . : local.lan
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : local.lan

Ethernet adapter Local:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
   Physical Address. . . . . . . . . : 00-13-3B-2F-67-62
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.9.100(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.9.253
   DNS Servers . . . . . . . . . . . : 192.168.9.253
   NetBIOS over Tcpip. . . . . . . . : Enabled

Here it is on..

$ ipconfig /all                                                                        
                                                                                       
Windows IP Configuration                                                               
                                                                                       
   Host Name . . . . . . . . . . . . : i5-win                                          
   Primary Dns Suffix  . . . . . . . : local.lan                                       
   Node Type . . . . . . . . . . . . : Hybrid                                          
   IP Routing Enabled. . . . . . . . : No                                              
   WINS Proxy Enabled. . . . . . . . : No                                              
   DNS Suffix Search List. . . . . . : local.lan                                       
                                                                                       
Ethernet adapter Local:                                                                
                                                                                       
   Connection-specific DNS Suffix  . : local.lan                                       
   Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller              
   Physical Address. . . . . . . . . : 00-13-3B-2F-67-62                               
   DHCP Enabled. . . . . . . . . . . : No                                              
   Autoconfiguration Enabled . . . . : Yes                                             
   IPv6 Address. . . . . . . . . . . : 2001:470:XXXX:9::2000(Preferred)                
   Lease Obtained. . . . . . . . . . : Tuesday, June 25, 2019 9:46:47 AM               
   Lease Expires . . . . . . . . . . : Tuesday, June 25, 2019 11:46:47 AM              
   Link-local IPv6 Address . . . . . : fe80::50:703a:ac66:c23b%15(Preferred)           
   IPv4 Address. . . . . . . . . . . : 192.168.9.100(Preferred)                        
   Subnet Mask . . . . . . . . . . . : 255.255.255.0                                   
   Default Gateway . . . . . . . . . : fe80::208:a2ff:fe0c:e624%15                     
                                       192.168.9.253                                   
   DHCPv6 IAID . . . . . . . . . . . : 520098619                                       
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-1F-5D-A5-38-59-F9-5F-63-C1       
   DNS Servers . . . . . . . . . . . : 2001:470:XXXX:9::253                            
                                       192.168.9.253                                   
                                       2001:470:XXXX:9::253                            
   NetBIOS over Tcpip. . . . . . . . : Enabled                                         
   Connection-specific DNS Suffix Search List :                                        
                                       local.lan

Do you show a linklocal but just not a goblal its prob just related to getting an IP depending on how your trying to do it SLACC, dhcpv6? etc. etc..

I have made a reg change, and then removed the nonsense with netsh to remove the bs adapters like isatap and teredo which have no use for. So turning it fully off and on is simple check box in the interface props.

provels

Appears I have no IPv6 DNS server, probably not relevant? Using pfBlockerNG in Resolver mode, no DNS on pfSense except 127.0.0.1.

Somewhat working Win10 Laptop:

Wireless LAN adapter Wi-Fi 2:

   Connection-specific DNS Suffix  . : workgroup
   Description . . . . . . . . . . . : Dell Wireless 1820A 802.11ac
   Physical Address. . . . . . . . . : 30-52-CB-E7-50-71
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2601:240:4200:26d8:1ca:93dd:c993:348b(Preferred)
   Temporary IPv6 Address. . . . . . : 2601:240:4200:26d8:9d51:9e10:4781:bce5(Deprecated)
   Link-local IPv6 Address . . . . . : fe80::1ca:93dd:c993:348b%16(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.102(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, June 25, 2019 9:45:34 AM
   Lease Expires . . . . . . . . . . : Wednesday, June 26, 2019 5:25:20 AM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 355488459
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-AD-A8-E8-30-52-CB-E7-50-71
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

100% Working Win10 VM:

Borked Hyper-v host (Missing a 2601 address?):

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Q6600
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Q6600:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Intel(R) Ethernet Server Adapter I340-T4 #3
   Physical Address. . . . . . . . . : 90-E2-BA-4C-E5-7E
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::f19f:7b17:4044:1673%25(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.20(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 361816762
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-CE-7A-CD-00-1F-D0-A6-C2-1F
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

provels

So magically my Hyper-V host now has an IPv6 address and IPv6-test.com seems to work for me 100% from it w/o making any changes, not even a reboot of either the host or FW. I still have the issue where my Win10 laptop performs intermittently, but works if I bounce to another access point and continues to work even if I bounce back. Just weird.

At any rate, I have noticed that from all machines the test results list my IPv4 WAN address, but all the IPv6 addresses are machine-specific. Is there a short answer to this or is it just how IPv6 works? The range assigned is not the same as the WAN v6 address. Thanks for any replies.