You shouldn't have to, but it may be a case where devices aren't brought up in the right order.
On your system, can you try to do: - ifdown -a - ifup lo - ifup eth2 - ifup eth3 - ifup bond0 - ifup br0 And see if that brings everything online properly? With that test ifenslave in my PPA, I added the logic to setup the bond when the slaves are being brought up before the master. I don't know what the bridge scripts are doing in a similar scenario where br0 would be brought up before bond0. As bond0 in that case wouldn't even exist (not just be in a non-configured state), I guess it'd simply fail to add it, giving you that empty bring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889423 Title: 802.3ad bonding not configured correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/889423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
