Home
last modified time | relevance | path

Searched refs:VLAN (Results 1 – 25 of 95) sorted by relevance

1234

/openbmc/openbmc-test-automation/network/
H A Dtest_vlan_network.robot2 Documentation Test setting VLAN and its configuration.
28 ${vlan_resource} ${NETWORK_MANAGER}action/VLAN
40 Add VLAN Via REST And Verify
41 [Documentation] Add VLAN via REST and verify it via REST and IPMI.
46 Create VLAN ${vlan_id}
47 Verify Existence Of VLAN ${vlan_id}
50 Valid Value lan_config['802.1q VLAN ID'] ["${vlan_id}"]
53 Add Invalid VLAN Via REST And Verify
54 [Documentation] Add Invalid VLAN via REST and verify.
57 Create VLAN ${invalid_vlan_id} expected_result=error
[all …]
/openbmc/openbmc-test-automation/ipmi/
H A Dtest_ipmi_network_configuration.robot27 ${vlan_resource} ${NETWORK_MANAGER}action/VLAN
75 Disable VLAN Via IPMI When Multiple VLAN Exist On BMC
76 [Documentation] Disable VLAN Via IPMI When Multiple VLAN Exist On BMC.
80 Create VLAN ${vlan_id}
83 Create VLAN Via IPMI off
86 Valid Value lan_config['802.1q VLAN ID'] ['Disabled']
89 Configure IP On VLAN Via IPMI
90 [Documentation] Configure IP On VLAN Via IPMI.
93 Create VLAN Via IPMI ${vlan_id_for_ipmi}
99 Valid Value lan_config['802.1q VLAN ID'] ['${vlan_id_for_ipmi}']
[all …]
/openbmc/linux/net/8021q/
H A DKconfig3 # 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"
/openbmc/u-boot/doc/
H A DREADME.t1040-l2switch11 - 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 DREADME.VLAN4 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
/openbmc/linux/Documentation/networking/
H A Dswitchdev.rst173 FDB entry is the {port, MAC, VLAN} tuple forwarding destination.
180 - VLAN flooding of multicast/broadcast and unknown unicast packets
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
310 For a given L2 VLAN domain, the switch device should flood multicast/broadcast
427 use per-port VLAN identifiers unless a better mechanism is available
432 appropriate filters for VLAN, multicast, unicast etc. The underlying device
440 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 …]
H A Dcdc_mbim.rst176 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 Dnf_flowtable.rst28 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
/openbmc/linux/Documentation/networking/dsa/
H A Dsja1105.rst41 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 …]
H A Db53.rst51 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 Ddsa.rst52 on Port-based VLAN IDs).
416 - inability to configure specific VLAN IDs / trunking VLANs between switches
474 more specifically with its VLAN filtering portion when configuring VLANs on top
476 supported by DSA are the FDB and VLAN objects.
492 tables and VLAN tables. For example, this might be useful if the tables
501 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 the
772 For example, all ports that belong to a VLAN-unaware bridge (which is
773 *currently* VLAN-unaware) are expected to learn source addresses in the
775 VLAN-unaware bridges). During forwarding and FDB lookup, a packet received on a
[all …]
/openbmc/phosphor-networkd/gen/xyz/openbmc_project/Network/VLAN/
H A Dmeson.build4 sdbusplus_current_path = 'xyz/openbmc_project/Network/VLAN'
7 'xyz/openbmc_project/Network/VLAN/Create__markdown'.underscorify(),
8 input: [ '../../../../../yaml/xyz/openbmc_project/Network/VLAN/Create.interface.yaml', ],
16 'xyz/openbmc_project/Network/VLAN/Create',
/openbmc/phosphor-networkd/gen/xyz/openbmc_project/Network/VLAN/Create/
H A Dmeson.build3 sdbusplus_current_path = 'xyz/openbmc_project/Network/VLAN/Create'
6 'xyz/openbmc_project/Network/VLAN/Create__cpp'.underscorify(),
8 '../../../../../../yaml/xyz/openbmc_project/Network/VLAN/Create.interface.yaml',
23 'xyz/openbmc_project/Network/VLAN/Create',
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/
H A DREADME.md23 5. VLANInterface: This describes the VLAN specific properties.
246 ### VLAN subsection
252 xyz.openbmc_project.Network.VLAN.Create VLAN su "<interface>" <VLAN id>
257 -d '{"data":["<interface>", <VLAN id>] }' \
258 https://${bmc}/xyz/openbmc_project/network/action/VLAN
266 https://${bmc}/xyz/openbmc_project/network/action/VLAN
273 /xyz/openbmc_project/network/<VLAN interface> \
279 https://${bmc}/xyz/openbmc_project/network/<VLAN interface>
293 https://${bmc}/xyz/openbmc_project/network/<VLAN interface>/enumerate
296 ### IPMI VLAN and IP
[all …]
/openbmc/linux/Documentation/arch/s390/
H A Dqeth.rst33 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.
/openbmc/linux/Documentation/bpf/
H A Dprog_flow_dissector.rst41 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``
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Network/VLAN/
H A Dmeson.build3 sdbusplus_current_path = 'xyz/openbmc_project/Network/VLAN'
8 '../../../../../yaml/xyz/openbmc_project/Network/VLAN.interface.yaml',
28 'xyz/openbmc_project/Network/VLAN',
/openbmc/linux/tools/testing/selftests/bpf/
H A Dtest_xdp_vlan.sh182 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
/openbmc/linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/
H A Dswitch-driver.rst89 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
/openbmc/qemu/qapi/
H A Drocker.json131 # @vlan-id: VLAN ID
165 # @vlan-id: VLAN ID
196 # @vlan-id: VLAN ID
198 # @new-vlan-id: new VLAN ID
273 # @vlan-id: VLAN ID
283 # @set-vlan-id: VLAN ID to set
285 # @pop-vlan: pop VLAN headr from packet
/openbmc/linux/Documentation/networking/device_drivers/ethernet/intel/
H A Diavf.rst70 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 …]
/openbmc/linux/Documentation/networking/device_drivers/ethernet/freescale/
H A Dgianfar.rst22 VLAN chapter
25 In order to use VLAN, please consult Linux documentation on
27 extraction of VLAN headers, but not filtering. Filtering will be
/openbmc/qemu/tests/rocker/
H A Dall13 printf "Running bridge VLAN test... "
17 printf "Running bridge VLAN STP test... "
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Network/
H A Dmeson.build11 subdir('VLAN') subdir
207 input: ['../../../../yaml/xyz/openbmc_project/Network/VLAN.interface.yaml'],
208 output: ['VLAN.md'],
220 'xyz/openbmc_project/Network/VLAN',
/openbmc/phosphor-host-ipmid/docs/
H A Dipmitool-commands-cheatsheet.md27 ### Set the VLAN
31 ### Delete the VLAN

1234