networking/dsa/configuration.rst

34 The corresponding linux Ethernet interface is called the master interface.
37 The slave interfaces depend on the master interface being up in order for them
38 to send or receive traffic. Prior to kernel v5.12, the state of the master
42 - when a DSA slave interface is brought up, the master interface is
44 - when the master interface is brought down, all DSA slave interfaces are
50   the master interface
53   another master interface
99     # For kernels earlier than v5.12, the master interface needs to be
111     # For kernels earlier than v5.12, the master interface needs to be
124     ip link set dev lan1 master br0
125     ip link set dev lan2 master br0
126     ip link set dev lan3 master br0
137     # For kernels earlier than v5.12, the master interface needs to be
153     ip link set dev lan1 master br0
154     ip link set dev lan2 master br0
181     # For kernels earlier than v5.12, the master interface needs to be
200     ip link set dev lan1 master br0
201     ip link set dev lan2 master br0
202     ip link set dev lan3 master br0
224     # For kernels earlier than v5.12, the master interface needs to be
241     ip link set dev lan1 master br0
242     ip link set dev lan2 master br0
243     ip link set dev lan3 master br0
244     ip link set eth0.1 master br0
264     # For kernels earlier than v5.12, the master interface needs to be
282     ip link set dev wan master br0
283     ip link set eth0.1 master br0
284     ip link set dev lan1 master br0
285     ip link set dev lan2 master br0
305 on whether the ``self`` or ``master`` flags are being used, a ``bridge fdb
342 well as a new mode using the ``master`` flag which installs FDB entries in the
347     bridge fdb add dev swp0 00:01:02:03:04:05 master static
357     bridge fdb add dev swp0 00:01:02:03:04:05 master static
364 Script writers are therefore encouraged to use the ``master static`` set of
391 and DSA master will be used - the numerically first port from the firmware
396 changing the DSA master of a user port. The ``IFLA_DSA_MASTER`` u32 netlink
397 attribute contains the ifindex of the master device that handles each slave
398 device. The DSA master must be a valid candidate based on firmware node
406     # See the DSA master in current use
409         dsa master eth0
412     ip link set swp0 type dsa master eth1
413     ip link set swp1 type dsa master eth0
414     ip link set swp2 type dsa master eth1
415     ip link set swp3 type dsa master eth0
417     # CPU ports in LAG, using explicit assignment of the DSA master
419     ip link set eth1 down && ip link set eth1 master bond0
420     ip link set swp0 type dsa master bond0
421     ip link set swp1 type dsa master bond0
422     ip link set swp2 type dsa master bond0
423     ip link set swp3 type dsa master bond0
424     ip link set eth0 down && ip link set eth0 master bond0
427         dsa master bond0
429     # CPU ports in LAG, relying on implicit migration of the DSA master
431     ip link set eth0 down && ip link set eth0 master bond0
432     ip link set eth1 down && ip link set eth1 master bond0
435         dsa master bond0
439 reacts to the ``IFLA_MASTER`` attribute change of its present master (``eth0``)
442 that were assigned to this interface to the first physical DSA master which is
448 possible to statically assign a user port towards a DSA master that has any
449 upper interfaces (this includes LAG devices - the master must always be the LAG
452 Live changing of the DSA master (and thus CPU port) affinity of a user port is
456 used as a DSA master; however, DSA will reject a LAG interface as a valid
457 candidate for being a DSA master unless it has at least one physical DSA master