From owner-freebsd-net@FreeBSD.ORG Thu Mar 25 15:45:42 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 2FD5B16A4CE for ; Thu, 25 Mar 2004 15:45:42 -0800 (PST) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B2C843D1D for ; Thu, 25 Mar 2004 15:45:41 -0800 (PST) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id i2PNmYns027713 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Mar 2004 01:48:35 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.12.11/8.12.11) id i2PNjR6d007053; Fri, 26 Mar 2004 01:45:27 +0200 (EET) (envelope-from ru) Date: Fri, 26 Mar 2004 01:45:27 +0200 From: Ruslan Ermilov To: "Jacob S. Barrett" Message-ID: <20040325234527.GC85417@ip.net.ua> References: <200403251118.40718.jbarrett@amduat.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yLVHuoLXiP9kZBkt" Content-Disposition: inline In-Reply-To: <200403251118.40718.jbarrett@amduat.net> User-Agent: Mutt/1.5.6i X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp) cc: freebsd-net@freebsd.org Subject: Re: Disabling VLAN_HWTAGGING 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: Thu, 25 Mar 2004 23:45:42 -0000 --yLVHuoLXiP9kZBkt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 25, 2004 at 11:18:40AM -0800, Jacob S. Barrett wrote: > Can you disable VLAN_HWTAGGING? >=20 Not without modifying if_nge.c, but it should be pretty trivial. > I am seeing very strange behavior on a if_nge card with VLANs. If i try = and=20 > connect an if_vlan to it the kernel panics. If I connect a ng_vlan to it= =20 > tcpdump show that the tagged frames are "leaving" the if_nge interface, b= ut=20 > tcpdump running on a remote host that is crossed over (if_em) show no fra= mes=20 > leaving the if_nge. >=20 ng_vlan(4) doesn't provide support for hardware VLAN tagging for output frames -- it always emits ETHERTYPE_VLAN type Ethernet frames. > I am wondering if it is something to do VLAN_HWTAGGING. The if_em cards = I=20 > have don't do it and work fine, but the if_nge cards don't work at all. >=20 What FreeBSD version you're seeing the panic on? Cheers, --=20 Ruslan Ermilov FreeBSD committer ru@FreeBSD.org --yLVHuoLXiP9kZBkt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAY28XUkv4P6juNwoRAjDeAJ466Agw2B1lzxfob8G0jsEhAidvuQCeNCzx 5YOGpJGWVmxYtWolIkXvhnw= =7F2R -----END PGP SIGNATURE----- --yLVHuoLXiP9kZBkt--