@gollum53: you are using lucid or later and you should have the following exmaple as bonding config in your /etc/network/interfaces
auto bond0 iface bond0 inet static address 192.168.1.10 netmask 255.255.255.0 gateway 192.168.1.1 bond-slaves none bond-mode 1 # active-passive bond-miimon 100 auto eth0 iface eth0 inet manual bond-primary bond0 bond-slaves eth0 eth1 auto eth1 iface eth1 inet manual bond-primary bond0 bond-slaves eth0 eth1 Why is that? Upstart brings most of the time first the bond0 interface up. But in most cases at this time, the hardware interfaces are not ready (udev didn't signal that to upstart) So, the bonding of the hardware interfaces to the bond interface needs to be done on hardware nic level. Can you come back and try that, pls? It works here on several hundreds of servers of HP without any problem. REgards, \sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/678425 Title: virtual network interfaces sometimes dont start on startup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs