networking/dsa/configuration.rst

1 .. SPDX-License-Identifier: GPL-2.0
10 .. _dsa-config-showcases:
13 -----------------------
37 The user interfaces depend on the conduit interface being up in order for them
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
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 ----------------------------------
92   .. code-block:: sh
95     ip addr add 192.0.2.1/30 dev lan1
96     ip addr add 192.0.2.5/30 dev lan2
97     ip addr add 192.0.2.9/30 dev lan3
109   .. code-block:: sh
121     ip link add name br0 type bridge
123     # add ports to bridge
129     ip addr add 192.0.2.129/25 dev br0
135   .. code-block:: sh
147     ip addr add 192.0.2.1/30 dev wan
150     ip link add name br0 type bridge
152     # add ports to bridge
157     ip addr add 192.0.2.129/25 dev br0
162 .. _dsa-vlan-configuration:
165 -------------------------------------
174   .. code-block:: sh
176     # tag traffic on CPU port
177     ip link add link eth0 name eth0.1 type vlan id 1
178     ip link add link eth0 name eth0.2 type vlan id 2
179     ip link add link eth0 name eth0.3 type vlan id 3
194     ip link add name br0 type bridge
199     # add ports to bridges
204     # tag traffic on ports
205     bridge vlan add dev lan1 vid 1 pvid untagged
206     bridge vlan add dev lan2 vid 2 pvid untagged
207     bridge vlan add dev lan3 vid 3 pvid untagged
210     ip addr add 192.0.2.1/30 dev eth0.1
211     ip addr add 192.0.2.5/30 dev eth0.2
212     ip addr add 192.0.2.9/30 dev eth0.3
219   .. code-block:: sh
221     # tag traffic on CPU port
222     ip link add link eth0 name eth0.1 type vlan id 1
235     ip link add name br0 type bridge
240     # add ports to bridge
246     # tag traffic on ports
247     bridge vlan add dev lan1 vid 1 pvid untagged
248     bridge vlan add dev lan2 vid 1 pvid untagged
249     bridge vlan add dev lan3 vid 1 pvid untagged
252     ip addr add 192.0.2.129/25 dev br0
258   .. code-block:: sh
260     # tag traffic on CPU port
261     ip link add link eth0 name eth0.1 type vlan id 1
262     ip link add link eth0 name eth0.2 type vlan id 2
276     ip link add name br0 type bridge
281     # add ports to bridges
287     # tag traffic on ports
288     bridge vlan add dev lan1 vid 1 pvid untagged
289     bridge vlan add dev lan2 vid 1 pvid untagged
290     bridge vlan add dev wan vid 2 pvid untagged
293     ip addr add 192.0.2.1/30 dev eth0.2
294     ip addr add 192.0.2.129/25 dev br0
300 ------------------------------------
305 on whether the ``self`` or ``master`` flags are being used, a ``bridge fdb
306 add`` or ``bridge fdb del`` command acts upon entries from one or both tables).
313   .. code-block:: sh
315     bridge fdb add dev swp0 00:01:02:03:04:05 self static
317     bridge fdb add dev swp0 00:01:02:03:04:05 static
325   .. code-block:: sh
328     bridge fdb add dev swp0 00:01:02:03:04:05 static
330     bridge fdb add dev swp0 00:01:02:03:04:05 local
333     bridge fdb add dev swp0 00:01:02:03:04:05
345   .. code-block:: sh
347     bridge fdb add dev swp0 00:01:02:03:04:05 master static
353   .. code-block:: sh
357     bridge fdb add dev swp0 00:01:02:03:04:05 master static
360     bridge fdb add dev swp0 00:01:02:03:04:05
362     bridge fdb add dev swp0 00:01:02:03:04:05 static
365 flags when working with bridge FDB entries on DSA switch interfaces.
368 -----------------------------------
381 Secondly, it is possible to perform load balancing between CPU ports on a per
385 on the CPU ports facing the physical DSA conduits that constitute the LAG slave
391 and DSA conduit will be used - the numerically first port from the firmware
398 device. The DSA conduit must be a valid candidate based on firmware node
404   .. code-block:: sh
407     ip -d link show dev swp0
418     ip link add bond0 type bond mode balance-xor && ip link set bond0 up
425     ip -d link show dev swp0
429     # CPU ports in LAG, relying on implicit migration of the DSA conduit
430     ip link add bond0 type bond mode balance-xor && ip link set bond0 up
433     ip -d link show dev swp0
443 eligible, based on the firmware description (it effectively reverts to the
449 upper interfaces (this includes LAG devices - the conduit must always be the LAG