since my ISP recently (and finally) enabled IPv6 for it's customers, I'm now trying to migrate to native IPv6, as opposed to using tunnelbroker.net.
I have 2 Hyper-V hosts running 2019 with Ethernet for the internal network and Wi-Fi to connect to my provider's LTE router on the window sill. Every host has 2 external virtual Switches: one for the Ethernet and one for Wi-Fi, with the Wi-Fi being disabled for the management operating system in Virtual Switch Manager. In this case, a current Win10 VM I use for testing did not even get an IPv6 address :-(
So per this post I set the "NetworkCategory" for the Wi-Fi interfaces to "Private" for both the the host and the VM. I also enabled the interface for the management operating system with IPv4 and 6. Now the host works just fine, ping -6 to the outside goes through. The VM seems OK too, it has everything it should need: IPv6/Prefix (origin RouterAdvertisement), temporary IPv6, DNS servers and default gateway (both the same as the host). Still no dice with pinging to the outside using IPv6.
The same goes for my Debian routers with dhcp or auto configurations, and accept_ra, autoconf and dhcp all set to 1. And this is the final goal: get my routers to do NAT6 and NAT64.
On the other hand the same host runs another Win10 VM connected to the internal Ethernet (running radvd and W2019DHCPv6) and I've never had any problems with that. Also the router itself works fine, since the problematic VM also has a Wi-Fi interface attached via DDA and connecting to the router that way, everything works. Also note that the VM uses an external vSwitch connected to a Wi-Fi interface which gives you an additional bridge interface...
Does anybody have any ideas? Please! My client provides me with a Hyper-V environment for teaching and I'd really like to stick with it. But I'd also like to get rid of IPv4 permanently which requires native IPv6 in my home office.
