A quick guide to the `traceroute` command, used to list all the nodes traversed to reach a host
When you try to reach a host on the Internet, you go through your home router, then you reach your ISP network, which in turn goes through its own upstream network router, and so on, until you finally reach the host.
Have you ever wanted to know what are the steps that your packets go through to do that?
traceroute command is made for this.
and it will (slowly) gather all the information while the packet travels.
In this example I tried reaching for my blog with
Not every router travelled returns us information. In this case,
* * *. Otherwise, we can see the hostname, the IP address, and some performance indicator.
For every router we can see 3 samples, which means traceroute tries by default 3 times to get you a good indication of the time needed to reach it. This is why it takes this long to execute
traceroute compared to simply doing a
ping to that host.
You can customize this number with the
traceroute -q 1 flaviocopes.com
traceroute command works on Linux, macOS, WSL, and anywhere you have a UNIX environment