 |
 |
traceroute to www.google.com (173.194.65.99), 64 hops max 1 traceroute: sendto: Network is unreachable is traceroute the same for ipv6? since ping is only working as ping6, which stands for my case, having a static ipv6 only address 2014-10-19 17:02 GMT+03:00 Panos Sid <[log in to unmask]>: > ping6 www.google.com > PING www.google.com(ee-in-x63.1e100.net) 56 data bytes > 64 bytes from ee-in-x63.1e100.net: icmp_seq=1 ttl=50 time=54.6 ms > 64 bytes from ee-in-x63.1e100.net: icmp_seq=2 ttl=50 time=54.8 ms > 64 bytes from ee-in-x63.1e100.net: icmp_seq=3 ttl=50 time=54.7 ms > 64 bytes from ee-in-x63.1e100.net: icmp_seq=4 ttl=50 time=54.8 ms > 64 bytes from ee-in-x63.1e100.net: icmp_seq=5 ttl=50 time=54.8 ms > ^C > --- www.google.com ping statistics --- > 5 packets transmitted, 5 received, 0% packet loss, time 4006ms > rtt min/avg/max/mdev = 54.696/54.799/54.883/0.161 ms > > > the traceroute result is untruncated > > 2014-10-19 16:54 GMT+03:00 Francis Kayiwa <[log in to unmask]>: > >> On 10/19/2014 09:38 AM, Panos Sid wrote: >> >>> traceroute: unknown host >>> >>> >>> sudo traceroute www.google.com >>> traceroute to www.google.com (173.194.65.106), 64 hops max >>> 1 traceroute: sendto: Network is unreachable >>> >> >> Is this ^^^ a truncated result? If not, it is useful if you provided >> unredacted results. (feel free to mask the IPs if concerened) It is odd >> that the first hop would fail which leads me to look in the direction of >> your route (still waiting for those results incidentally ;-) ) >> >> >> Can you ping the IP address above? traceroute by default uses ICMP (UDP) >> >> The traceroute -T switch does the same thing as ping. >> >> >> ./fxk >> >> -- >> You single-handedly fought your way into this hopeless mess. >> > >