Date: Tue, 12 Oct 2004 16:49:13 +0200 From: =?us-ascii?Q?Roubicek_Zdenek_=28T-Systems_PragoNet=29?= <Zdenek.Roubicek@pragonet.cz> To: <freebsd-current@freebsd.org> Subject: RE: Broadcom bge and 802.1Q vlan tags Message-ID: <9256D57F598E6C41B288AA7DB94F29C902DFB98A@pgnmail1.pgnaplikace.cz>
next in thread | raw e-mail | index | archive | help
> On Tue, Oct 12, 2004 at 09:24:15AM -0400, Don Bowman wrote: > > From: Ruslan Ermilov [mailto:ru@FreeBSD.org] > > > On Tue, Oct 12, 2004 at 08:32:38AM -0400, Don Bowman wrote: > > > > Roub?cek Zdenek: > > > > >=20 > > > > ... > > > There appears to be a bug with drivers that support VLAN tag > > > striping in hardware in case no VLAN interfaces are configured. > > > In this case, ether_demux() will just proceed like if it was > > > an untagged Ethernet frame. glebius@ promised to fix this bug. > > >=20 I do not quite understand this statement.=20 Does this mean that in case I do not have VLAN configured (ifconfig vlan100 create etc.) - ether_demux() will not work for bge interface properly on trunk ports (seeing 802.1Q frames but expecting Ethernet II frames), this is what I would expect - or it will work OK, it is able to see all frames as EthernetII, since tag has been stripped off by underlying HW and I cannot distinguish which packet comes from which vlan > > > Zdenek, unfortunately, the bge(4) driver doesn't allow the > > > user to disable hardware vlan tag striping (like, e.g., the > > > em(4) driver allows), so you cannot watch VLAN frames on this > > > box using tcpdump or ethereal. Any chance for a change? Having the option to disable hw vlan striping would be handy. At least for me :) Thanks for the info so far. At least now I know it is not because of my hands. Zdenek
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9256D57F598E6C41B288AA7DB94F29C902DFB98A>