I am trying to set up a Linux bridge with 2 ethernet interfaces and cannot get it to work correctly. I am using Gentoo Linux and thought it would be quite easy but I end up having trouble getting packets go through the bridge. All of that is virtualized under Hyper-V is that matters for anything (but I doubt it).

Here goes my configuration.

 ------              ------------------           --------         -----------
| NUX3 |------------|eth1  BRIDGE  eth0|---------| ROUTER |-------/ INTERNET /
 ------              ------------------           --------        ----------- (br0)
00:15:5d:00:01:12   00:15:5d:00:01:08 (eth0)   00:15:5d:00:01:03
                    00:15:5d:00:01:13 (eth1)       

# cat /etc/conf.d/net

bridge_br0=( "eth0 eth1" )
config_eth0=( "null" )
config_eth1=( "null" )
config_br0=( " netmask brd" )
routes_br0=( "default via" )

# brctl show

bridge name      bridge id              STP enabled      interfaces
br0              8000.00155d000108      no               eth0

# brctl showstp br0

eth0 (1)               state               forwarding
eth1 (2)               state               forwarding

# cat /etc/sysctl.conf

net.ipv4.ip_forward = 1
net.bridge.bridge-nf-call-arptables = 0
net.bridge.bridge-nf-call-iptables = 0

# ifconfig

       inet addr:  Bcast:  Mask:

# brctl showmacs br0

port no mac addr                    is local?        ageing timer
  1     00:15:5d:00:01:03           no                   1.51
  1     00:15:5d:00:01:08           yes                  0.00
  2     00:15:5d:00:01:12           no                  36.22
  2     00:15:5d:00:01:13           yes                  0.00

BRIDGE can ping the ROUTER but not NUX3, NUX3 cannot ping neither BRIDGE nor ROUTER. All seems good to me but I am obviously missing something. I'd be really glad if someone can point me to it!


  • I can also do it all manually but situation is exactly the same. No problem to bring the bridge up but nothing seems to go through... Mar 1, 2010 at 14:24

3 Answers 3


It's possible that the underlying network devices on the host do not have promiscuous mode enabled. In VMWare, for example, if the underlying virtual network adapter isn't +promisc then the guest bridge will fail miserably -- even though it thinks its able to enter promiscuous mode, it can't.

I've never used HyperV, but the logic should be the same, if the host doesn't allow the guest to enter promiscuous mode, the bridge can't pass packets back and forth because the network card will only handle frames that are addressed specifically to it.

If you disable the bridge, you're able to ping NUX3 and the router, correct?

  • Absolutely, I can ping both. Whoa, that would seem like a reasonable explanation of both a correct setup and a miserable failure to bridge while being absolutely logic :D I'll go find out right now and will keep you posted. Thanks John. Mar 2, 2010 at 8:28
  • I'll go ahead and rate this as the answer, since I can feel you are absolutely right. Trouble is that Hyper-V does not, as of today, support promisc mode for the virtual interfaces... DUH! Wish I knew that before :) Thanks again Jonh, you spared me some serious wasted time. Mar 2, 2010 at 9:27
  • Spot on, works like a charm with same VM under ESXi ;) Mar 3, 2010 at 18:24
  • Glad to know this worked for you... Can't say I'm too surprised by another half-baked Microsoft product, even free software works better than that ;)
    – John Ewart
    Mar 4, 2010 at 3:45
  • 1
    Clint's answer below fixed this for me! Feb 18, 2015 at 21:36

in the hyper-v manager, go to the settings for the vm you want to use a bridge on, and under every network interface that you want to use as part of the bridge enable the "allow mac address spoofing" checkbox. I'm using Windows Server 2008r2 SP1. That's what I did to get it to work. I'm also using Ubuntu 12.04 which has all the Hyper-V drivers preinstalled, but I don't think that matters.


Bridging works fine.

  1. As saying before need to enable MAC address spoofing
  2. In latest kernels iptables rules actuals for bridge too. So it must configured or disabled. For disable iptables rules for bridges execute: sysctl net.bridge.bridge-nf-call-iptables=0
  • 2
    OMG have issue in setting up EVE NG nested virtualization under KVM and not able to ping my gateway through bridge network... but using this command in eve i am able to ping a gateway.. vert very thanks for the posting sysctl net.bridge.bridge-nf-call-iptables=0 Sep 17, 2020 at 21:21
  • Thanks a lot, I'm not sure why this fixes my issue, I was looking at traffic on the bridge and it was actually mixed with both interfaces but not forwarding to each other, and now it's perfectly working, thanks a lot!
    – YCN-
    Jun 28 at 14:57

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .