Hyper-v create external Virtual Switch && external virtual switch remove host connection fix

 create external Virtual Switch

https://geek-university.com/vmware-esxi/virtual-switch-explained/

 

VMware has designed the vSphere suite to mimic the functions of a physical network, so a lot of the network hardware you’ll find in the real world, you will also find virtualized in vSphere. Virtual switches work very much like their physical counterparts, Ethernet switches, but lack some of their advanced functionality. They are used to establish a connection between the virtual and the physical network. A virtual switch can detect which virtual machines are logically connected to each of its virtual ports and use that information to forward traffic to the correct virtual machines. A virtual switch is connected to physical switches by using physical Ethernet adapters to join virtual networks with physical networks.

 

 

 

Create virtual switch in hyper –v  

https://www.vembu.com/blog/creating-hyper-v-virtual-switch-in-hyper-v-vm/

 

 

Virtual machine are in DHCP bridgeMode, they are ususally in a different subnet than HOST, but because of the virtual switch, host can ping virtual machine

https://askubuntu.com/questions/224391/unable-to-ssh-into-ubuntu-vm-running-w-a-nat-ip-address-even-w-openssh-server

 

The problem is the NAT. When you are using NAT, VirtualBox basically acts like a router making a subnet, and just like with a normal Router setup you can't access a device on a lower subnet. As I see it you have two options here:

1.      Switch your VM to a "Bridged Adapter" mode(can be done even after an OS is installed) and then Reboot or Renew your Server's IP. Your VM should show up with a normal IP on your Network and then you can easily access it. I usually recommend this for Servers anyway because burying a Server defeats the use of one.

2.      Make a Reverse SSH Tunnel. Basically instead of making a tunnel from your Host to the Guest Server, you do it the other way around. This is a pretty straight forward task and there's a nice HowTo to be found here: http://www.howtoforge.com/reverse-ssh-tunneling, Just use your Host's normal network IP and it should work. A user also posted a nice thing in the comments of the article about SSH Tunnels between 2 PCs with both being behind NATs.

Out of the above I still recommend #1 for obvious advantages to a server setup but if you really want to keep the Server Sandboxed then #2 should work fine.

external virtual switch remove host connection fix

 

For anyone that comes across this question. How I fixed it for me was to uncheck  the "allow managmeent oprating system to share this adapter". Click apply. Click Yes on the popup. Then check it and press apply again. At which point, the vEthernet adapter went from 'network' to 'Domain Network', and I could access the network and internet again on the host system

 

https://social.technet.microsoft.com/Forums/Office/en-US/e4d07e7d-e016-4801-93af-ae48b56b3249/hyperv-virtual-network-switch-disconnects-host-machines-network-connection?forum=w8itprovirt

After external virtual switch has been created, host and virtual machine will both use this virtual switch, need to right click on this virtual switch , check properties, IPV4 to re assign static IP of host.

The VMs uses DHCP IPs and in bridge mode by default(in a different/same subnet as host)

EX 192.168.11.0/24  0 - 255, 2^8 = 256 IPS, 0 networkID, 255 broad cast ID, IP range 1-254, 1 usually gateway IP