What steps will reproduce the problem?
1. using configuration 7 in your examples but with Hyper-V platform.
2. Pinging from physical hosts to virtual or opposite
3.
What is the expected output? What do you see instead?
I should be able to ping hosts on either side of the bridge. It is not
functioning as a bridge. When using static IP for the bridge, it only responds
to pings from eth0. So it is definitely not bridging between the two interfaces.
What version of the product are you using? On what operating system?
v10. Running it on Hyper-V Windows Server 2012 Enterprise.
Please provide any additional information below.
I am trying to bridge the host OS to the physical NIC for experimentation
purposes. I set it up so the host OS connects to an internal vSwitch. The WAN
bridge also connects to the internal vSwitch. I then create a second vSwitch
which connects to the physical NIC. The bridge also connects to this. So I have
OS>vSwitch(int)>WAN>vSwitch(ext)>NIC. As previously mentioned, the bridge only
responds to pings from eth0 which connects to the internal vSwitch. So the OS
can ping the bridge. But anything after the NIC cannot ping the bridge or the
OS. If i map eth0 to the external vSwitch, then everyone else can ping the
bridge but the host OS cannot.
Why is it not bridging the two interfaces?
Original issue reported on code.google.com by f.sar...@gmail.com on 7 Mar 2014 at 1:35
Original issue reported on code.google.com by
f.sar...@gmail.comon 7 Mar 2014 at 1:35