4 ms·
I hope this makes a difference - traceroute was invaluable when I first started working in networked environments, but over time, it's become effectively useles
by commandlinefan 5y ago
I hope this makes a difference - traceroute was invaluable when I first started working in networked environments, but over time, it's become effectively useless because it just reports "* * *" after the first couple of hops. I always assumed that was because of network security policies, but maybe it was just timing out the whole time.
- sigjuice 5y agoYou might have better results if you use different traceroute options (e.g. --tcp on Linux, which uses TCP SYN for probes) or other traceroute-like programs (e.g. lft, paris-traceroute, mtr)
- jleahy 5y agoI think it’s often due to people using private IP addresses for intermediate nodes, to save on ipv4 addresses. mtr will keep going after hitting a blackhole in the middle.