| /linux-6.3-rc2/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-6.3-rc2/Documentation/networking/ |
| A D | switchdev.rst | 173 FDB entry is the {port, MAC, VLAN} tuple forwarding destination.
222 traffic. To enable VLAN support, turn on VLAN filtering::
454 Bridge VLAN filtering
461 - with VLAN filtering turned off: the bridge is strictly VLAN unaware and its
468 - with VLAN filtering turned on: the bridge is VLAN-aware and frames ingressing
479 VLAN upper. The VLAN upper interface (which consumes the VLAN tag) can even
482 belonging to the VLAN upper interfaces are managed properly:
494 - with VLAN filtering turned on, these VLAN devices can be created as long as
500 way by the enabling of VLAN filtering on the bridge device(s). If the VLAN
511 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
|
| A D | vxlan.rst | 8 problem of limited VLAN IDs (4096) in IEEE 802.1q. With VXLAN the
23 neighbors GRE and VLAN. Configuring VXLAN requires the version of
|
| /linux-6.3-rc2/Documentation/networking/dsa/ |
| A D | sja1105.rst | 79 decodes the VLAN information from the 802.1Q tag. Advanced VLAN classification
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
189 - VLAN-aware virtual links: these match on destination MAC address, VLAN ID and
190 VLAN PCP.
226 tuple composed of destination MAC address, VLAN ID and VLAN PCP). Packets which
300 VLAN-unaware, frames carry a different VLAN tag internally, depending on
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
307 "VLAN-unaware" tc-flower keys (MAC DA).
[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).
476 supported by DSA are the FDB and VLAN objects.
776 VLAN-unaware bridge port should be able to find a VLAN-unaware FDB entry having
783 Similarly, each VLAN of each offloaded VLAN-aware bridge should have an
790 VLAN-aware database means that packets are supposed to match based on the VLAN
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
935 that the packet is also VLAN-tagged with the VLAN ID that the bridge processed
972 Bridge VLAN filtering
1000 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
|
| /linux-6.3-rc2/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-6.3-rc2/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-6.3-rc2/tools/testing/selftests/bpf/ |
| A D | test_xdp_vlan.sh | 182 export VLAN=4011
184 ip netns exec ${NS2} ip link add link $DEVNS2 name $DEVNS2.$VLAN type vlan id $VLAN
185 ip netns exec ${NS2} ip addr add ${IPADDR2}/24 dev $DEVNS2.$VLAN
187 ip netns exec ${NS2} ip link set $DEVNS2.$VLAN up
|
| /linux-6.3-rc2/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-6.3-rc2/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-6.3-rc2/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 …]
|
| /linux-6.3-rc2/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-6.3-rc2/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-6.3-rc2/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-6.3-rc2/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| A D | switchdev.rst | 30 Following bridge VLAN functions are supported by mlx5:
32 - VLAN filtering (including multiple VLANs per port)::
37 - VLAN push on bridge ingress::
41 - VLAN pop on bridge egress::
|
| /linux-6.3-rc2/Documentation/scsi/ |
| A D | bnx2fc.rst | 18 Furthermore, the Broadcom FCoE offload solution creates VLAN interfaces to
69 <INTERFACE>.<VLAN>-fcoe interfaces are automatically created.
|