drivers/net/bonding/bond_3ad.c | 3 +++ 1 files changed, 3 insertions(+)
New commits: commit 0b0b7113f42d0d9df3d26a4c4bcd28ff29af9b91 Author: Stephen Hemminger <[email protected]> Date: Wed Jan 7 16:45:11 2009 -0800 bonding: don't assign down link as aggregator If I put two interfaces into a bonded device using 802.3ad, then the bond0 device always has link up (carrier). It looks like the code in best aggregator selector believes that any link with ports is good enough to be considered the best, so when second ethernet is added, it considers the first one as good enough to be aggergator. After that, since there is one aggregator, it thinks the link is up. One way of fixing it is this, but does it violate the standard? Signed-off-by: Stephen Hemminger <[email protected]> http://suva.vyatta.com/git/?p=linux-vyatta.git;a=commitdiff;h=0b0b7113f42d0d9df3d26a4c4bcd28ff29af9b91 _______________________________________________ svn mailing list [email protected] http://mailman.vyatta.com/mailman/listinfo/svn
