Bug pinging from node selecting bridge interface name

hatman

New Member
Oct 13, 2021
2
0
1
41
Hey guys,

Came across a issue that I thought I would share with the community in case you spend hours like i did sanity testing you config to discover it's a potential bug.

I've been working on a build configured as a routed nat and when testing that everything was configuered correctly I discovered I couldn't ping if I selected vmbr0 as the source however if I used the IP address associated with that interface it worked fine. Please see below from my example.

root@nodes1:~# ping -I 172.16.1.1 1.1.1.1 PING 1.1.1.1 (1.1.1.1) from 172.16.1.1 : 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=56 time=11.8 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=56 time=11.8 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=56 time=11.9 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=56 time=11.4 ms ^C --- 1.1.1.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3006ms rtt min/avg/max/mdev = 11.361/11.705/11.897/0.204 ms root@nodes1:~# root@nodes1:~# root@nodes1:~# ping -I vmbr0 1.1.1.1 PING 1.1.1.1 (1.1.1.1) from 172.16.1.1 vmbr0: 56(84) bytes of data. ^C --- 1.1.1.1 ping statistics --- 14 packets transmitted, 0 received, 100% packet loss, time 13121ms

Is anyone else having this issue?