From owner-freebsd-net@FreeBSD.ORG Wed Dec 1 19:40:38 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DA7316A4CE for ; Wed, 1 Dec 2004 19:40:38 +0000 (GMT) Received: from smtp.astra.net.uk (smtp.astra.net.uk [212.47.64.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85A2843D41 for ; Wed, 1 Dec 2004 19:40:37 +0000 (GMT) (envelope-from mike@nux.co.uk) Received: from imap.nux.co.uk (unknown [194.165.198.17]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client did not present a certificate) by smtp.astra.net.uk (Postfix) with ESMTP id CB7EB3BE23 for ; Wed, 1 Dec 2004 19:40:36 +0000 (GMT) Received: (qmail 2791 invoked from network); 1 Dec 2004 19:40:14 -0000 Received: from unknown (HELO black.eros.office) (192.168.5.130) by imap.nux.co.uk with AES256-SHA encrypted SMTP; 1 Dec 2004 19:40:14 -0000 Received: (qmail 60015 invoked by uid 2223); 1 Dec 2004 19:44:30 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Dec 2004 19:44:30 -0000 Date: Wed, 1 Dec 2004 19:44:30 +0000 (GMT) From: Mike Wolman X-X-Sender: mike@black.eros.office To: Max Laier In-Reply-To: <200412011906.23421.max@love2party.net> Message-ID: <20041201193034.Q59898@black.eros.office> References: <20041130204100.A50634@black.eros.office> <200412011906.23421.max@love2party.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-net@freebsd.org Subject: Re: em, vlan and pf troubles X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 19:40:38 -0000 Hi Max, No dhcp stuff is running on this box as a client or server on any interfaces. I can confirm running tcpdump does "mess" vlan stuff up. I am reluctant to try the updates as on: http://marc.theaimsgroup.com/?l=freebsd-net&m=110172867801777&w=2 as we have a lot more than 3 vlans and the box is in use. However i am willing to give it a go if it helps, is it as simple as grabbing the latest cvs files from src/sys/dev/em/* and doing a make buildkernel or do other parts of the tree need updating? Also i have had a look through the docs for the em driver but cannot see how to disable the hardware vlan tagging - does anybody know of is this possible? Mike. On Wed, 1 Dec 2004, Max Laier wrote: > On Tuesday 30 November 2004 22:17, Mike Wolman wrote: >> Hi, >> >> I am having a problem with 5.3 release with pf, vlans and the em device. > <...> >> I have had a hunt on the lists and found: >> >> http://marc.theaimsgroup.com/?l=freebsd-net&m=110172867801777&w=2 > > From what I know about this problem, it is possible that trying to analyze to > problem creates the problem in the first place. i.e. if you tcpdump on the > em-card (or the vlan for the same reason) it will screw up the vlan hardware > support. A fix has been committed, but it might be the case that the fix > wasn't 100% correct (esp. when there are 3+ vlans on the interface). > > Is is possible that you switched to dhcp for these boxes? If you run dhclient > on em0 it will open a bpf-socket which seems to be the root of the em+vlan > troubles. I doubt that pf plays a part in this game. > >> I am not sure if this is related but suspect it is - if so will adding a >> different card from a different vendor fix this? (the machine is at a >> remote location but if this will fix the problem off i go) > > Using a card w/o hardware supported vlan tagging might help, but you obviously > lose the benefit. I am not sure if you can turn off the h/w-support on the > em-card, but that's sure worth a try. Tell us if it helpped. > > -- > /"\ Best regards, | mlaier@freebsd.org > \ / Max Laier | ICQ #67774661 > X http://pf4freebsd.love2party.net/ | mlaier@EFnet > / \ ASCII Ribbon Campaign | Against HTML Mail and News >