locked
IPV6 Route Advertisement not forwarded by Hyper-V Default Switch (Windows 10 1909) to guest VM's RRS feed

  • Question

  • My home network is dual stack ipv4/ipv6 and I'd like my VM's to be able to use ipv6 to the Internet.

    My home router advertises a /64 suffix to the network but this does not reach the VM's.

    I want to enable ipv6 forwarding on the Hyper-V Default Switch but can't find any information about how to achieve this.

    I prefer to change the Hyper-V Default Switch opposed to setting up a separate switch since that defeats the purpose of the default switch (it should work out-of-the-box)

    Windows 10 Pro 1909 18363.592


    Saturday, January 18, 2020 10:51 AM

All replies

  • Hi ,

    >>I want to enable ipv6 forwarding on the Hyper-V Default Switch but can't find any information about how to achieve this.

    >>I prefer to change the Hyper-V Default Switch opposed to setting up a separate switch since that defeats the purpose of the default switch (it should work out-of-the-box)

    We cannot remove or manage default switch, so I am afraid we cannot enable IPV6 forwarding on the default switch.

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Monday, January 20, 2020 9:18 AM
  • any chance in enabling some options through powershell to the default switch to enable it?

    Alternatively: Why would the default switch only allow for ipv4 routable traffic if public ipv6 is available in the host network?

    Monday, January 27, 2020 3:40 PM
  • Hi ,

    Sorry for the delayed response.

    >>any chance in enabling some options through powershell to the default switch to enable it?

    No ,we cannot manage default switch.

    >>Alternatively: Why would the default switch only allow for ipv4 routable traffic if public ipv6 is available in the host network?

    I did not find any related article talking about that if default switch will allow for IPV6 traffic. 

    Please understand, our forum doesn't focus on IPV6 related question, so I need to do more research on it. If we have any updates or any thoughts about this issue, we will keep you posted as soon as possible.

    If you have any updates during this process, please feel free to let me know.

    Best Regards,

    Candy


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Thursday, February 6, 2020 8:38 AM
  • Hi Tonjes,

    Sorry, it seems I have the same problem as you.

    I have tried as you did to play with the so-called "Default Switch". But, after many readings, I decided to forget about it and create an External vSwitch. Many persons have already tried to mangle the "Default Success" without any success - including myself.

    The good about External vSwitch:

    - both host and guest can talk to each other throughout the External vSwitch i.e, via the Hyper-V entity inside your (host) machine without traffic through Wifi or Ethernet cable. I would like to suggest you to change the network profile (public/private) of the External vSwitch to match the one of the host computer (which is probably already set to private). Otherwise, the firewall on host will block the access from guest  - without any error message. Please do have a look at https://www.servethehome.com/change-hyper-v-network-category-public-private-powershell/

    - moreover, guest and host can talk to each other via IPv6. Just try ping -6 <computername>

    - furthermore, you can access other computers in your local network using IPv6.

    Note: do not forget to "Allow management OS to share..." on Hyper-V GUI. 

     

    The bad:

    - neither host nor guest will be able to access IPv6-only sites, such as https://www.v6.facebook.com/. Only IPv4 will be working to access the outside world. Usually it is not yet a big trouble (by the way, we are in April 2020 and IPv4 should have been died long ago!).

    The ugly:

    - the External vSwitch will "wrap" the network adapter (wifi/Ethernet) that you will set to work with it. Meaning? If you open Task Manager Performance Tab you will notice that the adapter has gone! But believe me, it is still there!

    I know all of this because I have posted something just like you did: No IPv6 traffic inside WDAG, Sandbox and Hyper-V - Windows 10 Pro, v 1909. And it is still open!

    To finish, please have a look at What is the Hyper-V Virtual Switch and How Does it Work? It has helped me a lot!

    Good luck!

    Sandro


    Sunday, April 5, 2020 12:35 AM