netdev - Re: [PATCH net-next v3 10/10] Documentation: net: dsa: sja1105: Add info about supported traffic modes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 5 May 2019 21:34:54 +0300
From:   Vladimir Oltean <olteanv@...il.com>
To:     Florian Fainelli <f.fainelli@...il.com>
Cc:     Vivien Didelot <vivien.didelot@...il.com>,
        Andrew Lunn <andrew@...n.ch>,
        "David S. Miller" <davem@...emloft.net>,
        netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next v3 10/10] Documentation: net: dsa: sja1105: Add
 info about supported traffic modes

On Sun, 5 May 2019 at 20:04, Florian Fainelli <f.fainelli@...il.com> wrote:
>
>
>
> On 5/5/2019 3:19 AM, Vladimir Oltean wrote:
> > This adds a table which illustrates what combinations of management /
> > regular traffic work depending on the state the switch ports are in.
> >
> > Signed-off-by: Vladimir Oltean <olteanv@...il.com>
>
> Reviewed-by: Florian Fainelli <f.fainelli@...il.com>
>
> I have finally put my brain on and understood what you meant with the
> vlan_filtering=1 case, which is quite similar, if not identical to what
> happens with DSA_TAG_PROTO_NONE where DSA slave network devices are
> simply conduit for offloading bridge operations and the data path
> continues to be on the DSA master device.
> --
> Florian

It is similar but not identical with DSA_TAG_PROTO_NONE. The
difference being that L2 multicast traffic still goes through DSA
slave netdevices, and that is exactly why I need the filtering
function.

-Vladimir