[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090208232655.GA12756@electric-eye.fr.zoreil.com>
Date: Mon, 9 Feb 2009 00:26:55 +0100
From: Francois Romieu <romieu@...zoreil.com>
To: Pierre Ossman <drzeus-list@...eus.cx>
Cc: netdev@...r.kernel.org, Patrick McHardy <kaber@...sh.net>
Subject: Re: accelerated vlan gives pcap tagged packets untagged
Pierre Ossman <drzeus-list@...eus.cx> :
[...]
> I assume this is because the hardware supports vlans and handles all
> the tag stripping.
Partly.
> (I've confirmed with tcpdump that the packets lack tags when they are
> presented to userspace)
>
> From what I can tell, I cannot fix this without rebuilding the kernel
> and removing the acceleration support from the r8169 driver. Is there
> some method I've overlooked?
>
> Preferably, I'd like the kernel to expose to pcap what's on the wire
> (i.e. accelerated vs non-accelerated looks the same from userspace). If
> that means too much processing to be desirable, the next best thing
> would be to simply not show tagged packets on the raw interface.
Your issue seems to be related to the commit below:
commit bc1d0411b804ad190cdadabac48a10067f17b9e6
Author: Patrick McHardy <kaber@...sh.net>
Date: Mon Jul 14 22:49:30 2008 -0700
vlan: deliver packets received with VLAN acceleration to network taps
When VLAN header stripping is used, packets currently bypass packet
sockets (and other network taps) completely. For locally existing
VLANs, they appear directly on the VLAN device, for unknown VLANs
they are silently dropped.
Add a new function netif_nit_deliver() to deliver incoming packets
to all network interface taps and use it in __vlan_hwaccel_rx() to
make VLAN packets visible on the underlying device.
Signed-off-by: Patrick McHardy <kaber@...sh.net>
Signed-off-by: David S. Miller <davem@...emloft.net>
I have no idea what could be the right solution. Patrick ?
--
Ueimor
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists