Can anyone explain the logic of this traceroute command, what do you learn from this command?

Is it just me or does no one use -n option? It does cut down somewhat on the time not having to use DNS.
Also tcptraceroute is a bit quicker then the standard traceroute. I did two traceroutes to linux.org. The traceroute took 10 seconds, tcptraceroute took 5 seconds.
Note that as I repeated the process, they eventually took equal time to complete. I'm sure the routing table between the two was being reused.
 


Hmm the book author was trying to say that there was a huge gap in hop between second last and last hop, so destination was busy. I was trying to understand it. Thank you for all your replies. I didn't notice it was linux.org domain and I posted the question in linux.org. What a coincidence.
 

Members online


Top