networking/dsa/configuration.rst

34 The corresponding linux Ethernet interface is called the conduit interface.
37 The user interfaces depend on the conduit interface being up in order for them
38 to send or receive traffic. Prior to kernel v5.12, the state of the conduit
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
50   the conduit interface
53   another conduit interface
99     # For kernels earlier than v5.12, the conduit interface needs to be
111     # For kernels earlier than v5.12, the conduit interface needs to be
137     # For kernels earlier than v5.12, the conduit interface needs to be
181     # For kernels earlier than v5.12, the conduit interface needs to be
224     # For kernels earlier than v5.12, the conduit interface needs to be
264     # For kernels earlier than v5.12, the conduit interface needs to be
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
397 attribute contains the ifindex of the conduit device that handles each user
398 device. The DSA conduit must be a valid candidate based on firmware node
406     # See the DSA conduit in current use
417     # CPU ports in LAG, using explicit assignment of the DSA conduit
429     # CPU ports in LAG, relying on implicit migration of the DSA conduit
439 reacts to the ``IFLA_MASTER`` attribute change of its present conduit (``eth0``)
442 that were assigned to this interface to the first physical DSA conduit which is
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
456 used as a DSA conduit; however, DSA will reject a LAG interface as a valid
457 candidate for being a DSA conduit unless it has at least one physical DSA conduit