diff mbox series

selftests: net: test_vxlan_under_vrf: fix HV connectivity test

Message ID 20211105155529.105545-1-andrea.righi@canonical.com (mailing list archive)
State Accepted
Commit e7e4785fa30f9b5d1b60ed2d8e221891325dfc5f
Headers show
Series selftests: net: test_vxlan_under_vrf: fix HV connectivity test | expand

Commit Message

Andrea Righi Nov. 5, 2021, 3:55 p.m. UTC
It looks like test_vxlan_under_vrf.sh is always failing to verify the
connectivity test during the ping between the two simulated VMs.

This is due to the fact that veth-hv in each VM should have a distinct
MAC address.

Fix by setting a unique MAC address on each simulated VM interface.

Without this fix:

 $ sudo ./tools/testing/selftests/net/test_vxlan_under_vrf.sh
 Checking HV connectivity                                           [ OK ]
 Check VM connectivity through VXLAN (underlay in the default VRF)  [FAIL]

With this fix applied:

 $ sudo ./tools/testing/selftests/net/test_vxlan_under_vrf.sh
 Checking HV connectivity                                           [ OK ]
 Check VM connectivity through VXLAN (underlay in the default VRF)  [ OK ]
 Check VM connectivity through VXLAN (underlay in a VRF)            [FAIL]

NOTE: the connectivity test with the underlay VRF is still failing; it
seems that ARP requests are blocked at the simulated hypervisor level,
probably due to some missing ARP forwarding rules. This requires more
investigation (in the meantime we may consider to set that test as
expected failure - XFAIL).

Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
---
 tools/testing/selftests/net/test_vxlan_under_vrf.sh | 2 ++
 1 file changed, 2 insertions(+)

Comments

patchwork-bot+netdevbpf@kernel.org Nov. 10, 2021, 2:40 p.m. UTC | #1
Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri,  5 Nov 2021 16:55:29 +0100 you wrote:
> It looks like test_vxlan_under_vrf.sh is always failing to verify the
> connectivity test during the ping between the two simulated VMs.
> 
> This is due to the fact that veth-hv in each VM should have a distinct
> MAC address.
> 
> Fix by setting a unique MAC address on each simulated VM interface.
> 
> [...]

Here is the summary with links:
  - selftests: net: test_vxlan_under_vrf: fix HV connectivity test
    https://git.kernel.org/netdev/net/c/e7e4785fa30f

You are awesome, thank you!
diff mbox series

Patch

diff --git a/tools/testing/selftests/net/test_vxlan_under_vrf.sh b/tools/testing/selftests/net/test_vxlan_under_vrf.sh
index 534c8b7699ab..ea5a7a808f12 100755
--- a/tools/testing/selftests/net/test_vxlan_under_vrf.sh
+++ b/tools/testing/selftests/net/test_vxlan_under_vrf.sh
@@ -101,6 +101,8 @@  setup-vm() {
     ip -netns hv-$id link set veth-tap master br0
     ip -netns hv-$id link set veth-tap up
 
+    ip link set veth-hv address 02:1d:8d:dd:0c:6$id
+
     ip link set veth-hv netns vm-$id
     ip -netns vm-$id addr add 10.0.0.$id/24 dev veth-hv
     ip -netns vm-$id link set veth-hv up