Date: Thu, 4 Dec 2014 13:10:45 -0800 From: "David P. Discher" <dpd@dpdtech.com> To: Alan Somers <asomers@freebsd.org> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: FreeBSD 10-stable (r274577) LACP / IEEE 802.3ad with TP-Link TL-SG2008 - not working Message-ID: <9AE69175-92D9-49FA-A651-119C7046A1FA@dpdtech.com> In-Reply-To: <CAOtMX2gEGxTyXjitBu=pjkteocp1pSGxnb%2BWDb_jL3f0YNOjrg@mail.gmail.com> References: <1A44709E-7D0C-4932-8A28-383EAC3F340B@dpdtech.com> <CAOtMX2gEGxTyXjitBu=pjkteocp1pSGxnb%2BWDb_jL3f0YNOjrg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_3AE43373-3AAC-42D5-8BEE-0F93BCFA1EDE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 4, 2014, at 12:50 PM, Alan Somers <asomers@freebsd.org> 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=92s LACP packets, but still = sees the TP-Link=92s packets. >=20 > 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. >=20 > -Alan 99% sure the switch is configured correctly. I=92ve actually tried all = the different combination of the switch supports, and can=92t seem to = get them to sync up. =46rom the pcaps, both the host and switch are = sending the LACP packets =85 but it seems that the freebsd is just = passing them through/up =85 almost like FreeBSD doesn=92t recognized = them as LACP packets.=20 In looking a bit deeper on the pcaps in wireshark - the TP-Link=92s = packet correctly labels the =93partner=94 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.=20 Feels like a single bit or flag in the switches packets that is not = matching what FreeBSD is expecting.=20 I was hoping someone would have some insight before I start looking at = each bit of the packets what=92s not aligned. - David P. Discher http://davidpdischer.com/ AIM: DavidDPD | Y!M: daviddpdz=20 --Apple-Mail=_3AE43373-3AAC-42D5-8BEE-0F93BCFA1EDE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUgM3VAAoJEEmwU6XuhYWOmDAH/2VpBGNYhLTvSPk3n4zd5UTj KxfiJvBG1JOldYs3PCjqeb+Eq/L+pdNACxS5SThQyxsqcjLmNLUtxrmBCBOcXh7P VpCDEq7U/n0XD0ANOt6uBBQOaiI6FaNutZ5iWF5HF4fTTbsAr5r7tN3ORRJpCIpo YzU479bH5oitO+cf31GNnis9MymoifKCzXtNIMzAplIfUNGoVQiSTKWQ5B22Z+KS Ab+LqXKgueVzdWaoWu9dejRXd7oUvUGYUL5olVl1vnJO3TK0LPnzOapEq7s4My/L i42ZoFNcBuzkDw7DaZ1mLi9CBivJ6j+2nsQPqRR9Bxo5j2E9PKwXGyIYLJiaRbc= =s63r -----END PGP SIGNATURE----- --Apple-Mail=_3AE43373-3AAC-42D5-8BEE-0F93BCFA1EDE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9AE69175-92D9-49FA-A651-119C7046A1FA>