From: Florian Fainelli <f.fainelli@gmail.com>
To: Pierre Colombier <pierre@abeille.com>, netdev@vger.kernel.org
Subject: Re: feature request for kernel module 8021q
Date: Thu, 14 Sep 2017 15:16:32 -0700 [thread overview]
Message-ID: <A4D84B7F-5D4A-44C8-875C-C113D7C5C688@gmail.com> (raw)
In-Reply-To: <c010d65d-3050-8d88-22aa-cac092dd3904@abeille.com>
On September 14, 2017 12:14:04 PM PDT, Pierre Colombier <pierre@abeille.com> 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
next prev parent reply other threads:[~2017-09-14 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 19:14 feature request for kernel module 8021q Pierre Colombier
2017-09-14 22:16 ` Florian Fainelli [this message]
2017-09-15 13:02 ` Pierre Colombier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A4D84B7F-5D4A-44C8-875C-C113D7C5C688@gmail.com \
--to=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pierre@abeille.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox