New
#10
Internal switch is more secure because it has no Internet access, it can only communicate with the local network. A bridged internal switch is no longer internal switch.
As soon as you created the bridge, your internal switch became external. The setup you have now is an external switch setup, you are most definitely not using internal switch. This is important to understand so I repeat it: An internal switch is a switch which is connected to local network only but has no internet access. To connect to Internet you need to select an external switch. Bridging an internal switch will create a de facto external switch but can bring connectivity issues.
This from my tutorial at Eight Forums:
A Virtual Switch can be external, internal or private.
- External Virtual Switch: will connect a vm to host NIC. If host NIC is connected to Internet through router, the vm is also connected to Internet. If host NIC (LAN) is not connected to router or if the router has no Internet access, the internal network will still work allowing computers (physical and vm) belonging to the same subnet and workgroup or domain to communicate with each other (file and media sharing etc.). When connecting external switch to host WLAN NIC, the vm loses all connectivity when WLAN is disabled or not connected on host.
- Internal Virtual Switch: When a virtual NIC is connected to Internal VS it can communicate with other computers and vms on the same subnet but has no Internet access.
- Private Virtual Switch: When a virtual NIC is connected to Private VS it can communicate with other vms on same Hyper-V server but cannot communicate with host PC nor has it Internet access. A Private vs is often needed when installing a legacy Linux or pre-XP Windows vm. After installation you need then to disable Private Switch and use Internal or External to connect to the network.
In your case, to get rid of those minor issues, I would disconnect and delete the bridge, create an external switch and change settings for each of your virtual machines to set them use the external switch you created.
When you create an external switch assigning a WLAN adapter to it, Hyper-V takes care of creating the bridge with correct settings.
Kari
Last edited by Kari; 04 Oct 2014 at 18:36.