I'm also seeing this running On a Penguin Relion 2612, using the forcedeth gigabit ethernet driver, bonding eth0 and eth1 with bond-mode 4. Also, I'm running a vlan setup on top of the bonded driver.
I can generally get the setup to work by hand, although seemingly not with a mere "/etc/init.d/networking restart" or "ifdown bond0; ifup bond0". On initial startup, it seems that only one of the two slaves, either eth0 or eth1 is listed with "ifconfig", but not both. If I remove all devices with "ifconfig eth0 down; ifconfig bond0 down; ifconfig lo down", etc. and then "ifdown bond0", and do a network restart, it will end up working after some fiddling. In which case the bond0 interface, both eth0 and eth1, the vlan, and lo, are all listed by ifconfig. This is on a fresh karmic install from alternate install CD, btw. I just reinstalled from a system running Hardy, where this worked fine, although I had to update the /etc/network/interfaces configs (I was using post-up/down ifenslave passages before) -- 802.3ad interface bonding fails if started too early https://bugs.launchpad.net/bugs/482419 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
