| /openbmc/openbmc-test-automation/network/ |
| H A D | test_vlan_network.robot | 40 Add VLAN Via REST And Verify
46 Create VLAN ${vlan_id}
60 Delete VLAN Via REST
86 Delete IP On VLAN Via REST
128 Create VLAN ${vlan_id}
210 Create VLAN ${vlan_id}
239 ${vlan_ids}= Get VLAN IDs
258 Set Initial VLAN Config
331 Get VLAN IDs
341 Get VLAN URI For IP
[all …]
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_network_configuration.robot | 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
89 Configure IP On VLAN Via IPMI
103 Create VLAN Via IPMI When LAN And VLAN Exist On BMC
104 [Documentation] Create VLAN Via IPMI When LAN And VLAN Exist On BMC.
130 Create VLAN Via IPMI off
136 Create VLAN When LAN And VLAN Exist With IP Address Configured
137 [Documentation] Create VLAN when LAN and VLAN exist with IP address configured.
[all …]
|
| /openbmc/linux/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"
|
| /openbmc/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
|
| /openbmc/linux/Documentation/networking/ |
| H A D | switchdev.rst | 173 FDB entry is the {port, MAC, VLAN} tuple forwarding destination.
222 traffic. To enable VLAN support, turn on VLAN filtering::
454 Bridge VLAN filtering
461 - with VLAN filtering turned off: the bridge is strictly VLAN unaware and its
468 - with VLAN filtering turned on: the bridge is VLAN-aware and frames ingressing
479 VLAN upper. The VLAN upper interface (which consumes the VLAN tag) can even
482 belonging to the VLAN upper interfaces are managed properly:
494 - with VLAN filtering turned on, these VLAN devices can be created as long as
500 way by the enabling of VLAN filtering on the bridge device(s). If the VLAN
511 ensure VLAN awareness is pushed down to the hardware.
[all …]
|
| H A D | cdc_mbim.rst | 178 VLAN ID Z for all values of Z greater than 0.
250 /* use special negative offsets to get VLAN tag */
254 /* verify DSS VLAN range */
269 Tagged IP session 0 VLAN
285 behaviour is triggered by adding a VLAN link for the magic VLAN ID
291 subdevice after the MBIM SessionID instead of the VLAN ID. For
297 VLAN mapping
304 VLAN ID MBIM type MBIM SessionID Notes
312 a) if no VLAN ID 4094 link exists, else dropped
313 b) unsupported VLAN range, unconditionally dropped
[all …]
|
| /openbmc/linux/Documentation/networking/dsa/ |
| H A D | sja1105.rst | 79 decodes the VLAN information from the 802.1Q tag. Advanced VLAN classification
113 on the VLAN PCP bits (if no VLAN is present, the port-based default is used).
124 queue with VLAN awareness active, it is necessary to create a VLAN
189 - VLAN-aware virtual links: these match on destination MAC address, VLAN ID and
190 VLAN PCP.
226 tuple composed of destination MAC address, VLAN ID and VLAN PCP). Packets which
300 VLAN-unaware, frames carry a different VLAN tag internally, depending on
303 The virtual link keys are always fixed at {MAC DA, VLAN ID, VLAN PCP}, but the
304 driver asks for the VLAN ID and VLAN PCP when the port is under a VLAN-aware
307 "VLAN-unaware" tc-flower keys (MAC DA).
[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).
476 supported by DSA are the FDB and VLAN objects.
776 VLAN-unaware bridge port should be able to find a VLAN-unaware FDB entry having
783 Similarly, each VLAN of each offloaded VLAN-aware bridge should have an
790 VLAN-aware database means that packets are supposed to match based on the VLAN
795 VLAN-unaware bridge may have VLAN-aware (non-zero VID) FDB entries, and a
796 VLAN-aware bridge may have VLAN-unaware FDB entries. As in hardware, the
935 that the packet is also VLAN-tagged with the VLAN ID that the bridge processed
972 Bridge VLAN filtering
1000 associated with this VLAN ID.
[all …]
|
| /openbmc/linux/Documentation/arch/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.
|
| /openbmc/phosphor-networkd/gen/xyz/openbmc_project/Network/VLAN/ |
| H A D | meson.build | 4 'xyz/openbmc_project/Network/VLAN/Create__markdown'.underscorify(),
5 input: [ '../../../../../yaml/xyz/openbmc_project/Network/VLAN/Create.interface.yaml', ],
13 'xyz/openbmc_project/Network/VLAN/Create',
|
| /openbmc/phosphor-networkd/yaml/xyz/openbmc_project/Network/VLAN/ |
| H A D | Create.interface.yaml | 3 - name: VLAN
14 VLAN Identifier.
19 The path for the created VLAN object.
|
| /openbmc/phosphor-networkd/gen/xyz/openbmc_project/Network/VLAN/Create/ |
| H A D | meson.build | 3 'xyz/openbmc_project/Network/VLAN/Create__cpp'.underscorify(),
4 input: [ '../../../../../../yaml/xyz/openbmc_project/Network/VLAN/Create.interface.yaml', ],
12 'xyz/openbmc_project/Network/VLAN/Create',
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/ |
| H A D | README.md | 23 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>
296 ### IPMI VLAN and IP
314 NOTE: It takes 4-5 seconds to create the VLAN and configure the IP. If a VLAN
[all …]
|
| H A D | VLAN.interface.yaml | 2 This defines VLAN specific parameters.
13 VLAN Identifier.
|
| /openbmc/linux/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``
|
| /openbmc/linux/tools/testing/selftests/bpf/ |
| H A D | test_xdp_vlan.sh | 182 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/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Network/VLAN/ |
| H A D | meson.build | 4 input: [ '../../../../../yaml/xyz/openbmc_project/Network/VLAN.interface.yaml', ],
12 'xyz/openbmc_project/Network/VLAN',
|
| /openbmc/linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| H A 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.
208 packet will reach the mirror port, if the VLAN found in the packet is not
|
| /openbmc/linux/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
|
| /openbmc/qemu/qapi/ |
| H A D | rocker.json | 127 # @vlan-id: VLAN ID
161 # @vlan-id: VLAN ID
192 # @vlan-id: VLAN ID
194 # @new-vlan-id: new VLAN ID
269 # @vlan-id: VLAN ID
279 # @set-vlan-id: VLAN ID to set
281 # @pop-vlan: pop VLAN headr from packet
|
| /openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Network/ |
| H A D | meson.build | 123 subdir('VLAN') subdir
126 input: [ '../../../../yaml/xyz/openbmc_project/Network/VLAN.interface.yaml', ],
127 output: [ 'VLAN.md' ],
134 'xyz/openbmc_project/Network/VLAN',
|
| /openbmc/qemu/tests/rocker/ |
| H A D | all | 13 printf "Running bridge VLAN test... "
17 printf "Running bridge VLAN STP test... "
|
| /openbmc/linux/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
119 IDs within a single Ethernet frame. VLAN IDs are sometimes referred to as
122 VLAN ID, among other uses.
129 Where "24" and "371" are example VLAN IDs.
132 Receive checksum offloads, cloud filters, and VLAN acceleration are not
241 trusted mode, refer to the section "VLAN Tag Packet Steering" in this
[all …]
|