Date: Fri, 26 Mar 2004 01:45:27 +0200 From: Ruslan Ermilov <ru@freebsd.org> To: "Jacob S. Barrett" <jbarrett@amduat.net> Cc: freebsd-net@freebsd.org Subject: Re: Disabling VLAN_HWTAGGING Message-ID: <20040325234527.GC85417@ip.net.ua> In-Reply-To: <200403251118.40718.jbarrett@amduat.net> References: <200403251118.40718.jbarrett@amduat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, Mar 25, 2004 at 11:18:40AM -0800, Jacob S. Barrett wrote: > Can you disable VLAN_HWTAGGING? > 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 > connect an if_vlan to it the kernel panics. If I connect a ng_vlan to it > tcpdump show that the tagged frames are "leaving" the if_nge interface, but > tcpdump running on a remote host that is crossed over (if_em) show no frames > leaving the if_nge. > 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 > have don't do it and work fine, but the if_nge cards don't work at all. > What FreeBSD version you're seeing the panic on? Cheers, -- Ruslan Ermilov FreeBSD committer ru@FreeBSD.org [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAY28XUkv4P6juNwoRAjDeAJ466Agw2B1lzxfob8G0jsEhAidvuQCeNCzx 5YOGpJGWVmxYtWolIkXvhnw= =7F2R -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040325234527.GC85417>