Searched refs:VLAN (Results 1 – 25 of 56) sorted by relevance
123
3 # Configuration for 802.1Q VLAN support7 tristate "802.1Q/802.1ad VLAN Support"9 Select this and you will be able to create 802.1Q VLAN interfaces10 on your Ethernet interfaces. 802.1Q VLAN supports almost14 See the VLAN web page for more information:23 bool "GVRP (GARP VLAN Registration Protocol) support"33 bool "MVRP (Multiple VLAN Registration Protocol) support"
173 FDB entry is the {port, MAC, VLAN} tuple forwarding destination.180 - VLAN flooding of multicast/broadcast and unknown unicast packets221 Note: by default, the bridge does not filter on VLAN and only bridges untagged222 traffic. To enable VLAN support, turn on VLAN filtering::229 The switch device will learn/forget source MAC address/VLAN on ingress packets310 For a given L2 VLAN domain, the switch device should flood multicast/broadcast427 use per-port VLAN identifiers unless a better mechanism is available432 appropriate filters for VLAN, multicast, unicast etc. The underlying device440 of a VLAN-aware bridge doing ingress VID checking). See below for details.442 If the device implements e.g.: VLAN filtering, putting the interface in[all …]
176 channel. The cdc_mbim driver models such IP sessions as 802.1q VLAN178 VLAN ID Z for all values of Z greater than 0.184 VLAN links prior to establishing MBIM IP sessions where the SessionId185 is greater than 0. These links can be added by using the normal VLAN200 sessions as another set of 802.1q VLAN subdevices of the master wwanY201 device, mapping MBIM DSS session A to VLAN ID (256 + A) for all values207 The DSS VLAN subdevices are used as a practical interface between the240 Note that adding VLAN links for DSS sessions is entirely optional. A242 directly to the master network device, using the received VLAN tags to243 map frames to the correct DSS session and adding 18 byte VLAN ethernet[all …]
28 n-tuple selectors: layer 2 protocol encapsulation (VLAN and PPPoE), layer 3124 netdevice behind VLAN and PPPoE netdevices. The flowtable software datapath125 parses the VLAN and PPPoE layer 2 headers to extract the ethertype and the126 VLAN ID / PPPoE session ID which are used for the flowtable lookups. The129 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 actions158 such as PVID and untagged. You can also stack a classic VLAN device on top of
10 VLAN processing, network access control, flow-based network control,167 did not already implement VLAN parsing. Instead, it just interpreted174 Naively, to add VLAN support, it makes sense to add a new "vlan" flow175 key attribute to contain the VLAN tag, then continue to decode the176 encapsulated headers beyond the VLAN tag using the existing field177 definitions. With this change, a TCP packet in VLAN 10 would have a193 VLAN 10 is actually expressed as::226 indicating that a VLAN TCI should follow, but which is truncated just233 all-zero-bits VLAN TCI is not that rare, so the CFI bit (aka237 missing or malformed VLAN TCI.
34 by child VLAN devices (limits netdev->features set). This is currently35 used for all VLAN devices whether tags are stripped or inserted in157 * VLAN challenged159 NETIF_F_VLAN_CHALLENGED should be set for devices which can't cope with VLAN161 [FIXME: Those cases could be fixed in VLAN code by allowing only reduced-MTU
8 problem of limited VLAN IDs (4096) in IEEE 802.1q. With VXLAN the23 neighbors GRE and VLAN. Configuring VXLAN requires the version of
41 VLAN Lookup yes yes74 one bridge's ports from another's) or at the VLAN port membership level78 The hardware tags all traffic internally with a port-based VLAN (pvid), or it79 decodes the VLAN information from the 802.1Q tag. Advanced VLAN classification80 is not possible. Once attributed a VLAN tag, frames are checked against the81 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, but91 all bridges should have the same level of VLAN awareness (either both have113 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 …]
51 VLAN programming would basically change the CPU port's default PVID and make55 the default VLAN 1 has to be removed from the slave interface configuration in57 VLAN configuration in the bridge showcase.61 The configuration can only be set up via VLAN tagging and bridge setup.85 # activate VLAN filtering128 # activate VLAN filtering165 # activate VLAN filtering
52 on Port-based VLAN IDs).416 - inability to configure specific VLAN IDs / trunking VLANs between switches474 more specifically with its VLAN filtering portion when configuring VLANs on top476 supported by DSA are the FDB and VLAN objects.492 tables and VLAN tables. For example, this might be useful if the tables501 utilization of certain hardware tables in the device, such as FDB, VLAN, etc.628 a Port-based VLAN ID for each port and allowing only the CPU port and the772 For example, all ports that belong to a VLAN-unaware bridge (which is773 *currently* VLAN-unaware) are expected to learn source addresses in the775 VLAN-unaware bridges). During forwarding and FDB lookup, a packet received on a[all …]
36 - Support for VLAN filtering is not implemented37 - The HW does not support VLAN-specific fdb entries
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 or42 VLAN=numeric-vlan-id43 VLAN ID on which the event occurred. Not included44 if no VLAN is involved in the event.49 event reports the creation or destruction of a VLAN.
41 In the VLAN-less case, this is what the initial state of the BPF flow58 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 dissector99 the optional VLAN header and should gracefully handle both cases: when single100 or double VLAN is present and when it is not present. The same program142 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``
182 export VLAN=4011184 ip netns exec ${NS2} ip link add link $DEVNS2 name $DEVNS2.$VLAN type vlan id $VLAN185 ip netns exec ${NS2} ip addr add ${IPADDR2}/24 dev $DEVNS2.$VLAN187 ip netns exec ${NS2} ip link set $DEVNS2.$VLAN up
89 The hardware is not configurable with respect to VLAN awareness, thus any DPAA290 switch port should be used only in usecases with a VLAN aware bridge::96 Error: fsl_dpaa2_switch: Cannot join a VLAN-unaware bridge138 * VLAN: vlan_id/vlan_prio/vlan_tpid/vlan_dei179 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 be193 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
22 VLAN chapter25 In order to use VLAN, please consult Linux documentation on27 extraction of VLAN headers, but not filtering. Filtering will be
70 Setting VLAN Tag Stripping73 packets with VLAN tags, you can disable VLAN tag stripping for the VF. The75 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 command118 The IEEE 802.1ad standard, informally known as QinQ, allows for multiple VLAN119 IDs within a single Ethernet frame. VLAN IDs are sometimes referred to as120 "tags," and multiple VLAN IDs are thus referred to as a "tag stack." Tag stacks122 VLAN ID, among other uses.129 Where "24" and "371" are example VLAN IDs.[all …]
76 NOTE: When either SR-IOV mode or VMDq mode is enabled, hardware VLAN filtering77 and VLAN tag stripping/insertion will remain enabled. Please remove the old78 VLAN filter before the new VLAN filter is added. For example::162 MAC and VLAN anti-spoofing feature174 Setting MAC Address, VLAN and Rate Limit Using IProute2 Tool176 You can set a MAC address of a Virtual Function (VF), a default VLAN and the
48 NOTE: When SR-IOV mode is enabled, hardware VLAN filtering and VLAN tag49 stripping/insertion will remain enabled. Please remove the old VLAN filter50 before the new VLAN filter is added. For example::
71 unintended traffic streams, configure all SR-IOV enabled ports for VLAN tagging75 See "Configuring VLAN Tagging on SR-IOV Enabled Adapter Ports" later in this499 Configuring VLAN Tagging on SR-IOV Enabled Adapter Ports501 To configure VLAN tagging for the ports on an SR-IOV enabled adapter, use the502 following command. The VLAN configuration should be done before the VF driver503 is loaded or the VM is booted. The VF is not aware of the VLAN tag being505 VLAN" mode).511 For example, the following will configure PF eth0 and the first VF on VLAN 10::589 Next, add a VLAN interface on the VF interface. For example::594 VLAN interface does not matter (you can do either first). The result in this[all …]
261 1. 16 VLAN ID rules279 - Locations 0 - 15 for VLAN ID filters320 The VLAN filter (VLAN id) is compared against 16 filters.321 VLAN id must be accompanied by mask 0xF000. That is to distinguish VLAN filter322 from L2 Ethertype filter with UserPriority since both User Priority and VLAN ID325 To add a filter that directs packets from VLAN 2001 to queue 5::333 distinguish VLAN filter from L2 Ethertype filter with UserPriority since both334 User Priority and VLAN ID are passed in the same 'vlan' parameter.
52 bool "VLAN filtering"58 receive and forward traffic based on VLAN information in the packet59 any VLAN information configured on the bridge port or bridge device.
79 VLAN configuration84 bridge vlan add dev br0 vid 1 pvid untagged self <---- add cpu port to VLAN 1143 default VLAN (default_pvid).
18 Furthermore, the Broadcom FCoE offload solution creates VLAN interfaces to69 <INTERFACE>.<VLAN>-fcoe interfaces are automatically created.
36 #define VLAN 5 macro133 bpf_tail_call_static(skb, &jmp_table, VLAN); in parse_eth_proto()404 PROG(VLAN)(struct __sk_buff *skb) in PROG() argument
