Skip to content

Instantly share code, notes, and snippets.

@zeddee
Created September 13, 2020 00:48
Show Gist options
  • Save zeddee/39668bc393027eb80b80dbb7d938b034 to your computer and use it in GitHub Desktop.
Save zeddee/39668bc393027eb80b80dbb7d938b034 to your computer and use it in GitHub Desktop.

Hyper-V internal networking

writing this down before i forget.

main takeaways:

  • restart Windows when in doubt.

  • Don't use Hyper-V's "External" virtual switches.

  • Instead:

    1. Create a new "Internal" virtual switch to put all your VMs on.
    2. Create a bridge network using your ethernet/wireless adapter (configure network adapters in Control Panel) and this new switch.
    3. Restart windows.
  • managing networks on hyper-v is a pain because some update somewhere in Windows 10 broke how the Hyper-V virtual NIC would piggyback on the physical NIC to hoist VMs' virtual NICs onto the same subnet as the physical NIC.

  • if you were to set a Hyper-V virtual switch to "External" now, it would just hijack the physical NIC, and stop all internet traffic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment