Ping and Traceroute
Information is passed used the internet through multiple routers. As Vahid & Lysecky state, “The Internet is the most popular (but not the only) computer network today” (3.5). The internet is a vast network of computers using routers and ISPs to pass along information. When reviewing the ping times and packets that were sent, I noticed each set of commands sent 4 packets each. In my examples, no packets were lost in the ping process (see notes below).
When completing the traceroute process, I was able to get a much more detailed view of how the information was being processed from router to router. Also, there were failures along the way in the server that was traced to China. Due to the distance, I can see why information might time out, reach firewalls, or possible just hit disconnected servers or servers that are communicating too slow to really process the information. With the traceroute command it was easy to tell that my ping was failing in the middle of the transfer and was having to hop to different routers. Also, one cause could be the availability of routers to a specific area of the world.
Also, the further away the router was, the longer the time typically took for the packet to be received. When troubleshooting connectivity issues, the traceroute and ping could both be very useful. Ping would let you know if the other server was communicating at all. A very high ping time could also indicate that their server was having ISP connectivity issues possibly, or some other outside circumstance causing the transfer of data to be slow. The traceroute feature was great for pinpointing exactly where the information was failing. This might help troubleshoot whether the user was having the problem, the server being sent to was having a problem, or maybe something is down with the connectivity along the way.
This exercise was a great way to show just how many steps information takes to process when on the internet. I know we all seem to think that information is an A to B process when it comes to the internet, because we don’t see the information being transferred. This example shows just how many routes the information takes to get processed when a request is entered on your computer and then shown on your screen in a web browser.
Vahid, F., & Lysecky, S. (2019). Computing technology for all. zyBooks.
Ping and Traceroute Examples:
This screenshot is of a site in Australia. Four packets were sent with no losses and the ping time was much lower, ranging from 18ms to 23ms:
Comments
Post a Comment