Packets travel through a network by “hopping” from your computer, to your internet service provider, and then on through various other hops until the destination is reached. When looking at the data from the ping command I noticed the Google ping had the quickest response time average at 49ms. The Baidu website had and average response time of 149ms while the Spiegel website had and average response time of 295ms. These numbers are consistent with how I thought they would turn out because the Google website is closer to my home location than the other websites. I was surprised to see that between all three websites there was no packet loss. I would have thought that with the connections to the other websites being so far apart that I would have lost at least a small amount of packet data.
After running the “trace route” command the data showed that each website had taken the same number of hops to complete a successful trace. Each website also had a request time out at some point. I did notice that the number of hops and the step at which a request timed out were inconsistent. On a Google trace I typically had a timeout on hop six and ten, but I ran the command a few times and would sometimes find those hops and miss others. Utilizing the traceroute command can be very beneficial when troubleshooting issues with internet connections. If you are unable to connect to a certain website you can run the command and tell where along the way you are losing connection. This command can also tell you whether there is an issue with your internet service provider or not. One reason a ping request might time out is if the host website is down. Another reason may be that the computer trying to send the ping request is not connected to the internet. It should be noted that the traceroute command does not like to be ran through a VPN. I have tried on several attempts to gain a successful trace but failed each time until I shut the VPN off.
Comments
Post a Comment