It is now possible to ping the vtep addresses from both ends:
root@Device_A:~# ping -c1 192.168.255.1; ping -c1 192.168.255.2
PING 192.168.255.1 (192.168.255.1): 56 data bytes
64 bytes from 192.168.255.1: seq=0 ttl=64 time=0.398 ms
--- 192.168.255.1 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.398/0.398/0.398 ms
PING 192.168.255.2 (192.168.255.2): 56 data bytes
64 bytes from 192.168.255.2: seq=0 ttl=64 time=1.427 ms
--- 192.168.255.2 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 1.427/1.427/1.427 ms
root@Device_B:~# ping -c1 192.168.255.2; ping -c1 192.168.255.1
PING 192.168.255.2 (192.168.255.2): 56 data bytes
64 bytes from 192.168.255.2: seq=0 ttl=64 time=0.389 ms
--- 192.168.255.2 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.389/0.389/0.389 ms
PING 192.168.255.1 (192.168.255.1): 56 data bytes
64 bytes from 192.168.255.1: seq=0 ttl=64 time=1.528 ms
--- 192.168.255.1 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 1.528/1.528/1.528 ms
Whilst possible to ping vtep addresses from each end, the traffic is not shown on tcpdump?
root@Device_A:~# tcpdump -ni vxlan0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vxlan0, link-type EN10MB (Ethernet), capture size 262144 bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel
root@Device_B:~# tcpdump -ni vxlan0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vxlan0, link-type EN10MB (Ethernet), capture size 262144 bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel
If the wan cable is unplugged, it is not possible to ping the remote vtep address, so it is surely being used.
Regarding the other devices, it is not possible to reach other devices via the bridge segment:
Lan client1:
[pcaetano@fedora pcaetano]$ ip -br a
lo UNKNOWN 127.0.0.1/8 ::1/128
enp0s13f0u3 UP 192.168.2.101/24 fe80::c363:209c:ae32:b3d1/64
[pcaetano@fedora pcaetano]$ ping -c 5 192.168.2.102
PING 192.168.2.102 (192.168.2.102) 56(84) bytes of data.
From 192.168.2.101 icmp_seq=1 Destination Host Unreachable
From 192.168.2.101 icmp_seq=2 Destination Host Unreachable
From 192.168.2.101 icmp_seq=3 Destination Host Unreachable
From 192.168.2.101 icmp_seq=4 Destination Host Unreachable
From 192.168.2.101 icmp_seq=5 Destination Host Unreachable
Output from tcpdump on both devices:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br-lan, link-type EN10MB (Ethernet), capture size 262144 bytes
11:47:58.940273 00:e0:4c:68:16:ee > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.2.102 tell 192.168.2.101, length 46
11:47:59.958099 00:e0:4c:68:16:ee > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.2.102 tell 192.168.2.101, length 46
11:48:00.983061 00:e0:4c:68:16:ee > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.2.102 tell 192.168.2.101, length 46
11:48:02.006284 00:e0:4c:68:16:ee > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.2.102 tell 192.168.2.101, length 46
11:48:03.029978 00:e0:4c:68:16:ee > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.2.102 tell 192.168.2.101, length 46
11:48:04.053962 00:e0:4c:68:16:ee > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.2.102 tell 192.168.2.101, length 46
^C
6 packets captured
6 packets received by filter
0 packets dropped by kernel
root@Device_B:~# tcpdump -e -ni br-lan not port 80 and not port 22
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br-lan, link-type EN10MB (Ethernet), capture size 262144 bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel
Output from bridge fdb show
below:
root@Device_A:~# bridge fdb show
33:33:00:00:00:01 dev eth0 self permanent
33:33:00:00:00:02 dev eth0 self permanent
01:00:5e:00:00:01 dev eth0 self permanent
33:33:ff:6a:d7:eb dev eth0 self permanent
33:33:ff:00:00:00 dev eth0 self permanent
00:e0:4c:68:16:ee dev eth1 master br-lan
6a:78:6d:6a:d7:ea dev eth1 vlan 1 master br-lan permanent
6a:78:6d:6a:d7:ea dev eth1 master br-lan permanent
33:33:00:00:00:01 dev eth1 self permanent
33:33:00:00:00:02 dev eth1 self permanent
01:00:5e:00:00:01 dev eth1 self permanent
33:33:00:00:00:01 dev br-lan self permanent
33:33:00:00:00:02 dev br-lan self permanent
01:00:5e:00:00:01 dev br-lan self permanent
33:33:ff:00:00:01 dev br-lan self permanent
33:33:ff:6a:d7:ea dev br-lan self permanent
33:33:ff:00:00:00 dev br-lan self permanent
00:00:00:00:00:00 dev vxlan0 dst 10.0.0.20 via br-lan self permanent
root@Device_B:~# bridge fdb show
33:33:00:00:00:01 dev eth0 self permanent
33:33:00:00:00:02 dev eth0 self permanent
01:00:5e:00:00:01 dev eth0 self permanent
33:33:ff:6a:d7:ed dev eth0 self permanent
33:33:ff:00:00:00 dev eth0 self permanent
e4:11:5b:29:8f:7e dev eth1 master br-lan
6a:78:6d:6a:d7:ec dev eth1 vlan 1 master br-lan permanent
6a:78:6d:6a:d7:ec dev eth1 master br-lan permanent
33:33:00:00:00:01 dev eth1 self permanent
33:33:00:00:00:02 dev eth1 self permanent
01:00:5e:00:00:01 dev eth1 self permanent
33:33:00:00:00:01 dev br-lan self permanent
33:33:00:00:00:02 dev br-lan self permanent
01:00:5e:00:00:01 dev br-lan self permanent
33:33:00:01:00:02 dev br-lan self permanent
33:33:00:01:00:03 dev br-lan self permanent
00:00:00:00:00:00 dev vxlan0 dst 10.0.0.10 via br-lan self permanent
EDIT: wrong tcpdump output posted