Traveling Through a Network
Ping Activity:
When I pinged Google.com I received one “request timed out” notification and three replies:
Request timed out
2607:f8b0:4006:804::200e time=19ms
2607:f8b0:4006:804::200e time=19ms
2607:f8b0:4006:804::200e time=14ms
My ping sent four packets of which three were received and one was lost with an average round trip time of 17ms. One of my packets failed to reach Google.com whereas the other three did.
For my next two pings, I selected news.com.au and japantimes.co.jp the results are as follows:
When I pinged news.com.au, I received replies from all four packets
23.205.210.206: bytes=32 time=75ms TTL=59
23.205.210.206: bytes=32 time=18ms TTL=59
23.205.210.206: bytes=32 time=15ms TTL=59
23.205.210.206: bytes=32 time=14ms TTL=59
Average roundtrip of 30ms (0% Loss)
When I pinged japantimes.co.jp, all 4 of my packets failed “request times out” (100% Loss). My best guess is that the packets did not reach their destination within the TTL of 59 seconds.
Request timed out
Request timed out
Request timed out
Request timed out
Traceroute activity
When I ran a traceroute on google.com, the results showed that my packets passed through 11 routers; at router number 5, there appears to be a transmission failure through hop #6 then again at hop # 9.
When I ran a traceroute on news.com.au, my packets passed through a total of seven routers successfully with all three packets of information ranging from 5ms to 29ms.
When I ran a traceroute on japantimes.co.jp, I noticed a considerable difference in the number of routers my packets passed through as well as the amount of time it took. There were several requests timed out messages but the traceroute continued possibly being rerouted to different routers in an attempt to reach the site. Trace completed at 30 hops with several packets not reaching their destination. Times ranged from 5ms to 256ms.
After running three traceroutes, I concluded that geographical location impacted the number of router hops as well as the length of time it took for the packets to reach or attempt to reach their destination. The Japanese website went through all 30 hops and resulted in more packet loss compared to Google.com and the Australian site news.com.au.
Ping and traceroute can be used to troubleshoot and rule out suspected connectivity issues. Using both tools, a user can determine if the failure to reach a site is due to their connection or if the site is experiencing trouble.
Two possible reasons for traceroute and ping time out or return error responses could be a short TTL or low maximum hop count.
One of my classmates "JG" experienced similar results when using the traceroute utility to send packets to a site in a land far, far, away...
JG wrote: "Eddie, great job on explaining ping and traceroute. I had the same experience as you did when using traceroute on a Russian website, it timed out as well. It's quite amazing how all the technology works together behind the scenes to help us surf the web and find the information we need."
No comments:
Post a Comment