| /Documentation/networking/dsa/ |
| D | b53.rst | 48 The configuration slightly differ from the :ref:`dsa-vlan-configuration`.
51 VLAN programming would basically change the CPU port's default PVID and make
54 In difference to the configuration described in :ref:`dsa-vlan-configuration`
55 the default VLAN 1 has to be removed from the user interface configuration in
57 VLAN configuration in the bridge showcase.
61 The configuration can only be set up via VLAN tagging and bridge setup.
67 ip link add link eth0 name eth0.1 type vlan id 1
68 ip link add link eth0 name eth0.2 type vlan id 2
69 ip link add link eth0 name eth0.3 type vlan id 3
85 # activate VLAN filtering
[all …]
|
| D | sja1105.rst | 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
[all …]
|
| D | configuration.rst | 89 without using a VLAN based configuration.
162 .. _dsa-vlan-configuration:
168 (DSA_TAG_PROTO_NONE). These switches can be configured by a VLAN based
172 The configuration can only be set up via VLAN tagging and bridge setup.
177 ip link add link eth0 name eth0.1 type vlan id 1
178 ip link add link eth0 name eth0.2 type vlan id 2
179 ip link add link eth0 name eth0.3 type vlan id 3
196 # activate VLAN filtering
205 bridge vlan add dev lan1 vid 1 pvid untagged
206 bridge vlan add dev lan2 vid 2 pvid untagged
[all …]
|
| D | dsa.rst | 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
[all …]
|
| D | lan9303.rst | 36 - Support for VLAN filtering is not implemented
37 - The HW does not support VLAN-specific fdb entries
|
| /Documentation/networking/device_drivers/ethernet/ti/ |
| D | am65_nuss_cpsw_switchdev.rst | 65 [*] bridge vlan add dev br0 vid 1 pvid untagged self
79 VLAN configuration
84 bridge vlan add dev br0 vid 1 pvid untagged self <---- add cpu port to VLAN 1
93 bridge vlan add dev sw0p1 vid 100 pvid untagged master
94 bridge vlan add dev sw0p2 vid 100 pvid untagged master
95 bridge vlan add dev br0 vid 100 pvid untagged self <---- Add cpu port to VLAN100
99 bridge vlan add dev sw0p1 vid 100 master
100 bridge vlan add dev sw0p2 vid 100 master
101 bridge vlan add dev br0 vid 100 pvid tagged self <---- Add cpu port to VLAN100
110 bridge fdb add aa:bb:cc:dd:ee:ff dev sw0p1 master vlan 100
[all …]
|
| D | cpsw_switchdev.rst | 32 So, Ports in promiscuous mode will keep possibility of mcast and vlan
64 configured in vlan unaware mode or default_pvid has to be adjusted::
115 [*] bridge vlan add dev br0 vid 1 pvid untagged self
129 VLAN configuration
134 bridge vlan add dev br0 vid 1 pvid untagged self <---- add cpu port to VLAN 1
143 bridge vlan add dev sw0p1 vid 100 pvid untagged master
144 bridge vlan add dev sw0p2 vid 100 pvid untagged master
145 bridge vlan add dev br0 vid 100 pvid untagged self <---- Add cpu port to VLAN100
149 bridge vlan add dev sw0p1 vid 100 master
150 bridge vlan add dev sw0p2 vid 100 master
[all …]
|
| D | cpsw.rst | 246 // Create vlan 100 to map sk->priority to vlan qos
247 $ ip link add link eth0 name eth0.100 type vlan id 100
248 8021q: 802.1Q VLAN Support v1.8
249 8021q: adding VLAN 0 to HW filter on device eth0
250 8021q: adding VLAN 0 to HW filter on device eth1
251 net eth0: Adding vlanid 100 to vlan filter
256 $ ip link set eth0.100 type vlan \
261 // Check egress map for vlan 100
262 $ cat /proc/net/vlan/eth0.100
277 // run your listener on workstation (should be in same vlan)
[all …]
|
| /Documentation/networking/ |
| D | switchdev.rst | 173 FDB entry is the {port, MAC, VLAN} tuple forwarding destination.
180 - VLAN flooding of multicast/broadcast and unknown unicast packets
189 bridge fdb add dev DEV ADDRESS [vlan VID] [self] static
202 bridge fdb add dev DEV ADDRESS [vlan VID] master static
221 Note: by default, the bridge does not filter on VLAN and only bridges untagged
222 traffic. To enable VLAN support, turn on VLAN filtering::
229 The switch device will learn/forget source MAC address/VLAN on ingress packets
230 and notify the switch driver of the mac/vlan/port tuples. The switch driver,
310 For a given L2 VLAN domain, the switch device should flood multicast/broadcast
313 vlan L2 domain, can program the switch device for flooding. The packet may
[all …]
|
| D | cdc_mbim.rst | 176 channel. The cdc_mbim driver models such IP sessions as 802.1q VLAN
178 VLAN ID Z for all values of Z greater than 0.
184 VLAN links prior to establishing MBIM IP sessions where the SessionId
185 is greater than 0. These links can be added by using the normal VLAN
190 ip link add link wwan0 name wwan0.3 type vlan id 3
200 sessions as another set of 802.1q VLAN subdevices of the master wwanY
201 device, mapping MBIM DSS session A to VLAN ID (256 + A) for all values
207 The DSS VLAN subdevices are used as a practical interface between the
231 ip link add link wwan0 name wwan0.dss5 type vlan id 261
240 Note that adding VLAN links for DSS sessions is entirely optional. A
[all …]
|
| 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
180 eth(...), vlan(vid=10, pcp=0), eth_type(0x0800), ip(proto=6, ...), tcp(...)
183 has not been updated to understand the new "vlan" flow key attribute.
185 ignore the "vlan" attribute that it does not understand and therefore
193 VLAN 10 is actually expressed as::
[all …]
|
| D | bridge.rst | 151 VLAN chapter
159 A VLAN (Virtual Local Area Network) is a logical segmentation of a physical
164 Typically there are two VLAN implementations, IEEE 802.1Q and IEEE 802.1ad
165 (also known as QinQ). IEEE 802.1Q is a standard for VLAN tagging in Ethernet
167 physical network and tag Ethernet frames with VLAN information, which is
168 called *VLAN-tagged frames*. IEEE 802.1ad, commonly known as QinQ or Double
169 VLAN, is an extension of the IEEE 802.1Q standard. QinQ allows for the
170 stacking of multiple VLAN tags within a single Ethernet frame. The Linux
173 protocol for VLAN tagging.
175 `VLAN filtering <https://lore.kernel.org/netdev/1360792820-14116-1-git-send-email-vyasevic@redhat.c…
[all …]
|
| 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
|
| 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
142 * VLAN challenged
144 NETIF_F_VLAN_CHALLENGED should be set for devices which can't cope with VLAN
146 [FIXME: Those cases could be fixed in VLAN code by allowing only reduced-MTU
|
| /Documentation/arch/s390/ |
| 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.
|
| /Documentation/bpf/ |
| 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``
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| 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::
52 ip link set eth0 vf 0 vlan 100 // set vlan 100 for VF 0
53 ip link set eth0 vf 0 vlan 0 // Delete vlan 100
54 ip link set eth0 vf 0 vlan 200 // set a new vlan 200 for VF 0
|
| 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::
80 ip link set eth0 vf 0 vlan 100 // set vlan 100 for VF 0
81 ip link set eth0 vf 0 vlan 0 // Delete vlan 100
82 ip link set eth0 vf 0 vlan 200 // set a new vlan 200 for VF 0
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
|
| 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
118 The IEEE 802.1ad standard, informally known as QinQ, allows for multiple VLAN
119 IDs within a single Ethernet frame. VLAN IDs are sometimes referred to as
120 "tags," and multiple VLAN IDs are thus referred to as a "tag stack." Tag stacks
122 VLAN ID, among other uses.
126 # ip link add link eth0 eth0.24 type vlan proto 802.1ad id 24
[all …]
|
| D | ice.rst | 71 unintended traffic streams, configure all SR-IOV enabled ports for VLAN tagging
75 See "Configuring VLAN Tagging on SR-IOV Enabled Adapter Ports" later in this
512 Configuring VLAN Tagging on SR-IOV Enabled Adapter Ports
514 To configure VLAN tagging for the ports on an SR-IOV enabled adapter, use the
515 following command. The VLAN configuration should be done before the VF driver
516 is loaded or the VM is booted. The VF is not aware of the VLAN tag being
518 VLAN" mode).
522 # ip link set dev <ethX> vf <id> vlan <vlan id>
524 For example, the following will configure PF eth0 and the first VF on VLAN 10::
526 # ip link set dev eth0 vf 0 vlan 10
[all …]
|
| /Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| 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.
200 $ bridge vlan add vid 200 dev eth8
[all …]
|
| /Documentation/networking/device_drivers/ethernet/freescale/ |
| 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
|
| /Documentation/netlink/specs/ |
| D | rt_link.yaml | 54 name: vlan-protocols
742 name: ifla-vlan-flags
748 enum: vlan-flags
755 name: vlan-flags
764 name: ifla-vlan-qos-mapping
785 name: ifla-vf-vlan
792 name: vlan
879 name: ifla-vf-vlan-info
886 name: vlan
892 name: vlan-proto
[all …]
|
| /Documentation/scsi/ |
| D | bnx2fc.rst | 18 Furthermore, the Broadcom FCoE offload solution creates VLAN interfaces to
41 the system, bnx2fc driver would automatically claim the interfaces, starts vlan
68 6. Verify the vlan discovery is performed by running ifconfig and notice
69 <INTERFACE>.<VLAN>-fcoe interfaces are automatically created.
|
| /Documentation/networking/device_drivers/ethernet/aquantia/ |
| 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
323 are passed in the same 'vlan' parameter.
325 To add a filter that directs packets from VLAN 2001 to queue 5::
327 ethtool -N <ethX> flow-type ip4 vlan 2001 m 0xF000 action 1 loc 0
332 UserPriority (vlan) parameter must be accompanied by mask 0x1FFF. That is to
333 distinguish VLAN filter from L2 Ethertype filter with UserPriority since both
[all …]
|