From owner-freebsd-current@FreeBSD.ORG Tue Nov 9 19:09:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A06616A517; Tue, 9 Nov 2004 19:09:10 +0000 (GMT) Received: from mail.otel.net (gw3.OTEL.net [212.36.8.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C0F843D48; Tue, 9 Nov 2004 19:09: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 1CRbMY-000F7z-FF; Tue, 09 Nov 2004 21:09:06 +0200 Message-ID: <419115D2.8040003@OTEL.net> Date: Tue, 09 Nov 2004 21:09:06 +0200 From: Iasen Kostov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041027 X-Accept-Language: bg, en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: em0, VLAN and bpf(?) trouble w/RELENG_5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2004 19:09:10 -0000 Robert Watson wrote: >On Mon, 8 Nov 2004 astesin@ukrtelecom.net wrote: > > > >>The problem. From time to time, vlan0 stops passing packets at all. At >>this moments, Catalyst stops seeing MAC of vlan0 (it's the same MAC as >>em0) in the mantione VLAN (untagged VLAN is also configured at em0 and >>works fine!). This means that `show mac-address-table vlan XX' command >>on Catalyst don't show the MAC. >> >>The problem can be easily repeated manually. It's enough just to issue a >>command like `trafshow -I vlan0' of `tcpdump -I vlan0' and voila! vlan0 >>is out of business, no packets are going through. >> >> > >Hmm. Could I get you to try/investigate a few things: > >(1) If you run tcpdump on the em0 interface itself, does the same thing > happen? > >(2) When vlan0 wedges, do you still see traffic on em0, and can you > generate traffic on em0 that's picked up by the switch? > >(3) Do other vlan pseudo-interfaces wedge under similar circumstances? > >(4) Could you try running with "debug.mpsafenet=0" in loader.conf (reboot > for it to take effect) and see if that makes a difference? > >(5) Does it matter whether you enter promiscuous mode using BPF -- i.e., > "tcpdump -p -i vlan0" vs w/o the -p flag? > >(6) When vlan0 is in the wedged condition, how "no packets" is it? Can > you send packets but not receieve, or receive packets and not send? > >Thanks! > >Robert N M Watson FreeBSD Core Team, TrustedBSD Projects >robert@fledge.watson.org Principal Research Scientist, McAfee Research > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > This seam to happen only with promiscuous mode set. It doesn't happen when you use -p with tcpdump or trafshow. I suspect that the problem is somewhere in hardware vlan tagging. Possibly in promiscuous mode driver thinks that the adapter tags/untags packets but it doesn't (just a thoght ...). regards.