...
In some installs of Debian/Ubuntu, the traceroute tool is not always installed by default, so we have to run the following command in order to install it:
| Code Block |
|---|
$ sudo apt-get install traceroute |
Once you have traceroute installed, you can run a traceroute command simply by typing
| Code Block |
|---|
$ traceroute [host] |
Host can be either an IP Address, like 127.0.0.1, or a domain name, like localhost or google.com. In our example, we'll just use google.com:
| Code Block |
|---|
$ traceroute google.com traceroute to google.com (216.58.193.174), 30 hops max, 60 byte packets |
...
1 |
...
192.168.254.1 (192.168.254.1) |
...
0.537 ms |
...
0.777 ms |
...
0.759 ms |
...
2 |
...
208.77.211.129 (208.77.211.129) |
...
12.604 ms |
...
12.592 ms |
...
12.572 ms |
...
3 |
...
pin-206-126-16-161.static.pocketinet.com (206.126.16.161) |
...
12.553 ms |
...
12.533 ms |
...
12.513 ms |
...
4 |
...
core01-sea.net.pocketinet.com (206.126.21.9) |
...
13.331 ms |
...
15.410 ms |
...
16.634 ms |
...
5 |
...
six.sea01.google.com (206.81.80.17) |
...
16.644 ms |
...
16.929 ms |
...
20.069 ms |
...
6 |
...
66.249.94.212 (66.249.94.212) |
...
20.623 ms |
...
13.192 ms |
...
15.240 ms |
...
7 |
...
209.85.244.59 (209.85.244.59) |
...
15.472 ms |
...
15.474 ms |
...
16.509 ms |
...
8 |
...
sea09s15-in-f14.1e100.net (216.58.193.174) |
...
18.918 ms |
...
18.910 ms |
...
18.902 ms |
The above results are my results from the Vivio Internal Network, your results will be different, as you're probably on a different network. We'll talk more about these differences and what they mean further down in the article.
...
In some installs of RHEL/CentOS, the traceroute tool is not always installed by default, so we have to run the following command in order to install it:
| Code Block |
|---|
# yum install traceroute |
Once you have traceroute installed, you can run a traceroute command simply by typing
| Code Block |
|---|
# traceroute [host] |
Host can be either an IP Address, like 127.0.0.1, or a domain name, like localhost or google.com. In our example, we'll just use google.com:
| Code Block |
|---|
# traceroute google.com traceroute to google.com (216.58.193.174), 30 hops max, 60 byte packets |
...
1 |
...
192.168.254.1 (192.168.254.1) |
...
0.537 ms |
...
0.777 ms |
...
0.759 ms |
...
2 |
...
208.77.211.129 (208.77.211.129) |
...
12.604 ms |
...
12.592 ms |
...
12.572 ms |
...
3 |
...
pin-206-126-16-161.static.pocketinet.com (206.126.16.161) |
...
12.553 ms |
...
12.533 ms |
...
12.513 ms |
...
4 |
...
core01-sea.net.pocketinet.com (206.126.21.9) |
...
13.331 ms |
...
15.410 ms |
...
16.634 ms |
...
5 |
...
six.sea01.google.com (206.81.80.17) |
...
16.644 ms |
...
16.929 ms |
...
20.069 ms |
...
6 |
...
66.249.94.212 (66.249.94.212) |
...
20.623 ms |
...
13.192 ms |
...
15.240 ms |
...
7 |
...
209.85.244.59 (209.85.244.59) |
...
15.472 ms |
...
15.474 ms |
...
16.509 ms |
...
8 |
...
sea09s15-in-f14.1e100.net (216.58.193.174) |
...
18.918 ms |
...
18.910 ms |
...
18.902 ms |
The above results are my results from the Vivio Internal Network, your results will be different, as you're probably on a different network. We'll talk more about these differences and what they mean further down in the article.
...
So, looking at our traceroute, let's take a look at the first "hop":
| Code Block |
|---|
...
1 192.168.254.1 (192.168.254.1) |
...
0.537 |
...
ms 0.777 |
...
ms 0.759 ms |
...
In the above, the following are what each section refers to:
...