GNOME Bugzilla – Bug 578841
Ping and traceroute fails on certain address
Last modified: 2011-07-13 08:11:46 UTC
this report has been filed here: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-nettool/+bug/359315 "If i ping my standard reference basun.sunet.se it fails. Another address www.expressen.se works fine. Using ping from command line works without a problem. hjelm@aspire-one:~$ ping basun.sunet.se PING basun.umdc.umu.se (130.239.8.41) 56(84) bytes of data. 64 bytes from basun.umdc.umu.se (130.239.8.41): icmp_seq=1 ttl=245 time=35.6 ms 64 bytes from basun.umdc.umu.se (130.239.8.41): icmp_seq=2 ttl=245 time=35.6 ms 64 bytes from basun.umdc.umu.se (130.239.8.41): icmp_seq=3 ttl=245 time=34.8 ms Traceroute is the same. All other tabs works fine."
After some debugging i think i have narrowed it down to adresses that have a ipv6 adresses. This was in the console after i started it from a command line. command: /bin/ping6 ping6 -c 5 -n basun.sunet.se My computer apparently have a ipv6 address but it is not used. Not sure where the error is here but an error message would be nice. I will try to disable any ipv6 address and see what happens.
Looking at the sourcecode it does not take into account if the device is IPV6 enabled or not. Not sure how it should be done but a check prior to selecting which kind of ping is used.
This should be fixed with the patch applied in #650611, which gives priority to IPv4 over IPv6. *** This bug has been marked as a duplicate of bug 650611 ***