3 messages, 2 authors, 2017-09-15 · open the first message on its own page
From: Pierre Colombier <hidden>
Date: 2017-09-14 19:21:16
Hello One big problem with vlans on linux is that the native interface always get all vlans. This can cause problem with bridges. One interesting feature would be to have a special vlan number (let's say 0 or -1 or 4097 ) designed so that it gets all the untagged trafic and only the untagged trafic. what do you think about this ?
From: Florian Fainelli <f.fainelli@gmail.com>
Date: 2017-09-14 22:16:38
On September 14, 2017 12:14:04 PM PDT, Pierre Colombier [off-list ref] wrote:
Hello One big problem with vlans on linux is that the native interface always get all vlans. This can cause problem with bridges.
What specific problem are you thinking about?
One interesting feature would be to have a special vlan number (let's say 0 or -1 or 4097 ) designed so that it gets all the untagged trafic and only the untagged trafic.
4097 is not a valid number nor is -1 since that closely follows what the VLAN ID extracted from the tag would be. VLAN 0 is more or less the untagged VLAN.
what do you think about this ?
Provided the HW supports it, with two netdevice operations: ndo_rx_vlan_add_vid and ndo_rx_vlan_kill_vid you can have your HW filter out the VLAN tags it wishes to receive, respectively not receive anymore. If your device does not support that, then yes if you send frames with a VLAN tag for which you are not interested in processing, you are still receiving it unless there is a switch or any kind of VLAN filtering device in between. Bridge has also gained a VLAN filtering that can also be used to only the reception/transmission of desired VLAN tags. And it also allows you to define the default VLAN tag (VID1) -- Florian
From: Pierre Colombier <hidden>
Date: 2017-09-15 13:02:06
quoted
One interesting feature would be to have a special vlan number (let's say 0 or -1 or 4097 ) designed so that it gets all the untagged trafic and only the untagged trafic.4097 is not a valid number nor is -1 since that closely follows what the VLAN ID extracted from the tag would be. VLAN 0 is more or less the untagged VLAN.
I know -1 or 4097 are invalid numbers This is precicely why i suggested them as "special" I wasn't aware of the existing Vlan 0 feature I just tried again and it seems to be exactly what I was requesting. What do you mean by "more or less" ?