Ben Greear <greearb@xxxxxxxxxxxxxxx> writes:No. I don't see a good reason to strip on ethX. That hardware accel VLANs strip
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?
I think that for Q in Q, we would need some explicit flag on each skb to know when to add or modifyOn 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,What benefit will this add? It will certainly decrease performance to copy around
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...