netdev - Re: [RFC PATCH v2 2/2] Documentation: net: dsa: b53: Describe b53 configuration

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] [day] [month] [year] [list]

Date:   Tue, 2 Jul 2019 18:28:34 +0200
From:   Benedikt Spranger <b.spranger@...utronix.de>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Florian Fainelli <f.fainelli@...il.com>, netdev@...r.kernel.org,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Kurt Kanzenbach <kurt@...utronix.de>,
        Vivien Didelot <vivien.didelot@...il.com>
Subject: Re: [RFC PATCH v2 2/2] Documentation: net: dsa: b53: Describe b53
 configuration

Am Mon, 1 Jul 2019 19:35:50 +0200
schrieb Andrew Lunn <andrew@...n.ch>:

> > +Configuration without tagging support
> > +-------------------------------------
> 
> How does this differ to the text you just added in the previous patch?
The b53 has some implementation specific detail:

The b53 DSA driver tags the CPU port in all VLANs, since otherwise any
PVID untagged VLAN programming would basically change the CPU port's
default PVID and make it untagged, undesirable.

This need some attention while configuring. Therefore the configuration
is slightly different to the generic one:

The following extra commands are needed on b53 single port and gateway
configuration:

  bridge vlan del dev lan1 vid 1
  bridge vlan del dev lan2 vid 1

On bridge config the following commands are not needed:

  bridge vlan add dev lan1 vid 1 pvid untagged
  bridge vlan add dev lan2 vid 1 pvid untagged
  bridge vlan add dev lan3 vid 1 pvid untagged

> Do we need both?
I like full configuration examples. But it can also be done by
describing the changes. I would prefer both - description and full
script:

...
Configuration without tagging support
-------------------------------------

Older models (5325, 5365) support a different tag format that is not
supported yet. 539x and 531x5 require managed mode and some special
handling, which is also not yet supported. The tagging support is
disabled in these cases and the switch need a different configuration.

The configuration slightly differ from
the :ref:`dsa-vlan-configuration`.

+ The b53 tags the CPU port in all VLANs, since otherwise any PVID
+ untagged VLAN programming would basically change the CPU port's
+ default PVID and make it untagged, undesirable.

+ In difference to the configuration described
+ in :ref:`dsa-vlan-configuration` the default VLAN 1 has to be removed
+ from the slave interface configuration in single port and gateway
+ configuration, while there is no need to add an extra VLAN
+ configuration in the bridge showcase.

single port
~~~~~~~~~~~
...

Regards
    Bene Spranger