From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 23 22:30:00 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3231116A4CE for ; Tue, 23 Nov 2004 22:30:00 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE45743D41 for ; Tue, 23 Nov 2004 22:29:59 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iANMSDq6098611; Tue, 23 Nov 2004 17:28:13 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iANMSDCS098608; Tue, 23 Nov 2004 22:28:13 GMT (envelope-from robert@fledge.watson.org) Date: Tue, 23 Nov 2004 22:28:13 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Iasen Kostov In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: setting promisc mode kills vlans on devices with hwtagging (em, re ...) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Nov 2004 22:30:00 -0000 On Tue, 23 Nov 2004, Robert Watson wrote: > On Tue, 23 Nov 2004, Iasen Kostov wrote: > > > if you setup a vlan devices with parent one of emX or reX (this what I > > have at the moment) which has hardware vlan tagging just try to run > > tcpdump (without -p) and the vlans will die :). That doesn't happen with > > parent devices not supporting hwtagging. And this totally excludes > > possibility to run a bridge over vlans with parent device which support > > hwtaggs. And something else was observed with re driver - it is > > impossible to disable hwtaggs by -vlanhwtag neither you can disable vlan > > mtu :). > > I recently fixed this bug in if_em in HEAD, and will be merging that > back to RELENG_5 shortly. We plan to also merge the change to > RELENG_5_3 as an errata patch fix. It does not surprise me that if_re > has a similar bug; I'll look at abstracting the solution in the next > few days. I've now merged the fix to RELENG_5 from HEAD: Checking in if_em.c; /home/ncvs/src/sys/dev/em/if_em.c,v <-- if_em.c new revision: 1.44.2.4; previous revision: 1.44.2.3 done Checking in if_em.h; /home/ncvs/src/sys/dev/em/if_em.h,v <-- if_em.h new revision: 1.25.2.2; previous revision: 1.25.2.1 done I'll take a look at if_re shortly. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research