Hello, I have what should be a straight forward setup, but can't get traffic through my bridge. I am using an IBM x3550 M2, running Windows 2012 Hyper-V. I only have two VMs, one Server 2008R2 and my Sophos UTM 9.3. I have four physical NICS. Two are native on board and the other two via a PCIE card (Broadcom dual port BCM5709). I am not using subnets or VLANS. My network is a flat 192.168.0.0/24 network. My switch is an unmanaged 24 port switch.
Traffic Flow
LAN Switch UTM 9.3 Actiontec Router (ISP)
NIC Distribution
- NIC 1 (native) - only Host access - Cat 5e to switch.
- NIC 2 (native) - External virtual switch shared between 2 virtual hosts (Win 2008 R2 & UTM 9.3) - Cat 5e to switch.
- NIC 3 (Dual port card) - Bridged to NIC4 dedicated to UTM 9.3 - Cat 5e to actiontec router.
- NIC 4 (Dual port card) - Bridged to NIC3 dedicated to UTM 9.3 - Cat 5e to switch.
Results
I have NIC 2 (eth0) configured as 192.168.0.10 on UTM and this is my internal / management IP. I have NICs 3&4 (eth1 & eth2) bridged and using IP 192.168.0.20. The Desktop I am testing from is 192.168.0.30. The problem I am having is no traffic seems to traverse the bridge. I am unable to surf or ping outside my local LAN. Oddly, I can ping the management IP from the workstation with no issue. I can ping the bridge IP even without cables plugged into NICS 3 & 4 (red flag)!!!! It appears that all traffic to the mgt nic and the bridge are going through the management nic. I confirmed this by disabling the management port (ETH0) via the hyper-v console, and my pings to the mgt and bridge IPs both stopped. When I reenabled the MGT port (ETH0), the pings started up again.
Experiments (reran after recreating virtual switches in hyper-v, and again after reinstalling UTM)
#1 - Desktop -> Switch -> Actiontec router - Internet connectivity good.
#2 - Desktop -> Switch -> UTM 9.3 -> Actiontec router - No Inet connectivity.
#3 - If I disable management port via the hyper-v console, pinging to mgt and bridge both stop until re-enabled.
I can't tell if this is a misconfigured Hyper-v issue or a UTM issue.
JP
This thread was automatically locked due to age.