Hot answers tagged bridge
The Network Bridge functionality appears to be wholly implemented (at least in Windows 7) by the bridge.sys driver. Without access to the bridge.sys source code it's difficult to say anything with certainty, but some cursory sniffing around the binary doesn't show any exposed APIs that would be helpful in dumping the layer 2 adjacency table. (This ASCII ...
Check that the kernel is set to enable IP forwarding: sysctl -a | grep forwarding You can enable with: sudo sysctl net.ipv4.conf.all.forwarding=1 sudo sysctl net.ipv6.conf.all.forwarding=1 There may also be an issue with ARP proxying. Check with: sysctl -a | grep proxy_arp And set with the command sudo sysctl net.ipv4.conf.eth0.proxy_arp = 1 You ...
Your br0 has both bond0 and eth1 (a bonding slave) in it, and you have no Spanning-Tree on anything. I suspect you have created a network loop and need to remove eth1 from the bridge.
Try this: (source: http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#No_traffic_gets_trough_.28except_ARP_and_STP.29) No traffic gets trough (except ARP and STP) Your kernel might have ethernet filtering (ebtables, bridge-nf, arptables) enabled, and traffic gets filtered. The easiest way to disable this is to go to ...
If the interfaces are on the same subnet, bond them. If they're not, unless the VMs have routes that traverse the second bridge, they're never going to use it. It looks like they are on the same subnet, in which case, follow this guide: https://wiki.debian.org/Bonding
Only top voted, non community-wiki answers of a minimum length are eligible