I am running a test lab on my Windows 8.1 using Hyper-V.
![]()
My problem is, that the virtual LAN has limited connectivity, when the external vSwitch is configured to use the wifi interface, instead of the cable interface. I am troubleshooting this issue for hours now and I reached the point where I believe the Network
Bridge, that is created by the Hyper-V Virtual Switch Manager, is not forwarding packets.
Pings are delivered from 192.168.178.2 to 192.168.178.1 and back again.
Pings from 192.168.0.10 are delivered to 192.168.178.1, and the reply does reach the wifi interface …
== Trace on the WiFi interface ==
Here you see a log of the trace on the WiFi interface of the Hyper-V-Host,
while 192.168.0.10 is pinging 192.168.178.1
No Time Source Destination HW Source HW Destination Protocol Info
3 0.003340000 192.168.0.10 192.168.178.1 24:65:11:cc:c0:9e 24:65:11:2b:35:e4 ICMP Echo (ping) request id=0x0001, seq=44/11264, ttl=127 (reply in 4)
4 0.006094000 192.168.178.1 192.168.0.10 24:65:11:2b:35:e4 24:65:11:cc:c0:9e ICMP Echo (ping) reply id=0x0001, seq=44/11264, ttl=64 (request in 3)
5 0.006152000 192.168.178.1 192.168.0.10 24:65:11:cc:c0:9e 24:65:11:2b:35:e4 ICMP Echo (ping) reply id=0x0001, seq=44/11264, ttl=64
… but is never forwarded to the Network Bridge interface.
== Trace on the Network Bridge interface ==
Here you see a log of the trace on the Network Bridge interface of the Hyper-V-Host,
while the Hyper-V-Host is pinging 192.168.178.1 (#1)
and the 192.168.178.2 is pinging 192.168.178.1 (#7)
-> Note: The ping-reply from 192.168.178.1 to 192.168.0.10 is missing!
1 0.000000000 192.168.178.1 192.168.178.21 24:65:11:2b:35:e4 24:65:11:cc:c0:9e ICMP Echo (ping) reply id=0x0001, seq=9/2304, ttl=64
7 7.852500000 192.168.178.1 192.168.178.2 24:65:11:2b:35:e4 00:15:5d:b2:21:18 ICMP Echo (ping) reply id=0x0001, seq=439/46849, ttl
How do I solve this problem?