[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3sl7idmb4.fsf@maximus.localdomain>
Date: Sat, 21 Jul 2007 13:32:31 +0200
From: Krzysztof Halasa <khc@...waw.pl>
To: Ben Greear <greearb@...delatech.com>
Cc: andrei radulescu-banu <iubica2@...oo.com>,
Stephen Hemminger <shemminger@...ux-foundation.org>,
Patrick McHardy <kaber@...sh.net>,
linux-kernel@...r.kernel.org,
Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: Linux, tcpdump and vlan
Ben Greear <greearb@...delatech.com> writes:
> There is already a flag you can set on vlan devices (reorder-header)
> that strips the VLAN tag before presenting it to user-space.
Sure, but isn't it only valid for VLAN device (not the main ethX)?
I.e., can you have the tag stripped from frames captured on ethX?
> On tx, if it shows up on the vlan device, we add that device's VID to
> the header if no VID is currently in the SKB. If it is in the SKB header
> we change the VID to be the tx dev's VID (if it was different). This allows user-space
> to send a raw ethernet frame on a vlan device and have it automatically
> go out of the box on the correct vlan. User-space can also send raw VLAN frames
> and have those also go out on the correct VLAN.
Well... I think the tag should be added unconditionally (for things like
QinQ) but that's trivial and minor.
IOW: I think all Ethernet interfaces should always be VLAN-aware,
stripping the tag (only one) early on RX and adding it late on TX.
That means tcpdump would see packets with exactly one tag removed
(unless there was no tag), in both RX and TX.
Tcpdump would need other means to get VLAN id...
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists