€•ÃëŒsphinx.addnodes”Œdocument”“”)�”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)�”}”(hhh]”(hŒ pending_xref”“”)�”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…”�”}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ0/translations/zh_CN/networking/dsa/configuration”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)�”}”(hhh]”hŒChinese (Traditional)”…”�”}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/zh_TW/networking/dsa/configuration”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒItalian”…”�”}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/it_IT/networking/dsa/configuration”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒJapanese”…”�”}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/ja_JP/networking/dsa/configuration”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒKorean”…”�”}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/ko_KR/networking/dsa/configuration”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒPortuguese (Brazilian)”…”�”}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/pt_BR/networking/dsa/configuration”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒSpanish”…”�”}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ0/translations/sp_SP/networking/dsa/configuration”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒcomment”“”)�”}”(hŒ SPDX-License-Identifier: GPL-2.0”h]”hŒ SPDX-License-Identifier: GPL-2.0”…”�”}”hh·sbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1hµhhh²hh³ŒJ/var/lib/git/docbuild/linux/Documentation/networking/dsa/configuration.rst”h´KubhŒsection”“”)�”}”(hhh]”(hŒtitle”“”)�”}”(hŒ'DSA switch configuration from userspace”h]”hŒ'DSA switch configuration from userspace”…”�”}”(hhÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhÊh²hh³hÇh´KubhŒ paragraph”“”)�”}”(hŒŒThe DSA switch configuration is not integrated into the main userspace network configuration suites by now and has to be performed manually.”h]”hŒŒThe DSA switch configuration is not integrated into the main userspace network configuration suites by now and has to be performed manually.”…”�”}”(hhßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhhÊh²hubhŒtarget”“”)�”}”(hŒ.. _dsa-config-showcases:”h]”h}”(h]”h ]”h"]”h$]”h&]”Œrefid”Œdsa-config-showcases”uh1híh´K hhÊh²hh³hÇubhÉ)�”}”(hhh]”(hÎ)�”}”(hŒConfiguration showcases”h]”hŒConfiguration showcases”…”�”}”(hhþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhhûh²hh³hÇh´K ubhÞ)�”}”(hŒ—To configure a DSA switch a couple of commands need to be executed. In this documentation some common configuration scenarios are handled as showcases:”h]”hŒ—To configure a DSA switch a couple of commands need to be executed. In this documentation some common configuration scenarios are handled as showcases:”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khhûh²hubhŒdefinition_list”“”)�”}”(hhh]”(hŒdefinition_list_item”“”)�”}”(hŒO*single port* Every switch port acts as a different configurable Ethernet port ”h]”(hŒterm”“”)�”}”(hŒ *single port*”h]”hŒemphasis”“”)�”}”(hj)h]”hŒ single port”…”�”}”(hj-h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hj'ubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´Khj!ubhŒ definition”“”)�”}”(hhh]”hÞ)�”}”(hŒ@Every switch port acts as a different configurable Ethernet port”h]”hŒ@Every switch port acts as a different configurable Ethernet port”…”�”}”(hjEh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KhjBubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´Khjubj )�”}”(hŒG*bridge* Every switch port is part of one configurable Ethernet bridge ”h]”(j&)�”}”(hŒ*bridge*”h]”j,)�”}”(hjeh]”hŒbridge”…”�”}”(hjgh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hjcubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´Khj_ubjA)�”}”(hhh]”hÞ)�”}”(hŒ=Every switch port is part of one configurable Ethernet bridge”h]”hŒ=Every switch port is part of one configurable Ethernet bridge”…”�”}”(hj}h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khjzubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj_ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´Khjh²hubj )�”}”(hŒ *gateway* Every switch port except one upstream port is part of a configurable Ethernet bridge. The upstream port acts as different configurable Ethernet port. ”h]”(j&)�”}”(hŒ *gateway*”h]”j,)�”}”(hj�h]”hŒgateway”…”�”}”(hjŸh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hj›ubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´Khj—ubjA)�”}”(hhh]”hÞ)�”}”(hŒ•Every switch port except one upstream port is part of a configurable Ethernet bridge. The upstream port acts as different configurable Ethernet port.”h]”hŒ•Every switch port except one upstream port is part of a configurable Ethernet bridge. The upstream port acts as different configurable Ethernet port.”…”�”}”(hjµh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khj²ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj—ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´Khjh²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhhûh²hh³hÇh´NubhÞ)�”}”(hŒ…All configurations are performed with tools from iproute2, which is available at https://www.kernel.org/pub/linux/utils/net/iproute2/”h]”(hŒQAll configurations are performed with tools from iproute2, which is available at ”…”�”}”(hjÕh²hh³Nh´NubhŒ reference”“”)�”}”(hŒ4https://www.kernel.org/pub/linux/utils/net/iproute2/”h]”hŒ4https://www.kernel.org/pub/linux/utils/net/iproute2/”…”�”}”(hjßh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jáuh1jÝhjÕubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Khhûh²hubhÞ)�”}”(hX)Through DSA every port of a switch is handled like a normal linux Ethernet interface. The CPU port is the switch port connected to an Ethernet MAC chip. The corresponding linux Ethernet interface is called the conduit interface. All other corresponding linux interfaces are called user interfaces.”h]”hX)Through DSA every port of a switch is handled like a normal linux Ethernet interface. The CPU port is the switch port connected to an Ethernet MAC chip. The corresponding linux Ethernet interface is called the conduit interface. All other corresponding linux interfaces are called user interfaces.”…”�”}”(hjôh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K hhûh²hubhÞ)�”}”(hXThe user interfaces depend on the conduit interface being up in order for them to send or receive traffic. Prior to kernel v5.12, the state of the conduit interface had to be managed explicitly by the user. Starting with kernel v5.12, the behavior is as follows:”h]”hXThe user interfaces depend on the conduit interface being up in order for them to send or receive traffic. Prior to kernel v5.12, the state of the conduit interface had to be managed explicitly by the user. Starting with kernel v5.12, the behavior is as follows:”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K%hhûh²hubhŒ bullet_list”“”)�”}”(hhh]”(hŒ list_item”“”)�”}”(hŒ[when a DSA user interface is brought up, the conduit interface is automatically brought up.”h]”hÞ)�”}”(hŒ[when a DSA user interface is brought up, the conduit interface is automatically brought up.”h]”hŒ[when a DSA user interface is brought up, the conduit interface is automatically brought up.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K*hjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjh²hh³hÇh´Nubj)�”}”(hŒdwhen the conduit interface is brought down, all DSA user interfaces are automatically brought down. ”h]”hÞ)�”}”(hŒcwhen the conduit interface is brought down, all DSA user interfaces are automatically brought down.”h]”hŒcwhen the conduit interface is brought down, all DSA user interfaces are automatically brought down.”…”�”}”(hj3h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K,hj/ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjh²hh³hÇh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jh³hÇh´K*hhûh²hubhÞ)�”}”(hŒAIn this documentation the following Ethernet interfaces are used:”h]”hŒAIn this documentation the following Ethernet interfaces are used:”…”�”}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K/hhûh²hubj)�”}”(hhh]”(j )�”}”(hŒ*eth0* the conduit interface ”h]”(j&)�”}”(hŒ*eth0*”h]”j,)�”}”(hjfh]”hŒeth0”…”�”}”(hjhh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hjdubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´K2hj`ubjA)�”}”(hhh]”hÞ)�”}”(hŒthe conduit interface”h]”hŒthe conduit interface”…”�”}”(hj~h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K2hj{ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj`ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´K2hj]ubj )�”}”(hŒ!*eth1* another conduit interface ”h]”(j&)�”}”(hŒ*eth1*”h]”j,)�”}”(hjžh]”hŒeth1”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hjœubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´K5hj˜ubjA)�”}”(hhh]”hÞ)�”}”(hŒanother conduit interface”h]”hŒanother conduit interface”…”�”}”(hj¶h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K5hj³ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj˜ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´K5hj]h²hubj )�”}”(hŒ*lan1* a user interface ”h]”(j&)�”}”(hŒ*lan1*”h]”j,)�”}”(hjÖh]”hŒlan1”…”�”}”(hjØh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hjÔubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´K8hjÐubjA)�”}”(hhh]”hÞ)�”}”(hŒa user interface”h]”hŒa user interface”…”�”}”(hjîh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K8hjëubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hjÐubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´K8hj]h²hubj )�”}”(hŒ*lan2* another user interface ”h]”(j&)�”}”(hŒ*lan2*”h]”j,)�”}”(hjh]”hŒlan2”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´K;hjubjA)�”}”(hhh]”hÞ)�”}”(hŒanother user interface”h]”hŒanother user interface”…”�”}”(hj&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K;hj#ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´K;hj]h²hubj )�”}”(hŒ*lan3* a third user interface ”h]”(j&)�”}”(hŒ*lan3*”h]”j,)�”}”(hjFh]”hŒlan3”…”�”}”(hjHh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hjDubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´K>hj@ubjA)�”}”(hhh]”hÞ)�”}”(hŒa third user interface”h]”hŒa third user interface”…”�”}”(hj^h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K>hj[ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj@ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´K>hj]h²hubj )�”}”(hŒ6*wan* A user interface dedicated for upstream traffic ”h]”(j&)�”}”(hŒ*wan*”h]”j,)�”}”(hj~h]”hŒwan”…”�”}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hj|ubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´KAhjxubjA)�”}”(hhh]”hÞ)�”}”(hŒ/A user interface dedicated for upstream traffic”h]”hŒ/A user interface dedicated for upstream traffic”…”�”}”(hj–h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KAhj“ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hjxubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´KAhj]h²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhhûh²hh³hÇh´NubhÞ)�”}”(hŒ[Further Ethernet interfaces can be configured similar. The configured IPs and networks are:”h]”hŒ[Further Ethernet interfaces can be configured similar. The configured IPs and networks are:”…”�”}”(hj¶h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KChhûh²hubj)�”}”(hhh]”(j )�”}”(hŒ–*single port* * lan1: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3) * lan2: 192.0.2.5/30 (192.0.2.4 - 192.0.2.7) * lan3: 192.0.2.9/30 (192.0.2.8 - 192.0.2.11) ”h]”(j&)�”}”(hŒ *single port*”h]”j,)�”}”(hjÍh]”hŒ single port”…”�”}”(hjÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hjËubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´KIhjÇubjA)�”}”(hhh]”j)�”}”(hhh]”(j)�”}”(hŒ*lan1: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3)”h]”hÞ)�”}”(hjêh]”hŒ*lan1: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3)”…”�”}”(hjìh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KGhjèubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjåubj)�”}”(hŒ*lan2: 192.0.2.5/30 (192.0.2.4 - 192.0.2.7)”h]”hÞ)�”}”(hjh]”hŒ*lan2: 192.0.2.5/30 (192.0.2.4 - 192.0.2.7)”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KHhjÿubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjåubj)�”}”(hŒ,lan3: 192.0.2.9/30 (192.0.2.8 - 192.0.2.11) ”h]”hÞ)�”}”(hŒ+lan3: 192.0.2.9/30 (192.0.2.8 - 192.0.2.11)”h]”hŒ+lan3: 192.0.2.9/30 (192.0.2.8 - 192.0.2.11)”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KIhjubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjåubeh}”(h]”h ]”h"]”h$]”h&]”jMŒ*”uh1jh³hÇh´KGhjâubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hjÇubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´KIhjÄubj )�”}”(hŒ;*bridge* * br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255) ”h]”(j&)�”}”(hŒ*bridge*”h]”j,)�”}”(hjGh]”hŒbridge”…”�”}”(hjIh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hjEubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´KLhjAubjA)�”}”(hhh]”j)�”}”(hhh]”j)�”}”(hŒ0br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255) ”h]”hÞ)�”}”(hŒ/br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255)”h]”hŒ/br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255)”…”�”}”(hjfh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KLhjbubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj_ubah}”(h]”h ]”h"]”h$]”h&]”jMj4uh1jh³hÇh´KLhj\ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hjAubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´KLhjÄh²hubj )�”}”(hŒh*gateway* * br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255) * wan: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3) ”h]”(j&)�”}”(hŒ *gateway*”h]”j,)�”}”(hj’h]”hŒgateway”…”�”}”(hj”h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hj�ubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´KPhjŒubjA)�”}”(hhh]”j)�”}”(hhh]”(j)�”}”(hŒ/br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255)”h]”hÞ)�”}”(hj¯h]”hŒ/br0: 192.0.2.129/25 (192.0.2.128 - 192.0.2.255)”…”�”}”(hj±h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KOhj­ubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjªubj)�”}”(hŒ*wan: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3) ”h]”hÞ)�”}”(hŒ)wan: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3)”h]”hŒ)wan: 192.0.2.1/30 (192.0.2.0 - 192.0.2.3)”…”�”}”(hjÈh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KPhjÄubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjªubeh}”(h]”h ]”h"]”h$]”h&]”jMj4uh1jh³hÇh´KOhj§ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hjŒubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´KPhjÄh²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhhûh²hh³Nh´Nubhî)�”}”(hŒ.. _dsa-tagged-configuration:”h]”h}”(h]”h ]”h"]”h$]”h&]”hùŒdsa-tagged-configuration”uh1híh´KRhhûh²hh³hÇubeh}”(h]”(Œconfiguration-showcases”húeh ]”h"]”(Œconfiguration showcases”Œdsa-config-showcases”eh$]”h&]”uh1hÈhhÊh²hh³hÇh´K Œexpect_referenced_by_name”}”jhïsŒexpect_referenced_by_id”}”húhïsubhÉ)�”}”(hhh]”(hÎ)�”}”(hŒ"Configuration with tagging support”h]”hŒ"Configuration with tagging support”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj h²hh³hÇh´KUubhÞ)�”}”(hŒÃThe tagging based configuration is desired and supported by the majority of DSA switches. These switches are capable to tag incoming and outgoing traffic without using a VLAN based configuration.”h]”hŒÃThe tagging based configuration is desired and supported by the majority of DSA switches. These switches are capable to tag incoming and outgoing traffic without using a VLAN based configuration.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´KWhj h²hubj)�”}”(hhh]”(j )�”}”(hX›*single port* .. code-block:: sh # configure each interface ip addr add 192.0.2.1/30 dev lan1 ip addr add 192.0.2.5/30 dev lan2 ip addr add 192.0.2.9/30 dev lan3 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up ”h]”(j&)�”}”(hŒ *single port*”h]”j,)�”}”(hj4h]”hŒ single port”…”�”}”(hj6h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hj2ubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´Kjhj.ubjA)�”}”(hhh]”hŒ literal_block”“”)�”}”(hXb# configure each interface ip addr add 192.0.2.1/30 dev lan1 ip addr add 192.0.2.5/30 dev lan2 ip addr add 192.0.2.9/30 dev lan3 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up”h]”hXb# configure each interface ip addr add 192.0.2.1/30 dev lan1 ip addr add 192.0.2.5/30 dev lan2 ip addr add 192.0.2.9/30 dev lan3 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up”…”�”}”hjNsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆŒforce”‰Œlanguage”Œsh”Œhighlight_args”}”uh1jLh³hÇh´K\hjIubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj.ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´Kjhj+ubj )�”}”(hX2*bridge* .. code-block:: sh # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up # create bridge ip link add name br0 type bridge # add ports to bridge ip link set dev lan1 master br0 ip link set dev lan2 master br0 ip link set dev lan3 master br0 # configure the bridge ip addr add 192.0.2.129/25 dev br0 # bring up the bridge ip link set dev br0 up ”h]”(j&)�”}”(hŒ*bridge*”h]”j,)�”}”(hjsh]”hŒbridge”…”�”}”(hjuh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hjqubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´K„hjmubjA)�”}”(hhh]”jM)�”}”(hXò# For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up # create bridge ip link add name br0 type bridge # add ports to bridge ip link set dev lan1 master br0 ip link set dev lan2 master br0 ip link set dev lan3 master br0 # configure the bridge ip addr add 192.0.2.129/25 dev br0 # bring up the bridge ip link set dev br0 up”h]”hXò# For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up # create bridge ip link add name br0 type bridge # add ports to bridge ip link set dev lan1 master br0 ip link set dev lan2 master br0 ip link set dev lan3 master br0 # configure the bridge ip addr add 192.0.2.129/25 dev br0 # bring up the bridge ip link set dev br0 up”…”�”}”hj‹sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆj\‰j]Œsh”j_}”uh1jLh³hÇh´Kmhjˆubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hjmubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´K„hj+h²hubj )�”}”(hXT*gateway* .. code-block:: sh # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up # bring up the user interfaces ip link set wan up ip link set lan1 up ip link set lan2 up # configure the upstream port ip addr add 192.0.2.1/30 dev wan # create bridge ip link add name br0 type bridge # add ports to bridge ip link set dev lan1 master br0 ip link set dev lan2 master br0 # configure the bridge ip addr add 192.0.2.129/25 dev br0 # bring up the bridge ip link set dev br0 up ”h]”(j&)�”}”(hŒ *gateway*”h]”j,)�”}”(hj­h]”hŒgateway”…”�”}”(hj¯h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hj«ubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´K hj§ubjA)�”}”(hhh]”jM)�”}”(hX# For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up # bring up the user interfaces ip link set wan up ip link set lan1 up ip link set lan2 up # configure the upstream port ip addr add 192.0.2.1/30 dev wan # create bridge ip link add name br0 type bridge # add ports to bridge ip link set dev lan1 master br0 ip link set dev lan2 master br0 # configure the bridge ip addr add 192.0.2.129/25 dev br0 # bring up the bridge ip link set dev br0 up”h]”hX# For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up # bring up the user interfaces ip link set wan up ip link set lan1 up ip link set lan2 up # configure the upstream port ip addr add 192.0.2.1/30 dev wan # create bridge ip link add name br0 type bridge # add ports to bridge ip link set dev lan1 master br0 ip link set dev lan2 master br0 # configure the bridge ip addr add 192.0.2.129/25 dev br0 # bring up the bridge ip link set dev br0 up”…”�”}”hjÅsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆj\‰j]Œsh”j_}”uh1jLh³hÇh´K‡hjÂubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj§ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´K hj+h²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj h²hh³Nh´Nubhî)�”}”(hŒ.. _dsa-vlan-configuration:”h]”h}”(h]”h ]”h"]”h$]”h&]”hùŒdsa-vlan-configuration”uh1híh´K¢hj h²hh³hÇubeh}”(h]”(Œ"configuration-with-tagging-support”jþeh ]”h"]”(Œ"configuration with tagging support”Œdsa-tagged-configuration”eh$]”h&]”uh1hÈhhÊh²hh³hÇh´KUj}”jøjôsj }”jþjôsubhÉ)�”}”(hhh]”(hÎ)�”}”(hŒ%Configuration without tagging support”h]”hŒ%Configuration without tagging support”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjýh²hh³hÇh´K¥ubhÞ)�”}”(hŒ•A minority of switches are not capable to use a taging protocol (DSA_TAG_PROTO_NONE). These switches can be configured by a VLAN based configuration.”h]”hŒ•A minority of switches are not capable to use a taging protocol (DSA_TAG_PROTO_NONE). These switches can be configured by a VLAN based configuration.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K§hjýh²hubj)�”}”(hhh]”(j )�”}”(hXÇ*single port* The configuration can only be set up via VLAN tagging and bridge setup. .. code-block:: sh # tag traffic on CPU port ip link add link eth0 name eth0.1 type vlan id 1 ip link add link eth0 name eth0.2 type vlan id 2 ip link add link eth0 name eth0.3 type vlan id 3 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up ip link set eth0.1 up ip link set eth0.2 up ip link set eth0.3 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up # create bridge ip link add name br0 type bridge # activate VLAN filtering ip link set dev br0 type bridge vlan_filtering 1 # add ports to bridges ip link set dev lan1 master br0 ip link set dev lan2 master br0 ip link set dev lan3 master br0 # tag traffic on ports bridge vlan add dev lan1 vid 1 pvid untagged bridge vlan add dev lan2 vid 2 pvid untagged bridge vlan add dev lan3 vid 3 pvid untagged # configure the VLANs ip addr add 192.0.2.1/30 dev eth0.1 ip addr add 192.0.2.5/30 dev eth0.2 ip addr add 192.0.2.9/30 dev eth0.3 # bring up the bridge devices ip link set br0 up ”h]”(j&)�”}”(hŒ *single port*”h]”j,)�”}”(hj%h]”hŒ single port”…”�”}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hj#ubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´KØhjubjA)�”}”(hhh]”(hÞ)�”}”(hŒGThe configuration can only be set up via VLAN tagging and bridge setup.”h]”hŒGThe configuration can only be set up via VLAN tagging and bridge setup.”…”�”}”(hj=h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´K¬hj:ubjM)�”}”(hX# tag traffic on CPU port ip link add link eth0 name eth0.1 type vlan id 1 ip link add link eth0 name eth0.2 type vlan id 2 ip link add link eth0 name eth0.3 type vlan id 3 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up ip link set eth0.1 up ip link set eth0.2 up ip link set eth0.3 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up # create bridge ip link add name br0 type bridge # activate VLAN filtering ip link set dev br0 type bridge vlan_filtering 1 # add ports to bridges ip link set dev lan1 master br0 ip link set dev lan2 master br0 ip link set dev lan3 master br0 # tag traffic on ports bridge vlan add dev lan1 vid 1 pvid untagged bridge vlan add dev lan2 vid 2 pvid untagged bridge vlan add dev lan3 vid 3 pvid untagged # configure the VLANs ip addr add 192.0.2.1/30 dev eth0.1 ip addr add 192.0.2.5/30 dev eth0.2 ip addr add 192.0.2.9/30 dev eth0.3 # bring up the bridge devices ip link set br0 up”h]”hX# tag traffic on CPU port ip link add link eth0 name eth0.1 type vlan id 1 ip link add link eth0 name eth0.2 type vlan id 2 ip link add link eth0 name eth0.3 type vlan id 3 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up ip link set eth0.1 up ip link set eth0.2 up ip link set eth0.3 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up # create bridge ip link add name br0 type bridge # activate VLAN filtering ip link set dev br0 type bridge vlan_filtering 1 # add ports to bridges ip link set dev lan1 master br0 ip link set dev lan2 master br0 ip link set dev lan3 master br0 # tag traffic on ports bridge vlan add dev lan1 vid 1 pvid untagged bridge vlan add dev lan2 vid 2 pvid untagged bridge vlan add dev lan3 vid 3 pvid untagged # configure the VLANs ip addr add 192.0.2.1/30 dev eth0.1 ip addr add 192.0.2.5/30 dev eth0.2 ip addr add 192.0.2.9/30 dev eth0.3 # bring up the bridge devices ip link set br0 up”…”�”}”hjKsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆj\‰j]Œsh”j_}”uh1jLh³hÇh´K®hj:ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j@hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´KØhjubj )�”}”(hX±*bridge* .. code-block:: sh # tag traffic on CPU port ip link add link eth0 name eth0.1 type vlan id 1 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up ip link set eth0.1 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up # create bridge ip link add name br0 type bridge # activate VLAN filtering ip link set dev br0 type bridge vlan_filtering 1 # add ports to bridge ip link set dev lan1 master br0 ip link set dev lan2 master br0 ip link set dev lan3 master br0 ip link set eth0.1 master br0 # tag traffic on ports 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 # configure the bridge ip addr add 192.0.2.129/25 dev br0 # bring up the bridge ip link set dev br0 up ”h]”(j&)�”}”(hŒ*bridge*”h]”j,)�”}”(hjmh]”hŒbridge”…”�”}”(hjoh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hjkubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´KÿhjgubjA)�”}”(hhh]”jM)�”}”(hX]# tag traffic on CPU port ip link add link eth0 name eth0.1 type vlan id 1 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up ip link set eth0.1 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up # create bridge ip link add name br0 type bridge # activate VLAN filtering ip link set dev br0 type bridge vlan_filtering 1 # add ports to bridge ip link set dev lan1 master br0 ip link set dev lan2 master br0 ip link set dev lan3 master br0 ip link set eth0.1 master br0 # tag traffic on ports 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 # configure the bridge ip addr add 192.0.2.129/25 dev br0 # bring up the bridge ip link set dev br0 up”h]”hX]# tag traffic on CPU port ip link add link eth0 name eth0.1 type vlan id 1 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up ip link set eth0.1 up # bring up the user interfaces ip link set lan1 up ip link set lan2 up ip link set lan3 up # create bridge ip link add name br0 type bridge # activate VLAN filtering ip link set dev br0 type bridge vlan_filtering 1 # add ports to bridge ip link set dev lan1 master br0 ip link set dev lan2 master br0 ip link set dev lan3 master br0 ip link set eth0.1 master br0 # tag traffic on ports 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 # configure the bridge ip addr add 192.0.2.129/25 dev br0 # bring up the bridge ip link set dev br0 up”…”�”}”hj…sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆj\‰j]Œsh”j_}”uh1jLh³hÇh´KÛhj‚ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hjgubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´Kÿhjh²hubj )�”}”(hX$*gateway* .. code-block:: sh # tag traffic on CPU port ip link add link eth0 name eth0.1 type vlan id 1 ip link add link eth0 name eth0.2 type vlan id 2 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up ip link set eth0.1 up ip link set eth0.2 up # bring up the user interfaces ip link set wan up ip link set lan1 up ip link set lan2 up # create bridge ip link add name br0 type bridge # activate VLAN filtering ip link set dev br0 type bridge vlan_filtering 1 # add ports to bridges ip link set dev wan master br0 ip link set eth0.1 master br0 ip link set dev lan1 master br0 ip link set dev lan2 master br0 # tag traffic on ports bridge vlan add dev lan1 vid 1 pvid untagged bridge vlan add dev lan2 vid 1 pvid untagged bridge vlan add dev wan vid 2 pvid untagged # configure the VLANs ip addr add 192.0.2.1/30 dev eth0.2 ip addr add 192.0.2.129/25 dev br0 # bring up the bridge devices ip link set br0 up ”h]”(j&)�”}”(hŒ *gateway*”h]”j,)�”}”(hj§h]”hŒgateway”…”�”}”(hj©h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j+hj¥ubah}”(h]”h ]”h"]”h$]”h&]”uh1j%h³hÇh´M)hj¡ubjA)�”}”(hhh]”jM)�”}”(hXÉ# tag traffic on CPU port ip link add link eth0 name eth0.1 type vlan id 1 ip link add link eth0 name eth0.2 type vlan id 2 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up ip link set eth0.1 up ip link set eth0.2 up # bring up the user interfaces ip link set wan up ip link set lan1 up ip link set lan2 up # create bridge ip link add name br0 type bridge # activate VLAN filtering ip link set dev br0 type bridge vlan_filtering 1 # add ports to bridges ip link set dev wan master br0 ip link set eth0.1 master br0 ip link set dev lan1 master br0 ip link set dev lan2 master br0 # tag traffic on ports bridge vlan add dev lan1 vid 1 pvid untagged bridge vlan add dev lan2 vid 1 pvid untagged bridge vlan add dev wan vid 2 pvid untagged # configure the VLANs ip addr add 192.0.2.1/30 dev eth0.2 ip addr add 192.0.2.129/25 dev br0 # bring up the bridge devices ip link set br0 up”h]”hXÉ# tag traffic on CPU port ip link add link eth0 name eth0.1 type vlan id 1 ip link add link eth0 name eth0.2 type vlan id 2 # For kernels earlier than v5.12, the conduit interface needs to be # brought up manually before the user ports. ip link set eth0 up ip link set eth0.1 up ip link set eth0.2 up # bring up the user interfaces ip link set wan up ip link set lan1 up ip link set lan2 up # create bridge ip link add name br0 type bridge # activate VLAN filtering ip link set dev br0 type bridge vlan_filtering 1 # add ports to bridges ip link set dev wan master br0 ip link set eth0.1 master br0 ip link set dev lan1 master br0 ip link set dev lan2 master br0 # tag traffic on ports bridge vlan add dev lan1 vid 1 pvid untagged bridge vlan add dev lan2 vid 1 pvid untagged bridge vlan add dev wan vid 2 pvid untagged # configure the VLANs ip addr add 192.0.2.1/30 dev eth0.2 ip addr add 192.0.2.129/25 dev br0 # bring up the bridge devices ip link set br0 up”…”�”}”hj¿sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆj\‰j]Œsh”j_}”uh1jLh³hÇh´Mhj¼ubah}”(h]”h ]”h"]”h$]”h&]”uh1j@hj¡ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jh³hÇh´M)hjh²hubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhjýh²hh³Nh´Nubeh}”(h]”(Œ%configuration-without-tagging-support”jñeh ]”h"]”(Œ%configuration without tagging support”Œdsa-vlan-configuration”eh$]”h&]”uh1hÈhhÊh²hh³hÇh´K¥j}”jçjçsj }”jñjçsubhÉ)�”}”(hhh]”(hÎ)�”}”(hŒ$Forwarding database (FDB) management”h]”hŒ$Forwarding database (FDB) management”…”�”}”(hjïh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhjìh²hh³hÇh´M,ubhÞ)�”}”(hX‚The existing DSA switches do not have the necessary hardware support to keep the software FDB of the bridge in sync with the hardware tables, so the two tables are managed separately (``bridge fdb show`` queries both, and depending on whether the ``self`` or ``master`` flags are being used, a ``bridge fdb add`` or ``bridge fdb del`` command acts upon entries from one or both tables).”h]”(hŒ¸The existing DSA switches do not have the necessary hardware support to keep the software FDB of the bridge in sync with the hardware tables, so the two tables are managed separately (”…”�”}”(hjýh²hh³Nh´NubhŒliteral”“”)�”}”(hŒ``bridge fdb show``”h]”hŒbridge fdb show”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjýubhŒ, queries both, and depending on whether the ”…”�”}”(hjýh²hh³Nh´Nubj)�”}”(hŒ``self``”h]”hŒself”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjýubhŒ or ”…”�”}”(hjýh²hh³Nh´Nubj)�”}”(hŒ ``master``”h]”hŒmaster”…”�”}”(hj+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjýubhŒ flags are being used, a ”…”�”}”(hjýh²hh³Nh´Nubj)�”}”(hŒ``bridge fdb add``”h]”hŒbridge fdb add”…”�”}”(hj=h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjýubhŒ or ”…”�”}”hjýsbj)�”}”(hŒ``bridge fdb del``”h]”hŒbridge fdb del”…”�”}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjýubhŒ4 command acts upon entries from one or both tables).”…”�”}”(hjýh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M.hjìh²hubhÞ)�”}”(hŒöUp until kernel v4.14, DSA only supported user space management of bridge FDB entries using the bridge bypass operations (which do not update the software FDB, just the hardware one) using the ``self`` flag (which is optional and can be omitted).”h]”(hŒÁUp until kernel v4.14, DSA only supported user space management of bridge FDB entries using the bridge bypass operations (which do not update the software FDB, just the hardware one) using the ”…”�”}”(hjgh²hh³Nh´Nubj)�”}”(hŒ``self``”h]”hŒself”…”�”}”(hjoh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjgubhŒ- flag (which is optional and can be omitted).”…”�”}”(hjgh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M4hjìh²hubhŒ block_quote”“”)�”}”(hŒ�.. code-block:: sh bridge fdb add dev swp0 00:01:02:03:04:05 self static # or shorthand bridge fdb add dev swp0 00:01:02:03:04:05 static ”h]”jM)�”}”(hŒubridge fdb add dev swp0 00:01:02:03:04:05 self static # or shorthand bridge fdb add dev swp0 00:01:02:03:04:05 static”h]”hŒubridge fdb add dev swp0 00:01:02:03:04:05 self static # or shorthand bridge fdb add dev swp0 00:01:02:03:04:05 static”…”�”}”hj�sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆj\‰j]Œsh”j_}”uh1jLh³hÇh´M9hj‰ubah}”(h]”h ]”h"]”h$]”h&]”uh1j‡h³hÇh´M9hjìh²hubhÞ)�”}”(hXDue to a bug, the bridge bypass FDB implementation provided by DSA did not distinguish between ``static`` and ``local`` FDB entries (``static`` are meant to be forwarded, while ``local`` are meant to be locally terminated, i.e. sent to the host port). Instead, all FDB entries with the ``self`` flag (implicit or explicit) are treated by DSA as ``static`` even if they are ``local``.”h]”(hŒ_Due to a bug, the bridge bypass FDB implementation provided by DSA did not distinguish between ”…”�”}”(hj£h²hh³Nh´Nubj)�”}”(hŒ ``static``”h]”hŒstatic”…”�”}”(hj«h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj£ubhŒ and ”…”�”}”(hj£h²hh³Nh´Nubj)�”}”(hŒ ``local``”h]”hŒlocal”…”�”}”(hj½h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj£ubhŒ FDB entries (”…”�”}”(hj£h²hh³Nh´Nubj)�”}”(hŒ ``static``”h]”hŒstatic”…”�”}”(hjÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj£ubhŒ" are meant to be forwarded, while ”…”�”}”(hj£h²hh³Nh´Nubj)�”}”(hŒ ``local``”h]”hŒlocal”…”�”}”(hjáh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj£ubhŒd are meant to be locally terminated, i.e. sent to the host port). Instead, all FDB entries with the ”…”�”}”(hj£h²hh³Nh´Nubj)�”}”(hŒ``self``”h]”hŒself”…”�”}”(hjóh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj£ubhŒ3 flag (implicit or explicit) are treated by DSA as ”…”�”}”(hj£h²hh³Nh´Nubj)�”}”(hŒ ``static``”h]”hŒstatic”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj£ubhŒ even if they are ”…”�”}”(hj£h²hh³Nh´Nubj)�”}”(hŒ ``local``”h]”hŒlocal”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj£ubhŒ.”…”�”}”(hj£h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M?hjìh²hubjˆ)�”}”(hX[.. code-block:: sh # This command: bridge fdb add dev swp0 00:01:02:03:04:05 static # behaves the same for DSA as this command: bridge fdb add dev swp0 00:01:02:03:04:05 local # or shorthand, because the 'local' flag is implicit if 'static' is not # specified, it also behaves the same as: bridge fdb add dev swp0 00:01:02:03:04:05 ”h]”jM)�”}”(hX8# This command: bridge fdb add dev swp0 00:01:02:03:04:05 static # behaves the same for DSA as this command: bridge fdb add dev swp0 00:01:02:03:04:05 local # or shorthand, because the 'local' flag is implicit if 'static' is not # specified, it also behaves the same as: bridge fdb add dev swp0 00:01:02:03:04:05”h]”hX8# This command: bridge fdb add dev swp0 00:01:02:03:04:05 static # behaves the same for DSA as this command: bridge fdb add dev swp0 00:01:02:03:04:05 local # or shorthand, because the 'local' flag is implicit if 'static' is not # specified, it also behaves the same as: bridge fdb add dev swp0 00:01:02:03:04:05”…”�”}”hj3sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆj\‰j]Œsh”j_}”uh1jLh³hÇh´MEhj/ubah}”(h]”h ]”h"]”h$]”h&]”uh1j‡h³hÇh´MEhjìh²hubhÞ)�”}”(hXThe last command is an incorrect way of adding a static bridge FDB entry to a DSA switch using the bridge bypass operations, and works by mistake. Other drivers will treat an FDB entry added by the same command as ``local`` and as such, will not forward it, as opposed to DSA.”h]”(hŒÖThe last command is an incorrect way of adding a static bridge FDB entry to a DSA switch using the bridge bypass operations, and works by mistake. Other drivers will treat an FDB entry added by the same command as ”…”�”}”(hjIh²hh³Nh´Nubj)�”}”(hŒ ``local``”h]”hŒlocal”…”�”}”(hjQh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjIubhŒ5 and as such, will not forward it, as opposed to DSA.”…”�”}”(hjIh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MOhjìh²hubhÞ)�”}”(hŒýBetween kernel v4.14 and v5.14, DSA has supported in parallel two modes of adding a bridge FDB entry to the switch: the bridge bypass discussed above, as well as a new mode using the ``master`` flag which installs FDB entries in the software bridge too.”h]”(hŒ·Between kernel v4.14 and v5.14, DSA has supported in parallel two modes of adding a bridge FDB entry to the switch: the bridge bypass discussed above, as well as a new mode using the ”…”�”}”(hjih²hh³Nh´Nubj)�”}”(hŒ ``master``”h]”hŒmaster”…”�”}”(hjqh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjiubhŒ< flag which installs FDB entries in the software bridge too.”…”�”}”(hjih²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MThjìh²hubjˆ)�”}”(hŒN.. code-block:: sh bridge fdb add dev swp0 00:01:02:03:04:05 master static ”h]”jM)�”}”(hŒ7bridge fdb add dev swp0 00:01:02:03:04:05 master static”h]”hŒ7bridge fdb add dev swp0 00:01:02:03:04:05 master static”…”�”}”hj�sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆj\‰j]Œsh”j_}”uh1jLh³hÇh´MYhj‰ubah}”(h]”h ]”h"]”h$]”h&]”uh1j‡h³hÇh´MYhjìh²hubhÞ)�”}”(hŒãSince kernel v5.14, DSA has gained stronger integration with the bridge's software FDB, and the support for its bridge bypass FDB implementation (using the ``self`` flag) has been removed. This results in the following changes:”h]”(hŒžSince kernel v5.14, DSA has gained stronger integration with the bridge’s software FDB, and the support for its bridge bypass FDB implementation (using the ”…”�”}”(hj£h²hh³Nh´Nubj)�”}”(hŒ``self``”h]”hŒself”…”�”}”(hj«h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj£ubhŒ? flag) has been removed. This results in the following changes:”…”�”}”(hj£h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M]hjìh²hubjˆ)�”}”(hXØ.. code-block:: sh # This is the only valid way of adding an FDB entry that is supported, # compatible with v4.14 kernels and later: bridge fdb add dev swp0 00:01:02:03:04:05 master static # This command is no longer buggy and the entry is properly treated as # 'local' instead of being forwarded: bridge fdb add dev swp0 00:01:02:03:04:05 # This command no longer installs a static FDB entry to hardware: bridge fdb add dev swp0 00:01:02:03:04:05 static ”h]”jM)�”}”(hX³# This is the only valid way of adding an FDB entry that is supported, # compatible with v4.14 kernels and later: bridge fdb add dev swp0 00:01:02:03:04:05 master static # This command is no longer buggy and the entry is properly treated as # 'local' instead of being forwarded: bridge fdb add dev swp0 00:01:02:03:04:05 # This command no longer installs a static FDB entry to hardware: bridge fdb add dev swp0 00:01:02:03:04:05 static”h]”hX³# This is the only valid way of adding an FDB entry that is supported, # compatible with v4.14 kernels and later: bridge fdb add dev swp0 00:01:02:03:04:05 master static # This command is no longer buggy and the entry is properly treated as # 'local' instead of being forwarded: bridge fdb add dev swp0 00:01:02:03:04:05 # This command no longer installs a static FDB entry to hardware: bridge fdb add dev swp0 00:01:02:03:04:05 static”…”�”}”hjÇsbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆj\‰j]Œsh”j_}”uh1jLh³hÇh´MahjÃubah}”(h]”h ]”h"]”h$]”h&]”uh1j‡h³hÇh´Mahjìh²hubhÞ)�”}”(hŒ�Script writers are therefore encouraged to use the ``master static`` set of flags when working with bridge FDB entries on DSA switch interfaces.”h]”(hŒ3Script writers are therefore encouraged to use the ”…”�”}”(hjÝh²hh³Nh´Nubj)�”}”(hŒ``master static``”h]”hŒ master static”…”�”}”(hjåh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjÝubhŒL set of flags when working with bridge FDB entries on DSA switch interfaces.”…”�”}”(hjÝh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mlhjìh²hubeh}”(h]”Œ"forwarding-database-fdb-management”ah ]”h"]”Œ$forwarding database (fdb) management”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´M,ubhÉ)�”}”(hhh]”(hÎ)�”}”(hŒ#Affinity of user ports to CPU ports”h]”hŒ#Affinity of user ports to CPU ports”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÍhj h²hh³hÇh´MpubhÞ)�”}”(hŒýTypically, DSA switches are attached to the host via a single Ethernet interface, but in cases where the switch chip is discrete, the hardware design may permit the use of 2 or more ports connected to the host, for an increase in termination throughput.”h]”hŒýTypically, DSA switches are attached to the host via a single Ethernet interface, but in cases where the switch chip is discrete, the hardware design may permit the use of 2 or more ports connected to the host, for an increase in termination throughput.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mrhj h²hubhÞ)�”}”(hXcDSA can make use of multiple CPU ports in two ways. First, it is possible to statically assign the termination traffic associated with a certain user port to be processed by a certain CPU port. This way, user space can implement custom policies of static load balancing between user ports, by spreading the affinities according to the available CPU ports.”h]”hXcDSA can make use of multiple CPU ports in two ways. First, it is possible to statically assign the termination traffic associated with a certain user port to be processed by a certain CPU port. This way, user space can implement custom policies of static load balancing between user ports, by spreading the affinities according to the available CPU ports.”…”�”}”(hj$ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mwhj h²hubhÞ)�”}”(hXŽSecondly, it is possible to perform load balancing between CPU ports on a per packet basis, rather than statically assigning user ports to CPU ports. This can be achieved by placing the DSA conduits under a LAG interface (bonding or team). DSA monitors this operation and creates a mirror of this software LAG on the CPU ports facing the physical DSA conduits that constitute the LAG slave devices.”h]”hXŽSecondly, it is possible to perform load balancing between CPU ports on a per packet basis, rather than statically assigning user ports to CPU ports. This can be achieved by placing the DSA conduits under a LAG interface (bonding or team). DSA monitors this operation and creates a mirror of this software LAG on the CPU ports facing the physical DSA conduits that constitute the LAG slave devices.”…”�”}”(hj2 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M}hj h²hubhÞ)�”}”(hX´To make use of multiple CPU ports, the firmware (device tree) description of the switch must mark all the links between CPU ports and their DSA conduits using the ``ethernet`` reference/phandle. At startup, only a single CPU port and DSA conduit will be used - the numerically first port from the firmware description which has an ``ethernet`` property. It is up to the user to configure the system for the switch to use other conduits.”h]”(hŒ£To make use of multiple CPU ports, the firmware (device tree) description of the switch must mark all the links between CPU ports and their DSA conduits using the ”…”�”}”(hj@ h²hh³Nh´Nubj)�”}”(hŒ ``ethernet``”h]”hŒethernet”…”�”}”(hjH h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj@ ubhŒœ reference/phandle. At startup, only a single CPU port and DSA conduit will be used - the numerically first port from the firmware description which has an ”…”�”}”(hj@ h²hh³Nh´Nubj)�”}”(hŒ ``ethernet``”h]”hŒethernet”…”�”}”(hjZ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhj@ ubhŒ] property. It is up to the user to configure the system for the switch to use other conduits.”…”�”}”(hj@ h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M„hj h²hubhÞ)�”}”(hXƒDSA uses the ``rtnl_link_ops`` mechanism (with a "dsa" ``kind``) to allow changing the DSA conduit of a user port. The ``IFLA_DSA_CONDUIT`` u32 netlink attribute contains the ifindex of the conduit device that handles each user device. The DSA conduit must be a valid candidate based on firmware node information, or a LAG interface which contains only slaves which are valid candidates.”h]”(hŒ DSA uses the ”…”�”}”(hjr h²hh³Nh´Nubj)�”}”(hŒ``rtnl_link_ops``”h]”hŒ rtnl_link_ops”…”�”}”(hjz h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjr ubhŒ mechanism (with a “dsaâ€� ”…”�”}”(hjr h²hh³Nh´Nubj)�”}”(hŒ``kind``”h]”hŒkind”…”�”}”(hjŒ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjr ubhŒ8) to allow changing the DSA conduit of a user port. The ”…”�”}”(hjr h²hh³Nh´Nubj)�”}”(hŒ``IFLA_DSA_CONDUIT``”h]”hŒIFLA_DSA_CONDUIT”…”�”}”(hjž h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjr ubhŒø u32 netlink attribute contains the ifindex of the conduit device that handles each user device. The DSA conduit must be a valid candidate based on firmware node information, or a LAG interface which contains only slaves which are valid candidates.”…”�”}”(hjr h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M‹hj h²hubhÞ)�”}”(hŒ9Using iproute2, the following manipulations are possible:”h]”hŒ9Using iproute2, the following manipulations are possible:”…”�”}”(hj¶ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M’hj h²hubjˆ)�”}”(hXX.. code-block:: sh # See the DSA conduit in current use ip -d link show dev swp0 (...) dsa master eth0 # Static CPU port distribution ip link set swp0 type dsa master eth1 ip link set swp1 type dsa master eth0 ip link set swp2 type dsa master eth1 ip link set swp3 type dsa master eth0 # CPU ports in LAG, using explicit assignment of the DSA conduit ip link add bond0 type bond mode balance-xor && ip link set bond0 up ip link set eth1 down && ip link set eth1 master bond0 ip link set swp0 type dsa master bond0 ip link set swp1 type dsa master bond0 ip link set swp2 type dsa master bond0 ip link set swp3 type dsa master bond0 ip link set eth0 down && ip link set eth0 master bond0 ip -d link show dev swp0 (...) dsa master bond0 # CPU ports in LAG, relying on implicit migration of the DSA conduit ip link add bond0 type bond mode balance-xor && ip link set bond0 up ip link set eth0 down && ip link set eth0 master bond0 ip link set eth1 down && ip link set eth1 master bond0 ip -d link show dev swp0 (...) dsa master bond0 ”h]”jM)�”}”(hX # See the DSA conduit in current use ip -d link show dev swp0 (...) dsa master eth0 # Static CPU port distribution ip link set swp0 type dsa master eth1 ip link set swp1 type dsa master eth0 ip link set swp2 type dsa master eth1 ip link set swp3 type dsa master eth0 # CPU ports in LAG, using explicit assignment of the DSA conduit ip link add bond0 type bond mode balance-xor && ip link set bond0 up ip link set eth1 down && ip link set eth1 master bond0 ip link set swp0 type dsa master bond0 ip link set swp1 type dsa master bond0 ip link set swp2 type dsa master bond0 ip link set swp3 type dsa master bond0 ip link set eth0 down && ip link set eth0 master bond0 ip -d link show dev swp0 (...) dsa master bond0 # CPU ports in LAG, relying on implicit migration of the DSA conduit ip link add bond0 type bond mode balance-xor && ip link set bond0 up ip link set eth0 down && ip link set eth0 master bond0 ip link set eth1 down && ip link set eth1 master bond0 ip -d link show dev swp0 (...) dsa master bond0”h]”hX # See the DSA conduit in current use ip -d link show dev swp0 (...) dsa master eth0 # Static CPU port distribution ip link set swp0 type dsa master eth1 ip link set swp1 type dsa master eth0 ip link set swp2 type dsa master eth1 ip link set swp3 type dsa master eth0 # CPU ports in LAG, using explicit assignment of the DSA conduit ip link add bond0 type bond mode balance-xor && ip link set bond0 up ip link set eth1 down && ip link set eth1 master bond0 ip link set swp0 type dsa master bond0 ip link set swp1 type dsa master bond0 ip link set swp2 type dsa master bond0 ip link set swp3 type dsa master bond0 ip link set eth0 down && ip link set eth0 master bond0 ip -d link show dev swp0 (...) dsa master bond0 # CPU ports in LAG, relying on implicit migration of the DSA conduit ip link add bond0 type bond mode balance-xor && ip link set bond0 up ip link set eth0 down && ip link set eth0 master bond0 ip link set eth1 down && ip link set eth1 master bond0 ip -d link show dev swp0 (...) dsa master bond0”…”�”}”hjÈ sbah}”(h]”h ]”h"]”h$]”h&]”hÅhÆj\‰j]Œsh”j_}”uh1jLh³hÇh´M”hjÄ ubah}”(h]”h ]”h"]”h$]”h&]”uh1j‡h³hÇh´M”hj h²hubhÞ)�”}”(hX2Notice that in the case of CPU ports under a LAG, the use of the ``IFLA_DSA_CONDUIT`` netlink attribute is not strictly needed, but rather, DSA reacts to the ``IFLA_MASTER`` attribute change of its present conduit (``eth0``) and migrates all user ports to the new upper of ``eth0``, ``bond0``. Similarly, when ``bond0`` is destroyed using ``RTM_DELLINK``, DSA migrates the user ports that were assigned to this interface to the first physical DSA conduit which is eligible, based on the firmware description (it effectively reverts to the startup configuration).”h]”(hŒANotice that in the case of CPU ports under a LAG, the use of the ”…”�”}”(hjÞ h²hh³Nh´Nubj)�”}”(hŒ``IFLA_DSA_CONDUIT``”h]”hŒIFLA_DSA_CONDUIT”…”�”}”(hjæ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjÞ ubhŒI netlink attribute is not strictly needed, but rather, DSA reacts to the ”…”�”}”(hjÞ h²hh³Nh´Nubj)�”}”(hŒ``IFLA_MASTER``”h]”hŒ IFLA_MASTER”…”�”}”(hjø h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjÞ ubhŒ* attribute change of its present conduit (”…”�”}”(hjÞ h²hh³Nh´Nubj)�”}”(hŒ``eth0``”h]”hŒeth0”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjÞ ubhŒ2) and migrates all user ports to the new upper of ”…”�”}”(hjÞ h²hh³Nh´Nubj)�”}”(hŒ``eth0``”h]”hŒeth0”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjÞ ubhŒ, ”…”�”}”(hjÞ h²hh³Nh´Nubj)�”}”(hŒ ``bond0``”h]”hŒbond0”…”�”}”(hj. h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjÞ ubhŒ. Similarly, when ”…”�”}”(hjÞ h²hh³Nh´Nubj)�”}”(hŒ ``bond0``”h]”hŒbond0”…”�”}”(hj@ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjÞ ubhŒ is destroyed using ”…”�”}”(hjÞ h²hh³Nh´Nubj)�”}”(hŒ``RTM_DELLINK``”h]”hŒ RTM_DELLINK”…”�”}”(hjR h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jhjÞ ubhŒÐ, DSA migrates the user ports that were assigned to this interface to the first physical DSA conduit which is eligible, based on the firmware description (it effectively reverts to the startup configuration).”…”�”}”(hjÞ h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´Mµhj h²hubhÞ)�”}”(hXHIn a setup with more than 2 physical CPU ports, it is therefore possible to mix static user to CPU port assignment with LAG between DSA conduits. It is not possible to statically assign a user port towards a DSA conduit that has any upper interfaces (this includes LAG devices - the conduit must always be the LAG in this case).”h]”hXHIn a setup with more than 2 physical CPU ports, it is therefore possible to mix static user to CPU port assignment with LAG between DSA conduits. It is not possible to statically assign a user port towards a DSA conduit that has any upper interfaces (this includes LAG devices - the conduit must always be the LAG in this case).”…”�”}”(hjj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´M¾hj h²hubhÞ)�”}”(hŒ›Live changing of the DSA conduit (and thus CPU port) affinity of a user port is permitted, in order to allow dynamic redistribution in response to traffic.”h]”hŒ›Live changing of the DSA conduit (and thus CPU port) affinity of a user port is permitted, in order to allow dynamic redistribution in response to traffic.”…”�”}”(hjx h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÄhj h²hubhÞ)�”}”(hŒÿPhysical DSA conduits are allowed to join and leave at any time a LAG interface used as a DSA conduit; however, DSA will reject a LAG interface as a valid candidate for being a DSA conduit unless it has at least one physical DSA conduit as a slave device.”h]”hŒÿPhysical DSA conduits are allowed to join and leave at any time a LAG interface used as a DSA conduit; however, DSA will reject a LAG interface as a valid candidate for being a DSA conduit unless it has at least one physical DSA conduit as a slave device.”…”�”}”(hj† h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÝh³hÇh´MÇhj h²hubeh}”(h]”Œ#affinity-of-user-ports-to-cpu-ports”ah ]”h"]”Œ#affinity of user ports to cpu ports”ah$]”h&]”uh1hÈhhÊh²hh³hÇh´Mpubeh}”(h]”Œ'dsa-switch-configuration-from-userspace”ah ]”h"]”Œ'dsa switch configuration from userspace”ah$]”h&]”uh1hÈhhh²hh³hÇh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÇuh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)�”}”(hÍNŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”Œentry”Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jÇ Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÇŒ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”(hú]”hïajþ]”jôajñ]”jçauŒnameids”}”(j¡ jž jhújjjøjþj÷jôjçjñjæjãj jÿj™ j– uŒ nametypes”}”(j¡ ‰jˆj‰jøˆj÷‰jçˆjæ‰j ‰j™ ‰uh}”(jž hÊhúhûjhûjþj jôj jñjýjãjýjÿjìj– j uŒ footnote_refs”}”Œ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”Œ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”(hŒsystem_message”“”)�”}”(hhh]”hÞ)�”}”(hhh]”hŒ:Hyperlink target "dsa-config-showcases" is not referenced.”…”�”}”hj3 sbah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhj0 ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œsource”hÇŒline”K uh1j. ubj/ )�”}”(hhh]”hÞ)�”}”(hhh]”hŒ>Hyperlink target "dsa-tagged-configuration" is not referenced.”…”�”}”hjN sbah}”(h]”h ]”h"]”h$]”h&]”uh1hÝhjK ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”jH Œsource”hÇŒline”KRuh1j. ubj/ )�”}”(hhh]”hÞ)�”}”(hhh]”hŒ