Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Mar 2004 22:48:21 +0300
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:  <20040330194821.GA96878@ip.net.ua>
In-Reply-To: <200403301119.01357.jbarrett@amduat.net>
References:  <200403251118.40718.jbarrett@amduat.net> <200403290936.49345.jbarrett@amduat.net> <20040330103251.GA92824@ip.net.ua> <200403301119.01357.jbarrett@amduat.net>

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

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

On Tue, Mar 30, 2004 at 11:19:00AM -0800, Jacob S. Barrett wrote:
> Now what have I done wrong.  I noticed this yesterday and I can't figure =
out=20
> what I have done wrong.  VLAN tagged ARP requests coming into if_nge are =
not=20
> visible anymore (tcpdump).  Non VLAN tagged ARP requests are visible.  De=
bug=20
> statements are showing the frame doesn't make it into the driver.
>=20
Like I said in another email in this thread, if NIC is doing VLAN
stripping in firmware, you won't be able to see the original VLAN
packet with tcpdump(8) in 5.x.  Instead, it will be shown an inner
Ethernet packet on the physical ("parentdev") interface.  This can
be fixed.  But neither 4.x nor 5.x will show you the virgin VLAN
packet on output if the NIC does VLAN insertion in firmware.

> This is the request as it leaves the remote host.
> 11:04:53.588726 0:90:27:f4:58:1d ff:ff:ff:ff:ff:ff 8100 46: 802.1Q vlan#2=
 P0=20
> arp who-has 10.2.0.1 tell 10.2.0.2
>=20
> Strangely though, other broadcasts that are VLAN tagged get delivered to =
the=20
> driver. With your patch they now correctly show up on the ng_vlan interfa=
ce=20
> too.
>=20
> This is the other broadcast as sent by remote host:
> 0:90:27:f4:58:1d ff:ff:ff:ff:ff:ff 8100 257: 802.1Q vlan#2 P0 10.2.0.2.13=
8 >=20
> 10.2.0.255.138: NBT UDP PACKET(138)
>=20
> This is he above broadcast that was received by both if_nge and ng_vlan:
> 0:90:27:f4:58:1d ff:ff:ff:ff:ff:ff 0800 246: 10.2.0.2.138 > 10.2.0.255.13=
8:=20
> NBT UDP PACKET(138)
>=20
> Any idea why the ARP packets would be filtered at the NIC?
>=20
Hmm, this shouldn't happen.  Perhaps you have a firewall configured
to run at layer2 that rejects them?

> The same goes for=20
> ARP replies.  I can ARP request from the if_nge machine, but the replies =
get=20
> dropped.
>=20
If you set ARP entries manually, can you ping each other?


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

--ew6BAiZeqk4r7MaW
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAac8FUkv4P6juNwoRAvzuAKCA3RHJ78vMqnKoSrr3DdyCtdJZ5QCfUSyq
QVJY2kwTR2T29Yh3zj4Y9mw=
=Gsfu
-----END PGP SIGNATURE-----

--ew6BAiZeqk4r7MaW--



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