From owner-freebsd-current@FreeBSD.ORG Tue Oct 12 13:24:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFB4616A4CE; Tue, 12 Oct 2004 13:24:17 +0000 (GMT) Received: from exchange.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4275B43D45; Tue, 12 Oct 2004 13:24:17 +0000 (GMT) (envelope-from don@sandvine.com) X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 12 Oct 2004 09:24:15 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Broadcom bge and 802.1Q vlan tags Thread-Index: AcSwXnxCbncPZDtUS7+L6FarwyfVqAAAFltg From: "Don Bowman" To: "Ruslan Ermilov" cc: freebsd-current@FreeBSD.org cc: Gleb Smirnoff Subject: RE: Broadcom bge and 802.1Q vlan tags X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2004 13:24:17 -0000 From: Ruslan Ermilov [mailto:ru@FreeBSD.org] > On Tue, Oct 12, 2004 at 08:32:38AM -0400, Don Bowman wrote: > > Roub?cek Zdenek: > > >=20 > > > Hello current > > >=20 > > > I have run into a problem with my Broadcom NIC (Dell=20 > > > LATITUDE D600). I am not able to detect 802.1Q tags on=20 > > > incoming interface with ethereal or tcpdump. All incoming=20 > > > packets seems like they are not coming through trunk but as=20 > > > native ETH frames, ie. the vlan tag is missing, probably=20 > > > removed before being passed to tcpdump? > >=20 > > ... > >=20 > > do you have if_vlan loaded? try 'kldload if_vlan'. > > This happens automatically if you create a vlan interface, but > > you may not have one if you are just sniffing. > >=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 > 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. I believe you can work around it by creating a vlan interface, even if not connected. that is, if its the same bug that i've run into with em.