You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows Build: Microsoft Windows [Version 10.0.16299.192]
What am I doing:
I'm trying to execute a traceroute included in the GNU inetutils-traceroute package, nothing resolves. The same address resolves successfully using ping.
What should be happening instead:
Traceroute should function as it would when running in a native Ubuntu instance, or at least in a fashion comparable to running tracert in Windows Console
Windows Build: Microsoft Windows [Version 10.0.16299.192]
What am I doing:
I'm trying to execute a traceroute included in the GNU inetutils-traceroute package, nothing resolves. The same address resolves successfully using ping.
aydeisen@AEISEN-NBK3:
$ sudo apt-get install inetutils-traceroute$ ping www.google.comaydeisen@AEISEN-NBK3:
PING www.google.com (74.125.68.99) 56(84) bytes of data.
64 bytes from sc-in-f99.1e100.net (74.125.68.99): icmp_seq=1 ttl=39 time=213 ms
64 bytes from sc-in-f99.1e100.net (74.125.68.99): icmp_seq=2 ttl=39 time=212 ms
64 bytes from sc-in-f99.1e100.net (74.125.68.99): icmp_seq=3 ttl=39 time=212 ms
64 bytes from sc-in-f99.1e100.net (74.125.68.99): icmp_seq=4 ttl=39 time=212 ms
^C
--- www.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3001ms
rtt min/avg/max/mdev = 212.869/212.953/213.176/0.350 ms
aydeisen@AEISEN-NBK3:~$ traceroute www.google.com
traceroute to www.google.com (74.125.68.147), 64 hops max
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
^C
What should be happening instead:
Traceroute should function as it would when running in a native Ubuntu instance, or at least in a fashion comparable to running tracert in Windows Console
STrace of the failing command attached
traceroute.zip
The text was updated successfully, but these errors were encountered: