Ping & Traceroute
Reflecting on my experience using the ping and traceroute commands, I found that requests sent from a client to a server are tracked and measured during their journey; and those requests are labeled as transmissions.
First, we’ll discuss the ping command. The ping command is a network tool used to test the reachability of a host on an Internet Protocol (IP) network. It measures the Round-Trip Time (RTT) for requests sent from the originating host to a destination computer and back.
Next, we have traceroute. Traceroute is a network diagnostic tool used to trace the path that requests/data takes from one computer to another. The traceroute command identifies routers that requests/data travel to in route to its final destination. Both the ping, and traceroute commands measure requests/data in the form of, packets, and Round-Trip Time (RTT). See pics below.
Comparison of Requests
When sending ping requests or traceroute commands, the end results can vary depending on a wide range of reasons, such as, [i] the geographical location of the destination server, [ii] the network infrastructure of the website, and/or [iii] hardware issues (e.g., server offline).
Troubleshooting
The ping and traceroute commands can be used to troubleshoot internet connection problems by identifying the statues and stability of devices, and to determine failures within a network. Pings commands can determine if a device is reachable/online, if requests don’t “time-out”. Additionally, ping commands can detect the stability of communication between a device and other devices on a network by measuring if “time-outs” and Round-Trip Time (RTT).
Failed Ping/Traceroute
A couple of reasons why a ping request or a traceroute command might time out or return an error response are: [i] a server is offline or over-utilized, or [ii] a website domain is down (offline), or a mistake in the domain name when initiating the request (e.g., misspelled domain name).
No comments:
Post a Comment