Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Mar 2004 11:19:00 -0800
From:      "Jacob S. Barrett" <jbarrett@amduat.net>
To:        Ruslan Ermilov <ru@freebsd.org>
Cc:        freebsd-net@freebsd.org
Subject:   Re: Disabling VLAN_HWTAGGING
Message-ID:  <200403301119.01357.jbarrett@amduat.net>
In-Reply-To: <20040330103251.GA92824@ip.net.ua>
References:  <200403251118.40718.jbarrett@amduat.net> <200403290936.49345.jbarrett@amduat.net> <20040330103251.GA92824@ip.net.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
Now what have I done wrong.  I noticed this yesterday and I can't figure out 
what I have done wrong.  VLAN tagged ARP requests coming into if_nge are not 
visible anymore (tcpdump).  Non VLAN tagged ARP requests are visible.  Debug 
statements are showing the frame doesn't make it into the driver.

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 
arp who-has 10.2.0.1 tell 10.2.0.2

Strangely though, other broadcasts that are VLAN tagged get delivered to the 
driver. With your patch they now correctly show up on the ng_vlan interface 
too.

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.138 > 
10.2.0.255.138: NBT UDP PACKET(138)

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.138: 
NBT UDP PACKET(138)

Any idea why the ARP packets would be filtered at the NIC?  The same goes for 
ARP replies.  I can ARP request from the if_nge machine, but the replies get 
dropped.

-- 
Jacob S. Barrett
jbarrett@amduat.net
www.amduat.net

"I don't suffer from insanity, I enjoy every minute of it."



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