Krzysztof Halasa wrote:
Another idea - perhaps we could make the software VLANs behave
the same as hw ones? I.e., stripping the tag on RX while setting
some magic skb field?
The packets could go via main interface first (normal path, with
eth_type_trans stripping the tag and setting protocol = some 802.1Q),
netif_rx | netif_receive_skb, then through the VLAN device with
finally eth_type_trans setting the IPv4 etc. protocol to pass to
L3 layers.
There is already a flag you can set on vlan devices (reorder-header)
that strips the VLAN tag before presenting it to user-space.
I can see potential problems on TX, the packets would have to be
presented without the tag (but with VLAN ID set somewhere in the skb)
and that probably means all drivers would have to be modified.
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.
Seems a bit of work, I know my message is missing the patch...
Unless I mis-understand, this has been working since 2.4 days :)
Ben
--
Ben Greear <[EMAIL PROTECTED]>
Candela Technologies Inc http://www.candelatech.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
