| /linux/net/8021q/ |
| A D | Kconfig | 3 # Configuration for 802.1Q VLAN support
7 tristate "802.1Q/802.1ad VLAN Support"
9 Select this and you will be able to create 802.1Q VLAN interfaces
10 on your Ethernet interfaces. 802.1Q VLAN supports almost
14 See the VLAN web page for more information:
23 bool "GVRP (GARP VLAN Registration Protocol) support"
33 bool "MVRP (Multiple VLAN Registration Protocol) support"
|
| /linux/Documentation/networking/ |
| A D | switchdev.rst | 172 FDB entry is the {port, MAC, VLAN} tuple forwarding destination.
221 traffic. To enable VLAN support, turn on VLAN filtering::
453 Bridge VLAN filtering
460 - with VLAN filtering turned off: the bridge is strictly VLAN unaware and its
467 - with VLAN filtering turned on: the bridge is VLAN-aware and frames ingressing
478 VLAN upper. The VLAN upper interface (which consumes the VLAN tag) can even
481 belonging to the VLAN upper interfaces are managed properly:
493 - with VLAN filtering turned on, these VLAN devices can be created as long as
499 way by the enabling of VLAN filtering on the bridge device(s). If the VLAN
510 ensure VLAN awareness is pushed down to the hardware.
[all …]
|
| A D | cdc_mbim.rst | 178 VLAN ID Z for all values of Z greater than 0.
250 /* use special negative offsets to get VLAN tag */
254 /* verify DSS VLAN range */
269 Tagged IP session 0 VLAN
285 behaviour is triggered by adding a VLAN link for the magic VLAN ID
291 subdevice after the MBIM SessionID instead of the VLAN ID. For
297 VLAN mapping
304 VLAN ID MBIM type MBIM SessionID Notes
312 a) if no VLAN ID 4094 link exists, else dropped
313 b) unsupported VLAN range, unconditionally dropped
[all …]
|
| A D | nf_flowtable.rst | 28 n-tuple selectors: layer 2 protocol encapsulation (VLAN and PPPoE), layer 3
124 netdevice behind VLAN and PPPoE netdevices. The flowtable software datapath
125 parses the VLAN and PPPoE layer 2 headers to extract the ethertype and the
126 VLAN ID / PPPoE session ID which are used for the flowtable lookups. The
129 You do not need to add the PPPoE and the VLAN devices to your flowtable,
157 The flowtable infrastructure also supports for bridge VLAN filtering actions
158 such as PVID and untagged. You can also stack a classic VLAN device on top of
|
| A D | openvswitch.rst | 10 VLAN processing, network access control, flow-based network control,
167 did not already implement VLAN parsing. Instead, it just interpreted
174 Naively, to add VLAN support, it makes sense to add a new "vlan" flow
175 key attribute to contain the VLAN tag, then continue to decode the
176 encapsulated headers beyond the VLAN tag using the existing field
177 definitions. With this change, a TCP packet in VLAN 10 would have a
193 VLAN 10 is actually expressed as::
226 indicating that a VLAN TCI should follow, but which is truncated just
233 all-zero-bits VLAN TCI is not that rare, so the CFI bit (aka
237 missing or malformed VLAN TCI.
|
| A D | netdev-features.rst | 34 by child VLAN devices (limits netdev->features set). This is currently
35 used for all VLAN devices whether tags are stripped or inserted in
157 * VLAN challenged
159 NETIF_F_VLAN_CHALLENGED should be set for devices which can't cope with VLAN
161 [FIXME: Those cases could be fixed in VLAN code by allowing only reduced-MTU
|
| /linux/Documentation/s390/ |
| A D | qeth.rst | 33 or a VLAN is registered or unregistered on the network served by the device.
38 notifications are started afresh, a new host or VLAN is registered or
42 VLAN=numeric-vlan-id
43 VLAN ID on which the event occurred. Not included
44 if no VLAN is involved in the event.
49 event reports the creation or destruction of a VLAN.
|
| /linux/Documentation/bpf/ |
| A D | prog_flow_dissector.rst | 41 In the VLAN-less case, this is what the initial state of the BPF flow
58 In case of VLAN, flow dissector can be called with the two different states.
60 Pre-VLAN parsing::
76 have to parse VLAN information twice for double tagged packets.
79 Post-VLAN parsing::
94 In this case VLAN information has been processed before the flow dissector
99 the optional VLAN header and should gracefully handle both cases: when single
100 or double VLAN is present and when it is not present. The same program
142 C-based implementation can export. Notable example is single VLAN (802.1Q)
143 and double VLAN (802.1AD) tags. Please refer to the ``struct bpf_flow_keys``
|
| /linux/Documentation/networking/dsa/ |
| A D | sja1105.rst | 41 VLAN Lookup yes yes
74 one bridge's ports from another's) or at the VLAN port membership level
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
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).
124 queue with VLAN awareness active, it is necessary to create a VLAN
126 towards the switch, with the VLAN PCP bits set appropriately.
189 - VLAN-aware virtual links: these match on destination MAC address, VLAN ID and
190 VLAN PCP.
[all …]
|
| A D | b53.rst | 51 VLAN programming would basically change the CPU port's default PVID and make
55 the default VLAN 1 has to be removed from the slave interface configuration in
57 VLAN configuration in the bridge showcase.
61 The configuration can only be set up via VLAN tagging and bridge setup.
85 # activate VLAN filtering
128 # activate VLAN filtering
165 # activate VLAN filtering
|
| A D | dsa.rst | 52 on Port-based VLAN IDs).
445 supported by DSA are the FDB and VLAN objects.
461 tables and VLAN tables. For example, this might be useful if the tables
669 Bridge VLAN filtering
675 When VLAN filtering is turned on, the hardware must be programmed with
677 VLAN ID map/rules. If there is no PVID programmed into the switch port,
696 specified address in the specified VLAN Id in the forwarding database
697 associated with this VLAN ID. If the operation is not supported, this
717 specified address in the specified VLAN ID in the forwarding database
718 associated with this VLAN ID.
[all …]
|
| A D | lan9303.rst | 36 - Support for VLAN filtering is not implemented
37 - The HW does not support VLAN-specific fdb entries
|
| A D | configuration.rst | 86 without using a VLAN based configuration.
165 (DSA_TAG_PROTO_NONE). These switches can be configured by a VLAN based
169 The configuration can only be set up via VLAN tagging and bridge setup.
193 # activate VLAN filtering
234 # activate VLAN filtering
275 # activate VLAN filtering
|
| /linux/tools/testing/selftests/bpf/ |
| A D | test_xdp_vlan.sh | 180 export VLAN=4011
182 ip netns exec ns2 ip link add link $DEVNS2 name $DEVNS2.$VLAN type vlan id $VLAN
183 ip netns exec ns2 ip addr add ${IPADDR2}/24 dev $DEVNS2.$VLAN
185 ip netns exec ns2 ip link set $DEVNS2.$VLAN up
|
| /linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| A D | switch-driver.rst | 89 The hardware is not configurable with respect to VLAN awareness, thus any DPAA2
90 switch port should be used only in usecases with a VLAN aware bridge::
96 Error: fsl_dpaa2_switch: Cannot join a VLAN-unaware bridge
138 * VLAN: vlan_id/vlan_prio/vlan_tpid/vlan_dei
179 The DPAA2 switch supports only per port mirroring and per VLAN mirroring.
188 Error: fsl_dpaa2_switch: Only matching on VLAN ID supported.
191 If a mirroring VLAN filter is requested on a port, the VLAN must to be
193 a VLAN upper device if the switch port is used as a standalone interface::
197 Error: VLAN must be installed on the switch port.
208 packet will reach the mirror port, if the VLAN found in the packet is not
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| A D | iavf.rst | 70 Setting VLAN Tag Stripping
73 packets with VLAN tags, you can disable VLAN tag stripping for the VF. The
75 disable VLAN tag stripping. Note that if the PF has assigned a VLAN to a VF,
76 then requests from that VF to set VLAN tag stripping will be ignored.
78 To enable/disable VLAN tag stripping for a VF, issue the following command
119 IDs within a single Ethernet frame. VLAN IDs are sometimes referred to as
122 VLAN ID, among other uses.
129 Where "24" and "371" are example VLAN IDs.
132 Receive checksum offloads, cloud filters, and VLAN acceleration are not
241 trusted mode, refer to the section "VLAN Tag Packet Steering" in this
[all …]
|
| A D | igb.rst | 76 NOTE: When either SR-IOV mode or VMDq mode is enabled, hardware VLAN filtering
77 and VLAN tag stripping/insertion will remain enabled. Please remove the old
78 VLAN filter before the new VLAN filter is added. For example::
162 MAC and VLAN anti-spoofing feature
174 Setting MAC Address, VLAN and Rate Limit Using IProute2 Tool
176 You can set a MAC address of a Virtual Function (VF), a default VLAN and the
|
| A D | fm10k.rst | 48 NOTE: When SR-IOV mode is enabled, hardware VLAN filtering and VLAN tag
49 stripping/insertion will remain enabled. Please remove the old VLAN filter
50 before the new VLAN filter is added. For example::
|
| A D | ice.rst | 75 See "Configuring VLAN Tagging on SR-IOV Enabled Adapter Ports" later in this
517 Configuring VLAN Tagging on SR-IOV Enabled Adapter Ports
521 is loaded or the VM is booted. The VF is not aware of the VLAN tag being
523 VLAN" mode).
607 Next, add a VLAN interface on the VF interface. For example::
613 example is that the VF will get all traffic that is tagged with VLAN 100.
637 MAC and VLAN Anti-Spoofing Feature for VFs
841 IDs within a single Ethernet frame. VLAN IDs are sometimes referred to as
844 VLAN ID, among other uses.
862 1) The VF is not assigned a port VLAN.
[all …]
|
| A D | ixgbe.rst | 219 NOTE: When either SR-IOV mode or VMDq mode is enabled, hardware VLAN filtering
220 and VLAN tag stripping/insertion will remain enabled. Please remove the old
221 VLAN filter before the new VLAN filter is added. For example,
225 ip link set eth0 vf 0 vlan 100 // set VLAN 100 for VF 0
226 ip link set eth0 vf 0 vlan 0 // Delete VLAN 100
227 ip link set eth0 vf 0 vlan 200 // set a new VLAN 200 for VF 0
238 in the VLAN tag. When SR-IOV is not enabled, each traffic class is associated
476 the VLAN priority tag (802.1p) to filter traffic. That means that there are 8
505 MAC and VLAN anti-spoofing feature
|
| /linux/Documentation/networking/device_drivers/ethernet/freescale/ |
| A D | gianfar.rst | 22 VLAN chapter
25 In order to use VLAN, please consult Linux documentation on
27 extraction of VLAN headers, but not filtering. Filtering will be
|
| /linux/Documentation/networking/device_drivers/ethernet/aquantia/ |
| A D | atlantic.rst | 261 1. 16 VLAN ID rules
279 - Locations 0 - 15 for VLAN ID filters
320 The VLAN filter (VLAN id) is compared against 16 filters.
321 VLAN id must be accompanied by mask 0xF000. That is to distinguish VLAN filter
322 from L2 Ethertype filter with UserPriority since both User Priority and VLAN ID
325 To add a filter that directs packets from VLAN 2001 to queue 5::
333 distinguish VLAN filter from L2 Ethertype filter with UserPriority since both
334 User Priority and VLAN ID are passed in the same 'vlan' parameter.
|
| /linux/net/bridge/ |
| A D | Kconfig | 52 bool "VLAN filtering"
58 receive and forward traffic based on VLAN information in the packet
59 any VLAN information configured on the bridge port or bridge device.
|
| /linux/Documentation/networking/device_drivers/ethernet/ti/ |
| A D | am65_nuss_cpsw_switchdev.rst | 79 VLAN configuration
84 bridge vlan add dev br0 vid 1 pvid untagged self <---- add cpu port to VLAN 1
143 default VLAN (default_pvid).
|
| /linux/tools/testing/selftests/bpf/progs/ |
| A D | bpf_flow.c | 34 #define VLAN 5 macro
131 bpf_tail_call_static(skb, &jmp_table, VLAN); in parse_eth_proto()
389 PROG(VLAN)(struct __sk_buff *skb) in PROG() argument
|