From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 23 07:37:55 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 26A4D16A4CE for ; Tue, 23 Nov 2004 07:37:55 +0000 (GMT) Received: from corwin.easynet.fr (smarthost160.mail.easynet.fr [212.180.1.160]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B4C843D1D for ; Tue, 23 Nov 2004 07:37:54 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from [212.180.127.72] (helo=tatooine.tataz.chchile.org) by corwin.easynet.fr with esmtp (Exim 4.34) id 1CWVFH-0000Ia-7e; Tue, 23 Nov 2004 08:37:51 +0100 Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 7E9BF412C; Tue, 23 Nov 2004 08:37:41 +0100 (CET) Date: Tue, 23 Nov 2004 08:37:40 +0100 From: Jeremie Le Hen To: Iasen Kostov Message-ID: <20041123073740.GJ960@obiwan.tataz.chchile.org> References: <41A292D8.4050904@OTEL.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41A292D8.4050904@OTEL.net> User-Agent: Mutt/1.5.6i X-Broken-Reverse-DNS: no host name found for IP address 212.180.127.72 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 07:37:55 -0000 > 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 believe this has been fixed by Robert Watson one week ago, at least for the em(4) driver. I don't know anything about re(4). http://docs.freebsd.org/cgi/getmsg.cgi?fetch=291393+0+archive/2004/cvs-all/20041121.cvs-all Regards, -- Jeremie Le Hen jeremie@le-hen.org