On Dec 4, 2014, at 12:50 PM, Alan Somers <[email protected]> wrote:
>> Not sure if the attachment will work to the list, but here is a pcap >> attached em1 (sudo tcpdump -i em1 -s 0 -w lacp.pcap). Attaching to the lagg0 >> with tcpdump, filters out the freebsd’s LACP packets, but still sees the >> TP-Link’s packets. > > Did you remember to configure the switch to use LACP on those ports? > It isn't automatic. And did you remember to manually up em1? Those > are the two commonest LACP configuration mistakes. > > -Alan 99% sure the switch is configured correctly. I’ve actually tried all the different combination of the switch supports, and can’t seem to get them to sync up. From the pcaps, both the host and switch are sending the LACP packets … but it seems that the freebsd is just passing them through/up … almost like FreeBSD doesn’t recognized them as LACP packets. In looking a bit deeper on the pcaps in wireshark - the TP-Link’s packet correctly labels the “partner” systems to the super micro/freebsd box by port and mac address, however the FreeBSD response has all zeros for the partner systems mac and port. So without looking at the logs on the switch, my guess is the switch correctly sees the FreeBSD box, however the FreeBSD box is not correctly recognizing the packets from the switch as LACP. Feels like a single bit or flag in the switches packets that is not matching what FreeBSD is expecting. I was hoping someone would have some insight before I start looking at each bit of the packets what’s not aligned. - David P. Discher http://davidpdischer.com/ AIM: DavidDPD | Y!M: daviddpdz
signature.asc
Description: Message signed with OpenPGP using GPGMail
