networking/dsa/configuration.rst

1 .. SPDX-License-Identifier: GPL-2.0
10 .. _dsa-config-showcases:
13 -----------------------
18 *single port*
19   Every switch port acts as a different configurable Ethernet port
22   Every switch port is part of one configurable Ethernet bridge
25   Every switch port except one upstream port is part of a configurable
27   The upstream port acts as different configurable Ethernet port.
32 Through DSA every port of a switch is handled like a normal linux Ethernet
33 interface. The CPU port is the switch port connected to an Ethernet MAC chip.
42 - when a DSA user interface is brought up, the conduit interface is
44 - when the conduit interface is brought down, all DSA user interfaces are
70 *single port*
71   * lan1: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3)
72   * lan2: 192.0.2.5/30 (192.0.2.4 - 192.0.2.7)
73   * lan3: 192.0.2.9/30 (192.0.2.8 - 192.0.2.11)
76   * br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255)
79   * br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255)
80   * wan: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3)
82 .. _dsa-tagged-configuration:
85 ----------------------------------
91 *single port*
92   .. code-block:: sh
109   .. code-block:: sh
135   .. code-block:: sh
146     # configure the upstream port
162 .. _dsa-vlan-configuration:
165 -------------------------------------
171 *single port*
174   .. code-block:: sh
176     # tag traffic on CPU port
219   .. code-block:: sh
221     # tag traffic on CPU port
258   .. code-block:: sh
260     # tag traffic on CPU port
300 ------------------------------------
313   .. code-block:: sh
322 to the host port). Instead, all FDB entries with the ``self`` flag (implicit or
325   .. code-block:: sh
345   .. code-block:: sh
353   .. code-block:: sh
368 -----------------------------------
370 Typically, DSA switches are attached to the host via a single Ethernet
376 statically assign the termination traffic associated with a certain user port
377 to be processed by a certain CPU port. This way, user space can implement
390 using the ``ethernet`` reference/phandle. At startup, only a single CPU port
391 and DSA conduit will be used - the numerically first port from the firmware
396 changing the DSA conduit of a user port. The ``IFLA_DSA_CONDUIT`` u32 netlink
404   .. code-block:: sh
407     ip -d link show dev swp0
411     # Static CPU port distribution
418     ip link add bond0 type bond mode balance-xor && ip link set bond0 up
425     ip -d link show dev swp0
430     ip link add bond0 type bond mode balance-xor && ip link set bond0 up
433     ip -d link show dev swp0
447 static user to CPU port assignment with LAG between DSA conduits. It is not
448 possible to statically assign a user port towards a DSA conduit that has any
449 upper interfaces (this includes LAG devices - the conduit must always be the LAG
452 Live changing of the DSA conduit (and thus CPU port) affinity of a user port is