Using the ping and trace route commands the packets are sent from the requesting network source to the host network source through all the connected network equipment and lines including the local area network out to the wide area network and all the communication lines connecting all the routers in between the host website and the requester. I used the Nintendo of Japan website and a website in Russia that appeared to be similar to Yahoo or MSN for the ping and trace route activity, I found it interesting that even though the distance geographically was not completely different that the results were, the Nintendo of Japan website took 32ms and was over the span of 9 different hops where the Russian website was 148ms and over the span of 14 hops with 2 of them timing out. I do wonder if the Nintendo of Japan was perhaps faster and less hops because it may have been connected via satellite where the Russian website might have been connected through all mainland lines, really make me wonder.
Are they useful?
Ping can be helpful in not only quickly being able to see if whatever host you might be trying to connect to is even available but the amount of time it can take and possibly any sort of lag you may encounter depending on what you are trying to accomplish. It does however only really provide that limited information and diving deeper and using the trace route command you are able to see for example where the connection is having issues such as timing out and what the IP address is where it can connect to and how far the connection is able to get and or how many hops before encountering any of those issues. This could be useful as you might be able to get in touch with some support team and give them the information so they can troubleshoot from their end. A ping and or trace route might time out or return with an error if the host name / DNS is not resolving or if any of the routers or other networking equipment is having issues or is down.
My Ping / Trace route Results
**********************************
**********************************
https://www.nintendo.co.jp/
ping www.nintendo.co.jp
tracert www.nintendo.co.jp
C:\Users\Adam>ping www.nintendo.co.jp
Pinging e5192.g.akamaiedge.net [184.25.181.244] with 32 bytes of data:
Reply from 184.25.181.244: bytes=32 time=29ms TTL=56
Reply from 184.25.181.244: bytes=32 time=29ms TTL=56
Reply from 184.25.181.244: bytes=32 time=28ms TTL=56
Reply from 184.25.181.244: bytes=32 time=28ms TTL=56
Ping statistics for 184.25.181.244:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 29ms, Average = 28ms
C:\Users\Adam>tracert www.nintendo.co.jp
Tracing route to e5192.g.akamaiedge.net [184.25.181.244]
over a maximum of 30 hops:
1 2 ms 2 ms 4 ms 192.168.1.1
2 11 ms 18 ms 13 ms xxx.xxx.xxx.xxx
3 26 ms 31 ms 32 ms agg63.mtvroh2702h.midwest.rr.com [65.25.145.85]
4 19 ms 23 ms 15 ms agg43.clmcohib01r.midwest.rr.com [24.33.161.128]
5 21 ms 21 ms 23 ms be27.clevohek01r.midwest.rr.com [65.29.1.38]
6 31 ms 31 ms 27 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
7 34 ms 32 ms 30 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
8 29 ms 29 ms 31 ms 0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
9 30 ms 30 ms 32 ms a184-25-181-244.deploy.static.akamaitechnologies.com [184.25.181.244]
Trace complete.
**********************************
**********************************
https://www.yandex.ru/
ping www.yandex.ru
Pinging www.yandex.ru [77.88.55.88] with 32 bytes of data:
Reply from 77.88.55.88: bytes=32 time=145ms TTL=52
Reply from 77.88.55.88: bytes=32 time=139ms TTL=52
Reply from 77.88.55.88: bytes=32 time=142ms TTL=52
Reply from 77.88.55.88: bytes=32 time=143ms TTL=52
Ping statistics for 77.88.55.88:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 139ms, Maximum = 145ms, Average = 142ms
tracert www.yandex.ru
Tracing route to www.yandex.ru [77.88.55.88]
over a maximum of 30 hops:
1 2 ms 1 ms 3 ms 192.168.1.1
2 13 ms 11 ms 13 ms xxx.xxx.xxx.xxx
3 28 ms 33 ms 31 ms agg63.mtvroh2702h.midwest.rr.com [65.25.145.85]
4 19 ms 15 ms 15 ms agg43.clmcohib01r.midwest.rr.com [24.33.161.128]
5 23 ms 24 ms 21 ms be27.clevohek01r.midwest.rr.com [65.29.1.38]
6 30 ms 29 ms 32 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
7 26 ms 27 ms 28 ms 0.ae0.pr0.dca20.tbone.rr.com [107.14.19.65]
8 * 570 ms 601 ms ge-7-1-6.pr0.chi10.tbone.rr.com [66.109.9.74]
9 * * * Request timed out.
10 29 ms 33 ms 30 ms YANDEX-EURO.bear1.Washington111.Level3.net [4.14.97.242]
11 144 ms 140 ms 142 ms ams1-b1-xe-1-3-0.yndx.net [213.180.213.193]
12 140 ms 138 ms 142 ms jansson-et-4-1-0.yndx.net [213.180.213.95]
13 * * * Request timed out.
14 144 ms 144 ms 148 ms yandex.ru [77.88.55.88]
Trace complete.
**********************************
**********************************
ping www.google.com
Pinging www.google.com [172.217.4.68] with 32 bytes of data:
Reply from 172.217.4.68: bytes=32 time=33ms TTL=53
Reply from 172.217.4.68: bytes=32 time=35ms TTL=53
Reply from 172.217.4.68: bytes=32 time=34ms TTL=53
Reply from 172.217.4.68: bytes=32 time=35ms TTL=53
Ping statistics for 172.217.4.68:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 35ms, Average = 34ms
tracert www.google.com
Tracing route to www.google.com [172.217.6.4]
over a maximum of 30 hops:
1 3 ms 2 ms 3 ms 192.168.1.1
2 13 ms 12 ms 13 ms xxx.xxx.xxx.xxx
3 30 ms 29 ms 31 ms agg63.mtvroh2702h.midwest.rr.com [65.25.145.85]
4 20 ms 23 ms 21 ms agg43.clmcohib01r.midwest.rr.com [24.33.161.128]
5 27 ms 32 ms 29 ms be27.clevohek01r.midwest.rr.com [65.29.1.38]
6 30 ms 31 ms 39 ms bu-ether17.vinnva0510w-bcr00.tbone.rr.com [66.109.6.70]
7 28 ms 32 ms 29 ms bu-ether11.asbnva1611w-bcr00.tbone.rr.com [66.109.6.30]
8 27 ms 28 ms 33 ms 0.ae4.pr1.dca10.tbone.rr.com [66.109.1.113]
9 28 ms 29 ms 32 ms ix-ae-17-0.tcore2.aeq-ashburn.as6453.net [216.6.87.149]
10 29 ms 29 ms 28 ms 72.14.198.28
11 29 ms 28 ms 30 ms 108.170.246.49
12 31 ms 32 ms 30 ms 216.239.50.97
13 33 ms 33 ms 35 ms 209.85.253.248
14 35 ms 35 ms 35 ms 216.239.40.188
15 37 ms 37 ms 40 ms 108.170.243.174
16 34 ms 37 ms 36 ms 108.170.238.137
17 34 ms 35 ms 33 ms ord38s01-in-f4.1e100.net [172.217.6.4]
Trace complete.
**********************************
**********************************
No comments:
Post a Comment