Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Oct 2004 16:32:58 +0300
From:      Ruslan Ermilov <ru@freebsd.org>
To:        Don Bowman <don@sandvine.com>
Cc:        Gleb Smirnoff <glebius@freebsd.org>
Subject:   Re: Broadcom bge and 802.1Q vlan tags
Message-ID:  <20041012133258.GA84905@ip.net.ua>
In-Reply-To: <A8535F8D62F3644997E91F4F66E341FC9E34F8@exchange.sandvine.com>
References:  <A8535F8D62F3644997E91F4F66E341FC9E34F8@exchange.sandvine.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--45Z9DzgjV8m4Oswq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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
> > > >  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.
>=20
> 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.
>=20
Yes, sure.  But you still won't be able to see the VLAN frame
in this case (because VLAN information is stripped in h/w).


Cheers,
--=20
Ruslan Ermilov
ru@FreeBSD.org
FreeBSD committer

--45Z9DzgjV8m4Oswq
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBa90KqRfpzJluFF4RAuqPAJ4/3+eq3lqN/weXCSt7uhw6xa7q9wCgkLDZ
aMsCV8i+k/pbvhInTuX4cR8=
=tzc3
-----END PGP SIGNATURE-----

--45Z9DzgjV8m4Oswq--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041012133258.GA84905>