On 8/2/19 9:14 AM, Alexei Starovoitov wrote: > On Thu, Aug 1, 2019 at 9:04 PM David Ahern <dsah...@gmail.com> wrote: >> ... >> >>> >>> with -v I see: >>> COMMAND: ip netns exec ns-A ping -c1 -w1 -I 172.16.2.1 172.16.1.2 >>> ping: unknown iface 172.16.2.1 >>> TEST: ping out, address bind - ns-B IP >>> [FAIL] >> >> With ping from iputils-ping -I can be an address or a device. > > the ping, I have installed, supports -I. > The issue is somewhere else. Ideas? >
make sure ping supports the overloading of -I (both dev and address). check your kernel version. No results guaranteed on kernel prior to 5.3 This is Fedora 29 with 5.1 kernel TEST: ping out - ns-B IP [ OK ] TEST: ping out, device bind - ns-B IP [ OK ] TEST: ping out, address bind - ns-B IP [ OK ] TEST: ping out - ns-B loopback IP [ OK ] TEST: ping out, device bind - ns-B loopback IP [ OK ] TEST: ping out, address bind - ns-B loopback IP [ OK ] TEST: ping in - ns-A IP [ OK ] TEST: ping in - ns-A loopback IP [ OK ] TEST: ping local - ns-A IP [ OK ] TEST: ping local - ns-A loopback IP [ OK ] TEST: ping local - loopback [ OK ] TEST: ping local, device bind - ns-A IP [ OK ] TEST: ping local, device bind - ns-A loopback IP [ OK ] TEST: ping local, device bind - loopback [ OK ] TEST: ping out, blocked by rule - ns-B loopback IP [ OK ] TEST: ping in, blocked by rule - ns-A loopback IP [ OK ] TEST: ping out, blocked by route - ns-B loopback IP [ OK ] TEST: ping in, blocked by route - ns-A loopback IP [ OK ] TEST: ping out, unreachable default route - ns-B loopback IP [ OK ] Tests are known to work on Debian stretch and buster. Appears to work on Fedora 29.
