It looks like this has something to do with iptables (even if there are no iptables rules).
While messing around with something else I tried disabling bridge track from passing through iptables and that seemed to fix the problem. sysctl setting: net.bridge.bridge-nf-call-iptables=0 Unfortunately this isn't really an option in all cases as we (and OpenStack) rely on iptables in a number of places. Working configuration (in addition to above): sysctl net.bridge.bridge-nf-call-iptables net.bridge.bridge-nf-call-iptables = 0 iptables-save # Generated by iptables-save v1.4.12 on Thu Oct 4 01:31:25 2012 *filter :INPUT ACCEPT [623:48985] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [860:94775] COMMIT # Completed on Thu Oct 4 01:31:25 2012 What is the value of net.bridge.bridge-nf-call-iptables in your environment? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013199 Title: be2net driver used by HP BL460c bridge networking not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1013199/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
