registry team mailing list archive

Thread
Date

[Bug 482419] Re: 802.3ad interface bonding fails if started too early

To: registry@xxxxxxxxxxxxxxxxxxx
From: Michal Kleczek <482419@xxxxxxxxxxxxxxxxxx>
Date: Tue, 07 Dec 2010 19:51:38 -0000
Reply-to: Bug 482419 <482419@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

My symptoms are that interfaces are not brought up at boot. I have to manually:
1. stop networking
2. rmmod bonding
3. modprobe bonding
4. start networking
5. bring up all vlans one by one (ifup bond0.150x)

Once interfaces are up I do not have any problems with the network.

The history is that it didn't work after fresh Lucid installation. Then - after one of the updates it started working and now it is broken again (so I'm not sure if it is actually ifenslave issue). Sorry but I don't remember what updates they were.
I've tried different versions of ifenslave and various kernels. For me it looks like it has something to do with vlans being started too early.

-- 
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.
https://bugs.launchpad.net/bugs/482419

Title:
  802.3ad interface bonding fails if started too early