selftests: forwarding: Test routed bridge interface
authorPetr Machata <petrm@mellanox.com>
Mon, 25 Jun 2018 07:48:18 +0000 (10:48 +0300)
committerDavid S. Miller <davem@davemloft.net>
Tue, 26 Jun 2018 09:05:22 +0000 (18:05 +0900)
commit5b1e7f9ebd5653dc4cc026671ca07d8ab2419a99
treeb898c25f0f431fa0eef410e949eb868e98a09460
parent567ad1a2bb6c1e2ca9644d1b47263b7d5e1ff900
selftests: forwarding: Test routed bridge interface

Add test for cases where bridge itself acts as a router interface, with
front panel port attached to the bridge in question.

In the first test (router_bridge.sh), VLAN memberships are not
configured in any way, and everything uses default PVID of 1. Thus
traffic in $h1 and $h2 is untagged. This test ensures that the previous
patches didn't break a currently working scenario.

In the second test (router_bridge_vlan.sh), a VLAN 555 pvid untagged is
added to the bridge CPU port, with that VLAN leaving the bridge tagged
through its sole member port. The traffic is therefore expected to come
out tagged at $h1. This tests the fix introduced in the previous
patches.

Signed-off-by: Petr Machata <petrm@mellanox.com>
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
tools/testing/selftests/net/forwarding/router_bridge.sh [new file with mode: 0755]
tools/testing/selftests/net/forwarding/router_bridge_vlan.sh [new file with mode: 0755]