Lines Matching refs:VLAN
41 VLAN Lookup yes yes
74 one bridge's ports from another's) or at the VLAN port membership level
78 The hardware tags all traffic internally with a port-based VLAN (pvid), or it
79 decodes the VLAN information from the 802.1Q tag. Advanced VLAN classification
80 is not possible. Once attributed a VLAN tag, frames are checked against the
81 port's membership rules and dropped at ingress if they don't match any VLAN.
85 Normally the hardware is not configurable with respect to VLAN awareness, but
91 all bridges should have the same level of VLAN awareness (either both have
113 on the VLAN PCP bits (if no VLAN is present, the port-based default is used).
115 ``vlan_filtering``, the EtherType recognized by the switch as being VLAN can
117 for tagging. Therefore, the switch ignores the VLAN PCP if used in standalone
122 offloaded flows can be steered to TX queues based on the VLAN PCP, but the DSA
124 queue with VLAN awareness active, it is necessary to create a VLAN
125 sub-interface on the DSA master port, and send normal (0x8100) VLAN-tagged
126 towards the switch, with the VLAN PCP bits set appropriately.
130 disregards any VLAN PCP bits even if present. The traffic class for management
189 - VLAN-aware virtual links: these match on destination MAC address, VLAN ID and
190 VLAN PCP.
191 - VLAN-unaware virtual links: these match on destination MAC address only.
193 The VLAN awareness state of the bridge (vlan_filtering) cannot be changed while
205 CPU and to swp3. This type of key (DA only) when the port's VLAN awareness
226 tuple composed of destination MAC address, VLAN ID and VLAN PCP). Packets which
299 The SJA1105 switch family always performs VLAN processing. When configured as
300 VLAN-unaware, frames carry a different VLAN tag internally, depending on
301 whether the port is standalone or under a VLAN-unaware bridge.
303 The virtual link keys are always fixed at {MAC DA, VLAN ID, VLAN PCP}, but the
304 driver asks for the VLAN ID and VLAN PCP when the port is under a VLAN-aware
305 bridge. Otherwise, it fills in the VLAN ID and PCP automatically, based on
306 whether the port is standalone or in a VLAN-unaware bridge, and accepts only
307 "VLAN-unaware" tc-flower keys (MAC DA).
312 - port was standalone and joins a bridge (VLAN-aware or VLAN-unaware)
313 - port is part of a bridge whose VLAN awareness state changes
315 - port was standalone, but another port joins a VLAN-aware bridge and this
316 changes the global VLAN awareness state of the bridge