P
Pino-55
I have a Windows 10 desktop (64 bit version 1909)
Hyper-V is installed (I am running a Ubuntu VM)
IPv6 is installed and operational (native with DHCP-PD running on the router)
When I connect to my VPN provider, using OpenVPN it fails to connect on IPv6, although the provider supports this and I have verified this on a machine that does not have Hyper-V installed.
The issue seems to be how the TAP-9 interface is handled.
Specifically on the Hyper-V machine Tap-9 interface there is no IPv6 address (other than link-local) and no IPv6 DNS server address. Both exist on the non Hyper-V machine.
Looking at the registry I can see that HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters: DisabledComponents is set to 1(hex) and this appears to be the setting for 'disable IPv6 on all tunnel interfaces'. On the non Hyper-V this key is absent.
My questions are
Is this key the cause of my issues (i.e. is the TAP-9 interface treated as a tunnel?)
What are the risks if I remove or disable this key while Hyper-V is installed and running?
Is there an alternate solution (registry setting) that will allow IPv6 through the VPN tunnel while Hyper-V is running?
Thank you
Continue reading...
Hyper-V is installed (I am running a Ubuntu VM)
IPv6 is installed and operational (native with DHCP-PD running on the router)
When I connect to my VPN provider, using OpenVPN it fails to connect on IPv6, although the provider supports this and I have verified this on a machine that does not have Hyper-V installed.
The issue seems to be how the TAP-9 interface is handled.
Specifically on the Hyper-V machine Tap-9 interface there is no IPv6 address (other than link-local) and no IPv6 DNS server address. Both exist on the non Hyper-V machine.
Looking at the registry I can see that HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters: DisabledComponents is set to 1(hex) and this appears to be the setting for 'disable IPv6 on all tunnel interfaces'. On the non Hyper-V this key is absent.
My questions are
Is this key the cause of my issues (i.e. is the TAP-9 interface treated as a tunnel?)
What are the risks if I remove or disable this key while Hyper-V is installed and running?
Is there an alternate solution (registry setting) that will allow IPv6 through the VPN tunnel while Hyper-V is running?
Thank you
Continue reading...