Searched refs:VLAN (Results 1 – 25 of 45) sorted by relevance
12
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"
169 channel. The cdc_mbim driver models such IP sessions as 802.1q VLAN171 VLAN ID Z for all values of Z greater than 0.177 VLAN links prior to establishing MBIM IP sessions where the SessionId178 is greater than 0. These links can be added by using the normal VLAN193 sessions as another set of 802.1q VLAN subdevices of the master wwanY194 device, mapping MBIM DSS session A to VLAN ID (256 + A) for all values200 The DSS VLAN subdevices are used as a practical interface between the232 Note that adding VLAN links for DSS sessions is entirely optional. A234 directly to the master network device, using the received VLAN tags to235 map frames to the correct DSS session and adding 18 byte VLAN ethernet[all …]
7 VLAN processing, network access control, flow-based network control,164 did not already implement VLAN parsing. Instead, it just interpreted171 Naively, to add VLAN support, it makes sense to add a new "vlan" flow172 key attribute to contain the VLAN tag, then continue to decode the173 encapsulated headers beyond the VLAN tag using the existing field174 definitions. With this change, a TCP packet in VLAN 10 would have a190 VLAN 10 is actually expressed as:223 indicating that a VLAN TCI should follow, but which is truncated just230 all-zero-bits VLAN TCI is not that rare, so the CFI bit (aka234 missing or malformed VLAN TCI.
31 by child VLAN devices (limits netdev->features set). This is currently32 used for all VLAN devices whether tags are stripped or inserted in154 * VLAN challenged156 NETIF_F_VLAN_CHALLENGED should be set for devices which can't cope with VLAN158 [FIXME: Those cases could be fixed in VLAN code by allowing only reduced-MTU
5 problem of limited VLAN IDs (4096) in IEEE 802.1q. With VXLAN the20 neighbors GRE and VLAN. Configuring VXLAN requires the version of
19 indentifier (FID) based on the ingress port and VLAN. This trap is used
162 FDB entry is the {port, MAC, VLAN} tuple forwarding destination.169 - VLAN flooding of multicast/broadcast and unknown unicast packets187 Note: by default, the bridge does not filter on VLAN and only bridges untagged188 traffic. To enable VLAN support, turn on VLAN filtering:195 The switch device will learn/forget source MAC address/VLAN on ingress packets276 For a given L2 VLAN domain, the switch device should flood multicast/broadcast
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``
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.
39 VLAN Lookup yes yes70 customizing the TPID by which VLAN traffic is identified as such. The switch75 because the switch does no longer parse those packets as VLAN after the TPID104 one bridge's ports from another's) or at the VLAN port membership level108 The hardware tags all traffic internally with a port-based VLAN (pvid), or it109 decodes the VLAN information from the 802.1Q tag. Advanced VLAN classification110 is not possible. Once attributed a VLAN tag, frames are checked against the111 port's membership rules and dropped at ingress if they don't match any VLAN.115 Normally the hardware is not configurable with respect to VLAN awareness, but121 all bridges should have the same level of VLAN awareness (either both have[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).262 - inability to configure specific VLAN IDs / trunking VLANs between switches323 more specifically with its VLAN filtering portion when configuring VLANs on top330 As of today, the only SWITCHDEV objects supported by DSA are the FDB and VLAN370 a Port-based VLAN ID for each port and allowing only the CPU port and the497 Bridge VLAN filtering501 configured for turning on or off VLAN filtering. If nothing specific needs to503 When VLAN filtering is turned on, the hardware must be programmed with504 rejecting 802.1Q frames which have VLAN IDs outside of the programmed allowed505 VLAN ID map/rules. If there is no PVID programmed into the switch port,[all …]
36 - Support for VLAN filtering is not implemented37 - The HW does not support VLAN-specific fdb entries
79 without using a VLAN based configuration.161 (DSA_TAG_PROTO_NONE). These switches can be configured by a VLAN based166 The configuration can only be set up via VLAN tagging and bridge setup.189 # activate VLAN filtering231 # activate VLAN filtering273 # activate VLAN filtering
177 export VLAN=4011179 ip netns exec ns2 ip link add link $DEVNS2 name $DEVNS2.$VLAN type vlan id $VLAN180 ip netns exec ns2 ip addr add ${IPADDR2}/24 dev $DEVNS2.$VLAN182 ip netns exec ns2 ip link set $DEVNS2.$VLAN up
17 VLAN19 In order to use VLAN, please consult Linux documentation on21 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::
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.
229 1. 16 VLAN ID rules246 - Locations 0 - 15 for VLAN ID filters285 The VLAN filter (VLAN id) is compared against 16 filters.286 VLAN id must be accompanied by mask 0xF000. That is to distinguish VLAN filter287 from L2 Ethertype filter with UserPriority since both User Priority and VLAN ID290 To add a filter that directs packets from VLAN 2001 to queue 5:297 distinguish VLAN filter from L2 Ethertype filter with UserPriority since both298 User Priority and VLAN ID are passed in the same 'vlan' parameter.
23 tristate "Tag driver for switches using custom 802.1Q VLAN headers"28 VLAN in one way or another. It is not a complete solution.102 on a custom 802.1Q VLAN header) are available.
35 VLAN, enumerator132 bpf_tail_call(skb, &jmp_table, VLAN); in parse_eth_proto()388 PROG(VLAN)(struct __sk_buff *skb) in PROG() argument
98 unicast/multicast/broadcast (VLAN tagged or untagged) traffic between its102 port VLAN configuration and STP state.
15 Furthermore, the Broadcom FCoE offload solution creates VLAN interfaces to63 <INTERFACE>.<VLAN>-fcoe interfaces are automatically created.
