I chose to ping and traceroute Google (www.google.com (Links to an external site.)), The Japan Foundation (www.jpf.go.jp (Links to an external site.)), and Australia Government (www.australia.gov.au (Links to an external site.) ) which are all three in different time zones. All three of my ping commands sent and received 4 packets with a zero percent loss. The average times varied with Google being the fastest at 24 milliseconds round trip and The Japan Foundation the slowest at an average of 47 milliseconds round trip. When tracerouting the Australia Government site, however, there must have been server issues because the majority of my hops timed out. The Japan Foundation traceroute was once again the slowest to travel but had much more reliable hops than Australia did. It appears from reviewing the data received from both the ping and traceroutes, that the further away a site is located from you the longer it will take to travel, even in the digital world. Australia had the most hops on my traceroute and it also resulted in having the most failed hops.
I believe that using these featured commands could greatly help in figuring out or troubleshooting connection problems. You could also determine if the connection issue has more to do with your end or the receiving end. In most cases while conducting my research with ping and tracerouting, I found that the problems start between the seventh and tenth hop. I believe that to be because they are traveling through many more routers at that point and with the distance required to travel there is more margin for error. Another reason that a transmission may fail, is that the receiving computer could be offline and therefore the signal is unable to reach the destination, resulting in a timed out request. I have never actually used either of these commands until working on this assignment, but they could have been extremely helpful to me in the past when troubleshooting had I known they existed.
Examples of Ping and TraceRoute Images:
No comments:
Post a Comment