Packets of data travel from one destination to another through the network by transmission between routers. The ping command reveals whether a destination is available, and how quickly it can be accessed. The traceroute command reveals the path that packets of data traveled from one router to the next. Each time a packet is sent from one router to another, that is considered a hop. There are multiple paths that a packet can take to get to the same destination, depending on the routers that are available along the way.
In comparing the ping command for the three different websites that I used, all three pings successfully sent 4 packets of information. In addition, the amount of data sent in all three pings was 32 bytes. This allows for easy comparison of round trip time between the three websites. The average round trip time for the packets when pinging google.com (USA) was 12 ms. The average round trip time for packets sent to amazon.co.uk (United Kingdom) was 133 ms. The average round trip time for packets sent to amazon.ca (Canada) was 79 ms. This suggests that the farther the geographic distance, the longer the round trip time for packets to be sent.
On the other hand, the traceroute command told a different story. The only traceroute that was successfully completed was for google.com. Although I tried running the command multiple times for both amazon.co.uk, as well as amazon.ca, the commands always timed out before the information was received. This result confused me, since a command timeout can indicate packet loss. However, all of the pings were successful. I’m not sure how to reconcile the difference in the results between the pings and the traceroutes other than hypothesizing that if the command were to have enough time to run, the traceroute would be completed successfully, but since the distance the packets have to travel is so far (geographically), the command times out before the packets can travel that distance.
Pings and traceroutes can be used to diagnose connection problems in a few ways. A failed ping request may tell the user that the destination is not available. In addition, the ping request can tell the user the speed at which packets are traveling. A traceroute can tell the user the path through which packets are traveling. If a user is not able to access a destination, they may run a traceroute to pinpoint where in the path the data is being lost. Since the traceroute shows the routers associated with each hop, the specific router that is failing may be determined. In some cases, running a ping or traceroute may even reveal that the connection problem lies in the original device. Cases where a traceroute may timeout or a ping may fail include when the geographic distance traveled is too far, or if a destination server is down.
To view pings and trace routes, please click on the following link:
Pings and Traceroutes
Resources
Vahid, F., & Lysecky, S. (2017). Computing technology for all. Retrieved from zybooks.zyante.com/
Ping to google.com
Ping to amazon.co.uk
Ping to amazon.ca
Traceroute to google.com
Traceroute to amazon.co.uk
Traceroute to amazon.ca
In comparing the ping command for the three different websites that I used, all three pings successfully sent 4 packets of information. In addition, the amount of data sent in all three pings was 32 bytes. This allows for easy comparison of round trip time between the three websites. The average round trip time for the packets when pinging google.com (USA) was 12 ms. The average round trip time for packets sent to amazon.co.uk (United Kingdom) was 133 ms. The average round trip time for packets sent to amazon.ca (Canada) was 79 ms. This suggests that the farther the geographic distance, the longer the round trip time for packets to be sent.
On the other hand, the traceroute command told a different story. The only traceroute that was successfully completed was for google.com. Although I tried running the command multiple times for both amazon.co.uk, as well as amazon.ca, the commands always timed out before the information was received. This result confused me, since a command timeout can indicate packet loss. However, all of the pings were successful. I’m not sure how to reconcile the difference in the results between the pings and the traceroutes other than hypothesizing that if the command were to have enough time to run, the traceroute would be completed successfully, but since the distance the packets have to travel is so far (geographically), the command times out before the packets can travel that distance.
Pings and traceroutes can be used to diagnose connection problems in a few ways. A failed ping request may tell the user that the destination is not available. In addition, the ping request can tell the user the speed at which packets are traveling. A traceroute can tell the user the path through which packets are traveling. If a user is not able to access a destination, they may run a traceroute to pinpoint where in the path the data is being lost. Since the traceroute shows the routers associated with each hop, the specific router that is failing may be determined. In some cases, running a ping or traceroute may even reveal that the connection problem lies in the original device. Cases where a traceroute may timeout or a ping may fail include when the geographic distance traveled is too far, or if a destination server is down.
To view pings and trace routes, please click on the following link:
Pings and Traceroutes
Resources
Vahid, F., & Lysecky, S. (2017). Computing technology for all. Retrieved from zybooks.zyante.com/
Ping to google.com
No comments:
Post a Comment