From owner-freebsd-net@FreeBSD.ORG Thu Dec 4 22:04:54 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B3F5564 for ; Thu, 4 Dec 2014 22:04:54 +0000 (UTC) Received: from mail.egr.msu.edu (gribble.egr.msu.edu [35.9.37.169]) by mx1.freebsd.org (Postfix) with ESMTP id C3632C97 for ; Thu, 4 Dec 2014 22:04:52 +0000 (UTC) Received: from gribble (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id 9F962191F2 for ; Thu, 4 Dec 2014 16:58:07 -0500 (EST) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by gribble (gribble.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78BNVAdmC3g2 for ; Thu, 4 Dec 2014 16:58:07 -0500 (EST) Received: from EGR authenticated sender Message-ID: <5480D8EF.9000804@egr.msu.edu> Date: Thu, 04 Dec 2014 16:58:07 -0500 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: FreeBSD 10-stable (r274577) LACP / IEEE 802.3ad with TP-Link TL-SG2008 - not working References: <1A44709E-7D0C-4932-8A28-383EAC3F340B@dpdtech.com> <9AE69175-92D9-49FA-A651-119C7046A1FA@dpdtech.com> In-Reply-To: <9AE69175-92D9-49FA-A651-119C7046A1FA@dpdtech.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Dec 2014 22:04:54 -0000 On 12/04/2014 16:10, David P. Discher wrote: > > On Dec 4, 2014, at 12:50 PM, Alan Somers 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 > Is the switch side set to "active" for the lacp mode (instead of passive)? Also, try: sysctl net.link.lagg.0.lacp.lacp_strict_mode=0 If either of those work, I'll explain more, don't have time to dig for old email right this minute.