You might have also noticed that although the virtual switch vEthernet
is connected to (is using) host’s WLAN NIC
it is however showing an Ethernet LAN
symbol (connector of a LAN cable) and presented under LAN connections
. This has a simple explanation: all Hyper-V network connections are Ethernet (LAN) connections; Hyper-V does not support WiFi so even when a virtual switch is connected to a wireless NIC, Hyper-V presents it as Ethernet connection to the virtual machine i.e. the virtual NIC on vm “thinks” it is connected with an Ethernet cable.
This also means that when we are using an external virtual switch connected to a WLAN NIC, we need an extra network bridge on the host. The virtual NIC connects to a virtual switch, virtual switch in its turn connects to a host network bridge which creates (as its name says) a bridge between our virtual Ethernet connection and host WLAN NIC’s connection to the router: