networking/dsa/dsa.rst

52 on Port-based VLAN IDs).
416 - inability to configure specific VLAN IDs / trunking VLANs between switches
474 more specifically with its VLAN filtering portion when configuring VLANs on top
476 supported by DSA are the FDB and VLAN objects.
492   tables and VLAN tables. For example, this might be useful if the tables
501   utilization of certain hardware tables in the device, such as FDB, VLAN, etc.
628   a Port-based VLAN ID for each port and allowing only the CPU port and the
772 For example, all ports that belong to a VLAN-unaware bridge (which is
773 *currently* VLAN-unaware) are expected to learn source addresses in the
775 VLAN-unaware bridges). During forwarding and FDB lookup, a packet received on a
776 VLAN-unaware bridge port should be able to find a VLAN-unaware FDB entry having
780 a port which is a member of a different VLAN-unaware bridge (and is therefore
783 Similarly, each VLAN of each offloaded VLAN-aware bridge should have an
785 that VLAN, but not shared by ports belonging to different bridges that are
788 In this context, a VLAN-unaware database means that all packets are expected to
789 match on it irrespective of VLAN ID (only MAC address lookup), whereas a
790 VLAN-aware database means that packets are supposed to match based on the VLAN
793 At the bridge layer, VLAN-unaware FDB entries have the special VID value of 0,
794 whereas VLAN-aware FDB entries have non-zero VID values. Note that a
795 VLAN-unaware bridge may have VLAN-aware (non-zero VID) FDB entries, and a
796 VLAN-aware bridge may have VLAN-unaware FDB entries. As in hardware, the
857   ``db->bridge``. Separation between the VLAN-unaware database and the per-VID
932 VLAN-unaware, and in this case the FID must be equal to the FID used by the
933 driver for its VLAN-unaware address database associated with that bridge.
934 Alternatively, the bridge may be VLAN-aware, and in that case, it is guaranteed
935 that the packet is also VLAN-tagged with the VLAN ID that the bridge processed
972 Bridge VLAN filtering
976   configured for turning on or off VLAN filtering. If nothing specific needs to
978   When VLAN filtering is turned on, the hardware must be programmed with
979   rejecting 802.1Q frames which have VLAN IDs outside of the programmed allowed
980   VLAN ID map/rules.  If there is no PVID programmed into the switch port,
982   accept any 802.1Q frames irrespective of their VLAN ID, and untagged frames are
985 - ``port_vlan_add``: bridge layer function invoked when a VLAN is configured
987   of a VLAN only if a foreign bridge port is also a member of it (and
988   forwarding needs to take place in software), or the VLAN is installed to the
989   VLAN group of the bridge device itself, for termination purposes
992   to manually install a VLAN on the CPU port.
994 - ``port_vlan_del``: bridge layer function invoked when a VLAN is removed from the
999   specified address in the specified VLAN Id in the forwarding database
1000   associated with this VLAN ID.
1004   the specified MAC address from the specified VLAN ID if it was mapped into
1016   specified address in the specified VLAN ID in the forwarding database
1017   associated with this VLAN ID.
1021   the specified MAC address from the specified VLAN ID if it was mapped into
1035 LAG join/leave the bridge. Switchdev port attributes (VLAN filtering, STP