From: Vladimir Oltean <olteanv@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev <netdev@vger.kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: VLAN filtering with DSA
Date: Thu, 10 Sep 2020 22:08:17 +0300 [thread overview]
Message-ID: <20200910190817.xfckbgxxuzupmnhb@skbuf> (raw)
In-Reply-To: <7b23a257-6ac2-e6b2-7df8-9df28973e315@gmail.com>
On Thu, Sep 10, 2020 at 12:05:17PM -0700, Florian Fainelli wrote:
> On 9/10/2020 12:01 PM, Vladimir Oltean wrote:
> > On Thu, Sep 10, 2020 at 11:42:02AM -0700, Florian Fainelli wrote:
> > > On 9/10/2020 8:07 AM, Vladimir Oltean wrote:
> > > Yes, doing what you suggest would make perfect sense for a DSA master that
> > > is capable of VLAN filtering, I did encounter that problem with e1000 and
> > > the dsa-loop.c mockup driver while working on a mock-up 802.1Q data path.
> >
> > Yes, I have another patch where I add those VLANs from tag_8021q.c which
> > I did not show here.
> >
> > But if the DSA switch that uses tag_8021q is cascaded to another one,
> > that's of little use if the upper switch does not propagate that
> > configuration to its own upstream.
>
> Yes, that would not work. As soon as you have a bridge spanning any of those
> switches, does not the problem go away by virtue of the switch port forcing
> the DSA master/upstream to be in promiscuous mode?
Well, yes, bridged it works but standalone it doesn't. A bit strange if
you ask me.
-Vladimir
next prev parent reply other threads:[~2020-09-10 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 15:07 VLAN filtering with DSA Vladimir Oltean
2020-09-10 18:41 ` Florian Fainelli
2020-09-11 13:20 ` Ido Schimmel
2020-09-11 16:30 ` Vladimir Oltean
2020-09-11 16:32 ` Vladimir Oltean
2020-09-11 16:57 ` Florian Fainelli
2020-09-10 18:42 ` Florian Fainelli
2020-09-10 19:01 ` Vladimir Oltean
2020-09-10 19:05 ` Florian Fainelli
2020-09-10 19:08 ` Vladimir Oltean [this message]
2020-09-10 19:09 ` Florian Fainelli
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=20200910190817.xfckbgxxuzupmnhb@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.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;
as well as URLs for NNTP newsgroup(s).