Lines Matching full:vlan

52 on Port-based VLAN IDs).
420 - inability to configure specific VLAN IDs / trunking VLANs between switches
478 more specifically with its VLAN filtering portion when configuring VLANs on top
480 supported by DSA are the FDB and VLAN objects.
496   tables and VLAN tables. For example, this might be useful if the tables
505   utilization of certain hardware tables in the device, such as FDB, VLAN, etc.
632   a Port-based VLAN ID for each port and allowing only the CPU port and the
776 For example, all ports that belong to a VLAN-unaware bridge (which is
777 *currently* VLAN-unaware) are expected to learn source addresses in the
779 VLAN-unaware bridges). During forwarding and FDB lookup, a packet received on a
780 VLAN-unaware bridge port should be able to find a VLAN-unaware FDB entry having
784 a port which is a member of a different VLAN-unaware bridge (and is therefore
787 Similarly, each VLAN of each offloaded VLAN-aware bridge should have an
789 that VLAN, but not shared by ports belonging to different bridges that are
792 In this context, a VLAN-unaware database means that all packets are expected to
793 match on it irrespective of VLAN ID (only MAC address lookup), whereas a
794 VLAN-aware database means that packets are supposed to match based on the VLAN
797 At the bridge layer, VLAN-unaware FDB entries have the special VID value of 0,
798 whereas VLAN-aware FDB entries have non-zero VID values. Note that a
799 VLAN-unaware bridge may have VLAN-aware (non-zero VID) FDB entries, and a
800 VLAN-aware bridge may have VLAN-unaware FDB entries. As in hardware, the
861   ``db->bridge``. Separation between the VLAN-unaware database and the per-VID
936 VLAN-unaware, and in this case the FID must be equal to the FID used by the
937 driver for its VLAN-unaware address database associated with that bridge.
938 Alternatively, the bridge may be VLAN-aware, and in that case, it is guaranteed
939 that the packet is also VLAN-tagged with the VLAN ID that the bridge processed
976 Bridge VLAN filtering
980   configured for turning on or off VLAN filtering. If nothing specific needs to
982   When VLAN filtering is turned on, the hardware must be programmed with
983   rejecting 802.1Q frames which have VLAN IDs outside of the programmed allowed
984   VLAN ID map/rules.  If there is no PVID programmed into the switch port,
986   accept any 802.1Q frames irrespective of their VLAN ID, and untagged frames are
989 - ``port_vlan_add``: bridge layer function invoked when a VLAN is configured
991   of a VLAN only if a foreign bridge port is also a member of it (and
992   forwarding needs to take place in software), or the VLAN is installed to the
993   VLAN group of the bridge device itself, for termination purposes
994   (``bridge vlan add dev br0 vid 100 self``). VLANs on shared ports are
996   to manually install a VLAN on the CPU port.
998 - ``port_vlan_del``: bridge layer function invoked when a VLAN is removed from the
1003   specified address in the specified VLAN Id in the forwarding database
1004   associated with this VLAN ID.
1008   the specified MAC address from the specified VLAN ID if it was mapped into
1020   specified address in the specified VLAN ID in the forwarding database
1021   associated with this VLAN ID.
1025   the specified MAC address from the specified VLAN ID if it was mapped into
1039 LAG join/leave the bridge. Switchdev port attributes (VLAN filtering, STP