| /OK3568_Linux_fs/kernel/net/8021q/ |
| H 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"
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.t1040-l2switch | 11 - Independent and shared VLAN learning (IVL, SVL) 16 - VLAN editing, translation and remarking 31 - Port-based VLAN 32 - Private/Shared VLAN learning 33 - VLAN ingress filtering 42 ethsw [port <port_no>] pvid { [help] | show | <pvid> } - set/show PVID (ingress and egress VLAN tag… 43 ethsw [port <port_no>] vlan { [help] | show | add <vid> | del <vid> } - add a VLAN to a port (VLAN … 47 ethsw vlan fdb { [help] | show | shared | private } - make VLAN learning shared or private 48 ethsw [port <port_no>] ingress filtering { [help] | show | enable | disable } - enable/disable VLAN…
|
| H A D | README.VLAN | 4 You control the sending/receiving of VLAN tagged packets with the 8 CDP is used mainly to discover your device VLAN(s) when connected to
|
| /OK3568_Linux_fs/kernel/Documentation/networking/ |
| H A 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 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 240 Note that adding VLAN links for DSS sessions is entirely optional. A 242 directly to the master network device, using the received VLAN tags to 243 map frames to the correct DSS session and adding 18 byte VLAN ethernet [all …]
|
| H 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.
|
| H 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
|
| H A D | switchdev.rst | 172 FDB entry is the {port, MAC, VLAN} tuple forwarding destination. 179 - VLAN flooding of multicast/broadcast and unknown unicast packets 197 Note: by default, the bridge does not filter on VLAN and only bridges untagged 198 traffic. To enable VLAN support, turn on VLAN filtering:: 205 The switch device will learn/forget source MAC address/VLAN on ingress packets 286 For a given L2 VLAN domain, the switch device should flood multicast/broadcast
|
| /OK3568_Linux_fs/kernel/Documentation/networking/dsa/ |
| H A D | sja1105.rst | 39 VLAN Lookup yes yes 81 Depending on VLAN awareness state, the following operating modes are possible 84 - Mode 1 (VLAN-unaware): a port is in this mode when it is used as a standalone 86 - Mode 2 (fully VLAN-aware): a port is in this mode when it is enslaved to a 87 bridge with ``vlan_filtering=1``. Access to the entire VLAN range is given to 92 - Mode 3 (best-effort VLAN-aware): a port is in this mode when enslaved to a 97 port*), and shared VLAN learning is performed (FDB lookup is done only by 122 [ 61.204770] sja1105 spi0.1: Reset switch and programmed static config. Reason: VLAN filtering 126 [ 64.682927] sja1105 spi0.1: Reset switch and programmed static config. Reason: VLAN filtering 155 \* "maximum of 7 non-pvid VLANs per port": Decoding VLAN-tagged packets on the [all …]
|
| H 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
|
| H A D | dsa.rst | 52 on Port-based VLAN IDs). 262 - inability to configure specific VLAN IDs / trunking VLANs between switches 323 more specifically with its VLAN filtering portion when configuring VLANs on top 330 As of today, the only SWITCHDEV objects supported by DSA are the FDB and VLAN 370 a Port-based VLAN ID for each port and allowing only the CPU port and the 497 Bridge VLAN filtering 501 configured for turning on or off VLAN filtering. If nothing specific needs to 503 When VLAN filtering is turned on, the hardware must be programmed with 504 rejecting 802.1Q frames which have VLAN IDs outside of the programmed allowed 505 VLAN ID map/rules. If there is no PVID programmed into the switch port, [all …]
|
| H A D | configuration.rst | 79 without using a VLAN based configuration. 161 (DSA_TAG_PROTO_NONE). These switches can be configured by a VLAN based 166 The configuration can only be set up via VLAN tagging and bridge setup. 189 # activate VLAN filtering 231 # activate VLAN filtering 273 # activate VLAN filtering
|
| H A D | lan9303.rst | 36 - Support for VLAN filtering is not implemented 37 - The HW does not support VLAN-specific fdb entries
|
| /OK3568_Linux_fs/kernel/Documentation/networking/devlink/ |
| H A D | sja1105.rst | 30 - Can terminate VLAN-tagged traffic over switch net 34 - Can do QoS based on VLAN PCP and VLAN membership 44 - Switch uses Shared VLAN Learning (FDB lookup uses 48 port, due to a maximum number of 32 VLAN retagging
|
| /OK3568_Linux_fs/kernel/Documentation/bpf/ |
| H 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``
|
| /OK3568_Linux_fs/kernel/Documentation/s390/ |
| H 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.
|
| /OK3568_Linux_fs/buildroot/package/hostapd/ |
| H A D | Config.in | 87 bool "Enable VLAN support" 95 bool "Enable dynamic VLAN support" 100 bridge and VLAN interfaces if necessary. 103 bool "Use netlink-based API for VLAN operations" 108 Use netlink-based kernel API for VLAN operations 111 comment "netlink-based VLAN support needs a toolchain w/ threads"
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/bpf/ |
| H A D | test_xdp_vlan.sh | 177 export VLAN=4011 179 ip netns exec ns2 ip link add link $DEVNS2 name $DEVNS2.$VLAN type vlan id $VLAN 180 ip netns exec ns2 ip addr add ${IPADDR2}/24 dev $DEVNS2.$VLAN 182 ip netns exec ns2 ip link set $DEVNS2.$VLAN up
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/intel/ |
| H 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 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. 129 Where "24" and "371" are example VLAN IDs. [all …]
|
| H 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
|
| H 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::
|
| H 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
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/freescale/ |
| H 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
|
| /OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/aquantia/ |
| H 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.
|
| /OK3568_Linux_fs/kernel/net/bridge/ |
| H 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.
|
| /OK3568_Linux_fs/kernel/drivers/staging/fsl-dpaa2/ethsw/ |
| H A D | README | 98 unicast/multicast/broadcast (VLAN tagged or untagged) traffic between its 102 port VLAN configuration and STP state.
|