| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 27 Dec 2007 10:48:00 +0800 From: "Lewis Li" <lachang.li@...el.com.tw> To: <linux-kernel@...r.kernel.org> Subject: Re: 2 ports could not bond to a aggregator in 802.3ad mode issue Yes, you are right. The incorrect behavior is due to we don't setup the lacpdu of switch correctly. The bonding driver is correct. Thanks for your comment! > I do not believe so. > > IEEE 802.3 section 43.3.9 states, in part, > > "Links that are not successful candidates for aggregation (e.g., > links that are attached to other devices that cannot perform aggregation > or links that have been manually configured to be non-aggregatable) are > enabled to operate as individual IEEE 802.3 links. For consistency of > modeling, such a link is regarded as being attached to a compatible > Aggregator that can only be associated with a single link. That is, from > the perspective of Link Aggregation, non-aggregated links are not a > special case; they compose an aggregation with a maximum membership of > one link." > > I do not see that it is correct to attach the links to a common > aggregator, as your output indicates that no partner association has > been created (the Partner MAC is all zeroes) and the links are therefore > apparently connected to a device that cannot perform aggregation. > > --- > -Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com Regards, Lewis Li -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists