From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 25 15:19:10 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 34FE316A4CE; Thu, 25 Nov 2004 15:19:10 +0000 (GMT) Received: from mail.otel.net (gw3.OTEL.net [212.36.8.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64AF143D5D; Thu, 25 Nov 2004 15:19:09 +0000 (GMT) (envelope-from tbyte@OTEL.net) Received: from dragon.otel.net ([212.36.8.135]) by mail.otel.net with esmtp (Exim 4.30; FreeBSD) id 1CXLOj-000IQk-Rj; Thu, 25 Nov 2004 17:19:05 +0200 Message-ID: <41A5F7F5.5000000@OTEL.net> Date: Thu, 25 Nov 2004 17:19:17 +0200 From: Iasen Kostov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041117 X-Accept-Language: bg, en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: Thu, 25 Nov 2004 15:19:10 -0000 Robert Watson wrote: >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 > > > >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > > My if_em.c is 1.44.2.4 and if_em.h is 1.25.2.2 and the same happens again... I ran ping throu vlan device on one console and then start tcpdump on another console and the ping stops.