From owner-freebsd-net@FreeBSD.ORG Wed Dec 1 18:05:45 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 EEFCC16A4CE for ; Wed, 1 Dec 2004 18:05:45 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BC0743D55 for ; Wed, 1 Dec 2004 18:05:45 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CZYrI-00062e-00; Wed, 01 Dec 2004 19:05:44 +0100 Received: from [84.128.137.129] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CZYrH-0002Gt-00; Wed, 01 Dec 2004 19:05:44 +0100 From: Max Laier To: freebsd-net@freebsd.org Date: Wed, 1 Dec 2004 19:06:16 +0100 User-Agent: KMail/1.7.1 References: <20041130204100.A50634@black.eros.office> In-Reply-To: <20041130204100.A50634@black.eros.office> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2375476.OhgcbjOL2O"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412011906.23421.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: Mike Wolman 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 18:05:46 -0000 --nextPart2375476.OhgcbjOL2O Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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=3Dfreebsd-net&m=3D110172867801777&w=3D2 =46rom what I know about this problem, it is possible that trying to analyz= e to=20 problem creates the problem in the first place. i.e. if you tcpdump on the= =20 em-card (or the vlan for the same reason) it will screw up the vlan hardwar= e=20 support. A fix has been committed, but it might be the case that the fix=20 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 dhclie= nt=20 on em0 it will open a bpf-socket which seems to be the root of the em+vlan= =20 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 obviou= sly=20 lose the benefit. I am not sure if you can turn off the h/w-support on the= =20 em-card, but that's sure worth a try. Tell us if it helpped. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart2375476.OhgcbjOL2O Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBrggfXyyEoT62BG0RAk+7AJ9OCdbLotlEOZJQuThTj/6wotEB5wCeJGij q81ycBLqvoFYgLmRYOl/LuQ= =RZQE -----END PGP SIGNATURE----- --nextPart2375476.OhgcbjOL2O--