When it came to running the ping and traceroute, I understood the concept on how to do it, but I was very confused on whether they would end themselves or was I supposed to end it. As they were running, they just kept going on and on. So I used control C to end it. I am not sure if I did anything wrong, but maybe one of you can give me more insight on this process. Nonetheless, below are screenshots of the ping and traceroute, with the results documented:
Reflecting back on this experience, it is easy to see exactly how packets travel through the network. From the ping, you can see how many packets were sent and how many were received. In my cases, I had only 1 packet that wasn't received. The other two websites, received every packet of information that was sent out. In the traceroute, you can see exactly where each packet of information went. The relationship for roundtrip time and geographical location is that the further the geographical locations (i.e. I live in the U.S. and I was searching a website from Australia) the longer the roundtrip times.
Two instances in which a ping request or traceroute command may time out or return with an error response is if the destination is unreachable or if there is bad/no internet connection. The ping and traceroute, are useful for troubleshooting internet connection problems because it allows you to see exactly where the error might have occurred.
Comments
Post a Comment