Pings are used to test the reachability of a device on the network, this can be used to determine the issues going on with a simple internet connection. It's basically like an echo; the command sends out a request to the destination URL and waits for a response. Whether you get a response or not would tell you what other steps to take. Not getting a response can move you towards using a traceroute which basically tells you every step the request goes through in order to get the response. In doing this step you can see exactly where the request is failing, whether it's before or after it reaches its destination. Seeing high latency in the middle or end of the test can be normal but if you see high latency at the beginning of the test this could mean there is a problem with the local network.
The 3 pings I did were for Google.com, amazon.jp, and walmart.com. All 3 pings went through successfully, it is the traceroutes I had some interesting responses. I had several timeouts and * in the middle of both Amazon.jp and walmart.com. Responses with an * can mean there is a problem with the network, and a smooth and consistent time with a higher latency at the end can be something as simple as congestion as you near the end of the path. When it comes to internet and connectivity issues both ping and traceroute can be very useful especially if used together. Ping being used to see if there is a connection between the network and outside sites and traceroute being used to see the exact path of the ping to see exactly where things go wrong if there is an issue with the ping in the first place.
Comments
Post a Comment