From owner-freebsd-net@FreeBSD.ORG Fri Jan 29 23:59:13 2010 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0ACFD1065672 for ; Fri, 29 Jan 2010 23:59:13 +0000 (UTC) (envelope-from jfb@mr-happy.com) Received: from vexbert.mr-paradox.net (vexbert.mr-paradox.net [IPv6:2001:470:b:28:f::1]) by mx1.freebsd.org (Postfix) with ESMTP id DF4688FC15 for ; Fri, 29 Jan 2010 23:59:12 +0000 (UTC) Received: from crow.mr-happy.com (crow.mr-happy.com [10.1.0.2]) by vexbert.mr-paradox.net (Postfix) with ESMTP id 0C076845AE; Fri, 29 Jan 2010 18:59:12 -0500 (EST) Received: by crow.mr-happy.com (Postfix, from userid 16139) id 6D647BAA8; Fri, 29 Jan 2010 18:59:11 -0500 (EST) Date: Fri, 29 Jan 2010 18:59:11 -0500 From: Jeff Blank To: Jack Vogel Message-ID: <20100129235911.GA67110@mr-happy.com> References: <201001291920.o0TJKAw9005498@freefall.freebsd.org> <2a41acea1001291447n5852f5b4h193d3ad6dff9faac@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2a41acea1001291447n5852f5b4h193d3ad6dff9faac@mail.gmail.com> X-Face: #0jV*~a}VtKS-&E/!EJpH('H1Va}24dxF0oT&+.R3Gu8C; xhSC+<|+H84&YLbMvphuRT4cp3.|8EN_(2Eix/6{.Up~u`a^}0Ln&b+9Fw|BPig@-{y\pL_46d&ZwA]5%_AU?}DezfE&1!>H?3E$!Yve7.O<+..Jnb4:'6Ey_]FtFzU9=*l$1p/@gA,Ze>^5<]+r(XJ+m7`/vMDc$'wy|`e X-Virus-Scanned: ClamAV 0.94.2/10342/Fri Jan 29 11:14:10 2010 on vexbert.mr-paradox.net X-Virus-Status: Clean Cc: FreeBSD Net Subject: Re: kern/141646: [em] em(4) + lagg(4) + vlan(4) generates ISL-tagged frames instead of 802.1q-tagged frames X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2010 23:59:13 -0000 On Fri, Jan 29, 2010 at 02:47:39PM -0800, Jack Vogel wrote: > What's with the encrypted messages entered in this bug suddenly? Just base64-encoded plain text--it appears GNATS is not base64-aware. To summarize (I received a copy directly), Mr. Anishchuk is experiencing the same problem and suggested a workaround (also posted to the list previously) involving "ifconfig_emN='-vlanhwtag up'" in rc.conf. He also seemed to think it was twice-Q-tagged frames rather than ISL-tagged frames, which does not match my packet captures. > An important update - I have root caused this. Turns out its kinda > interesting. > The reason there is a problem is due to the stacked pseudo devices, since > the vlan device is on lagg, and not directly on em, the em driver is not > getting > the "event" of the vlan attachment, and thus the vlan hw filter routine is > never > run, that routine sets a CRITICAL bit in the control register which > differentiates > between ISL and 802 tags... and thus our failure :( > The question now is what to do about this, I am thinking about this now.... Interesting indeed. I look forward to a fix (and have alternate interfaces and -vlanhwtag in the mean time). thanks, Jeff