On 4/16/19 11:06 AM, Bengt Gördén wrote:
On 2019-04-15 21:12, Carlos E. R. wrote:
linux-0o2k:~ # ping6 ff02::1 connect: Invalid argument
Just a small comment. You seem too have an old iputils installed.
It is Leap 15.1 Beta... the most recent possible.
It was a bug in 2017. A workaround is to specify the interface in the command when trying to ping. Most tools recognize <ipv6>%<dev> or you could also use -i in this case.
Like so: ping6 ff02::1%eth0
Ah! I always forget that syntax, and the man page has no examples, I was at a loss to find out the correct combination. Thanks. The result is curious: linux-0o2k:~ # ping6 -c 1 ff02::1%eth0 PING ff02::1%eth0(ff02::1%eth0) 56 data bytes 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=1 ttl=64 time=0.067 ms --- ff02::1%eth0 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.067/0.067/0.067/0.000 ms linux-0o2k:~ # but: linux-0o2k:~ # ping6 -c 4 ff02::1%eth0 PING ff02::1%eth0(ff02::1%eth0) 56 data bytes 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=1 ttl=64 time=0.062 ms 64 bytes from fe80::21e:bff:fe08:4ccb%eth0: icmp_seq=1 ttl=1 time=0.375 ms (DUP!) 64 bytes from fe80::4ecc:6aff:fe61:50a1%eth0: icmp_seq=1 ttl=64 time=0.417 ms (DUP!) 64 bytes from fe80::4609:b8ff:fe42:c944%eth0: icmp_seq=1 ttl=64 time=0.425 ms (DUP!) 64 bytes from fe80::fa8e:85ff:fe64:78f2%eth0: icmp_seq=1 ttl=64 time=1.68 ms (DUP!) 64 bytes from fe80::3a80:dfff:fe5c:75b5%eth0: icmp_seq=1 ttl=64 time=77.7 ms (DUP!) 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=2 ttl=64 time=0.066 ms 64 bytes from fe80::21e:bff:fe08:4ccb%eth0: icmp_seq=2 ttl=1 time=0.363 ms (DUP!) 64 bytes from fe80::4ecc:6aff:fe61:50a1%eth0: icmp_seq=2 ttl=64 time=0.395 ms (DUP!) 64 bytes from fe80::4609:b8ff:fe42:c944%eth0: icmp_seq=2 ttl=64 time=0.404 ms (DUP!) 64 bytes from fe80::fa8e:85ff:fe64:78f2%eth0: icmp_seq=2 ttl=64 time=0.649 ms (DUP!) 64 bytes from fe80::3a80:dfff:fe5c:75b5%eth0: icmp_seq=2 ttl=64 time=304 ms (DUP!) 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=3 ttl=64 time=0.059 ms 64 bytes from fe80::21e:bff:fe08:4ccb%eth0: icmp_seq=3 ttl=1 time=0.373 ms (DUP!) 64 bytes from fe80::4ecc:6aff:fe61:50a1%eth0: icmp_seq=3 ttl=64 time=0.392 ms (DUP!) 64 bytes from fe80::4609:b8ff:fe42:c944%eth0: icmp_seq=3 ttl=64 time=0.400 ms (DUP!) 64 bytes from fe80::fa8e:85ff:fe64:78f2%eth0: icmp_seq=3 ttl=64 time=0.660 ms (DUP!) 64 bytes from fe80::3a80:dfff:fe5c:75b5%eth0: icmp_seq=3 ttl=64 time=187 ms (DUP!) 64 bytes from fe80::221:85ff:fe16:2d0b%eth0: icmp_seq=4 ttl=64 time=0.052 ms --- ff02::1%eth0 ping statistics --- 4 packets transmitted, 4 received, +15 duplicates, 0% packet loss, time 3002ms rtt min/avg/max/mdev = 0.052/30.355/304.330/78.294 ms linux-0o2k:~ # With 1 ping, there is no time for the reply from the rest of the network, it exits at the first reply. The command doesn't know that it is a multicast.qq
And for what it's worth. Now days ping6 and ping are the same. $ ls -l `which ping6` lrwxrwxrwx 1 root root 4 2 aug 2018 /usr/bin/ping6 -> ping
That I noticed yesterday. Good thing, having two versions was absurd. -- Cheers / Saludos, Carlos E. R. (from openSUSE, Leap 15.1 x86_64 (ssd-test)) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org