linux.git/tools/testing/selftests/net/forwarding, branch v5.17

selftests: forwarding: Add Q-in-VNI test for IPv6

2021-12-23T01:14:34+00:00

Add test to check Q-in-VNI traffic with IPv6 underlay and overlay.
The test is similar to the existing IPv4 test.

Signed-off-by: Amit Cohen 
Reviewed-by: Petr Machata 
Signed-off-by: Jakub Kicinski

selftests: forwarding: Add a test for VxLAN symmetric routing with IPv6

2021-12-23T01:14:34+00:00

In a similar fashion to the asymmetric test, add a test for symmetric
routing. In symmetric routing both the ingress and egress VTEPs perform
routing in the overlay network into / from the VxLAN tunnel. Packets in
different directions use the same VNI - the L3 VNI.
Different tenants (VRFs) use different L3 VNIs.

Add a test which is similar to the existing IPv4 test to check IPv6.

Signed-off-by: Amit Cohen 
Reviewed-by: Petr Machata 
Signed-off-by: Jakub Kicinski

selftests: forwarding: Add a test for VxLAN asymmetric routing with IPv6

2021-12-23T01:14:34+00:00

In asymmetric routing the ingress VTEP routes the packet into the
correct VxLAN tunnel, whereas the egress VTEP only bridges the packet to
the correct host. Therefore, packets in different directions use
different VNIs - the target VNI.

Add a test which is similar to the existing IPv4 test to check IPv6.

The test uses a simple topology with two VTEPs and two VNIs and verifies
that ping passes between hosts (local / remote) in the same VLAN (VNI)
and in different VLANs belonging to the same tenant (VRF).

While the test does not check VM mobility, it does configure an anycast
gateway using a macvlan device on both VTEPs.

Signed-off-by: Amit Cohen 
Reviewed-by: Petr Machata 
Signed-off-by: Jakub Kicinski

selftests: forwarding: vxlan_bridge_1q: Remove unused function

2021-12-23T01:14:33+00:00

Remove `vxlan_ping_test()` which is not used and probably was copied
mistakenly from vxlan_bridge_1d.sh.

This was found while adding an equivalent test for IPv6.

Signed-off-by: Amit Cohen 
Reviewed-by: Petr Machata 
Signed-off-by: Jakub Kicinski

selftests: forwarding: Add VxLAN tests with a VLAN-aware bridge for IPv6

2021-12-23T01:14:33+00:00

The tests are very similar to their VLAN-unaware counterpart
(vxlan_bridge_1d_ipv6.sh and vxlan_bridge_1d_port_8472_ipv6.sh),
but instead of using multiple VLAN-unaware bridges, a single VLAN-aware
bridge is used with multiple VLANs.

Signed-off-by: Amit Cohen 
Reviewed-by: Petr Machata 
Signed-off-by: Jakub Kicinski

selftests: forwarding: Add VxLAN tests with a VLAN-unaware bridge for IPv6

2021-12-23T01:14:32+00:00

Add tests similar to vxlan_bridge_1d.sh and vxlan_bridge_1d_port_8472.sh.

The tests set up a topology with three VxLAN endpoints: one
"local", possibly offloaded, and two "remote", formed using veth pairs
and likely purely software bridges. The "local" endpoint is connected to
host systems by a VLAN-unaware bridge.

Since VxLAN tunnels must be unique per namespace, each of the "remote"
endpoints is in its own namespace. H3 forms the bridge between the three
domains.

Send IPv4 packets and IPv6 packets with IPv6 underlay.
Use `TC_FLAG`, which is defined in `forwarding.config` file, for TC
checks. `TC_FLAG` allows testing that on HW datapath, the traffic
actually goes through HW.

Signed-off-by: Amit Cohen 
Reviewed-by: Petr Machata 
Signed-off-by: Jakub Kicinski

selftests: lib.sh: Add PING_COUNT to allow sending configurable amount of packets

2021-12-23T01:14:32+00:00

Currently `ping_do()` and `ping6_do()` send 10 packets.

There are cases that it is not possible to catch only the interesting
packets using tc rule, so then, it is possible to send many packets and
verify that at least this amount of packets hit the rule.

Add `PING_COUNT` variable, which is set to 10 by default, to allow tests
sending more than 10 packets using the existing ping API.

Signed-off-by: Amit Cohen 
Reviewed-by: Petr Machata 
Signed-off-by: Jakub Kicinski

Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net

2021-12-17T00:13:19+00:00

No conflicts.

Signed-off-by: Jakub Kicinski

selftest/net/forwarding: declare NETIFS p9 p10

2021-12-13T14:54:15+00:00

The recent GRE selftests defined NUM_NETIFS=10. If the users copy
forwarding.config.sample to forwarding.config directly, they will get
error "Command line is not complete" when run the GRE tests, because
create_netif_veth() failed with no interface name defined.

Fix it by extending the NETIFS with p9 and p10.

Fixes: 2800f2485417 ("selftests: forwarding: Test multipath hashing on inner IP pkts for GRE tunnel")
Signed-off-by: Hangbin Liu 
Reviewed-by: Ido Schimmel 
Signed-off-by: David S. Miller

selftests: net: bridge: fix typo in vlan_filtering dependency test

2021-11-29T12:49:53+00:00

Prior patch:
]# TESTS=vlmc_filtering_test ./bridge_vlan_mcast.sh
TEST: Vlan multicast snooping enable                                [ OK ]
Device "bridge" does not exist.
TEST: Disable multicast vlan snooping when vlan filtering is disabled   [FAIL]
        Vlan filtering is disabled but multicast vlan snooping is still enabled

After patch:
# TESTS=vlmc_filtering_test ./bridge_vlan_mcast.sh
TEST: Vlan multicast snooping enable                                [ OK ]
TEST: Disable multicast vlan snooping when vlan filtering is disabled   [ OK ]

Fixes: f5a9dd58f48b7c ("selftests: net: bridge: add test for vlan_filtering dependency")
Cc: Nikolay Aleksandrov 
Signed-off-by: Ivan Vecera 
Acked-by: Nikolay Aleksandrov 
Signed-off-by: David S. Miller