I’m going to look into other switches/routers and read the spec a bit closer, but linux seems to think the LACPDU check is packet size => sizeof(struct lacpdu) :
- https://github.com/torvalds/linux/blob/70e71ca0af244f48a5dcf56dc435243792e3a495/drivers/net/bonding/bond_3ad.c#L2185 - David P. Discher http://davidpdischer.com/ AIM: DavidDPD | Y!M: daviddpdz On Dec 18, 2014, at 10:46 AM, John-Mark Gurney <j...@funkthat.com> wrote: >> >> Good find, Craig. Also, I found the full LACPDU definition. It's in >> section 5.4.2.2, page 33, of the 802.1ax-2008 spec that I linked to. >> You can see the 4-byte FCS field at the end. Does your tp_link[4] >> field look like an FCS? If so, you need to figure out why it's >> propagating all the way up to the LACP level. > > It very well could be that the authors of the TP-Link firmware missed > the comment in 1ax that says the FCS is generated by the MAC, and > include it in their sending... > > If you could capture the original frame, and check the ether_type > field, to see if it is 124 or 128... If it's 128, they probably added > the FCS manually and the the MAC adds it a second time... >
signature.asc
Description: Message signed with OpenPGP using GPGMail
