Before patch, device sends a non 802.1Q frame, which is not what was wanted by user.
(Maybe he wants to check its device/network is able to transport 1522 bytes frames, who knows...) To use non tagged frames, user selects eth0 device, and to send tagged frames, he selects eth0.0 Now, maybe eth0 and eth0.0 should share same IP addresses, because incoming frame with ID=0 tag should be received by eth0 device, but I am not sure standard requires this.
-- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [email protected] majordomo info at you sure you actually want to do this? Frames received on VLAN 0 should be treated just as if they had no VLAN tag at all, except that they have an 802.1p value.
The current behaviour seems better to me since its symetrical to the output path, where the VLAN device is necessary to be able to specify a priority mapping.
While many refuse to use apps, more and more of the younger generation are using them and reaping the benefits.
It would be nice if the unsuspecting user was at least warned that their use of VLAN 0 is non-standard and may cause surprising results like leakage into the "native" VLAN.
That could be done in /sbin/ip or /sbin/vconfig, of course.
-- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [email protected] majordomo info at agree. Indicates that the tag header contains only priority information; no VLAN identifier is present in the frame. which implies that its valid to use 0 as tag in the header.