diff options
| author | Vladimir Oltean <[email protected]> | 2024-08-15 03:07:01 +0300 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2024-08-16 09:59:32 +0100 |
| commit | e29b82ef27616777e21c07dc263a8769cbdaa358 (patch) | |
| tree | e1a73f3cc790ffec4d4c6ff5c188562728edaf30 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 237979504264912a9797dabc0db35126e705fe0d (diff) | |
selftests: net: bridge_vlan_aware: test that other TPIDs are seen as untagged
The bridge VLAN implementation w.r.t. VLAN protocol is described in
merge commit 1a0b20b25732 ("Merge branch 'bridge-next'"). We are only
sensitive to those VLAN tags whose TPID is equal to the bridge's
vlan_protocol. Thus, an 802.1ad VLAN should be treated as 802.1Q-untagged.
Add 3 tests which validate that:
- 802.1ad-tagged traffic is learned into the PVID of an 802.1Q-aware
bridge
- Double-tagged traffic is forwarded when just the PVID of the port is
present in the VLAN group of the ports
- Double-tagged traffic is not forwarded when the PVID of the port is
absent from the VLAN group of the ports
The test passes with both veth and ocelot.
Signed-off-by: Vladimir Oltean <[email protected]>
Reviewed-by: Ido Schimmel <[email protected]>
Tested-by: Ido Schimmel <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions