Ping and traceroute commands are two commands that take place within the command prompt of an operating system. These commands are used to identify whether your computer can reach another server to see if there is a possibility to establish a connection. These commands also show at what point where there may be a fault between the two connections and shows a visual representation of the distance between the two connections.
Assessment of Ping and Traceroute Commands
After reviewing the ping and traceroutes we can identify from the results how close the servers are within range of our internet service provider's servers. When I used the ping command on the google website, it took about 35 milliseconds to transmit the 32 bytes of data that I sent from my computer to their servers. When I pinged the website, weblio.jp, my ping of 32 bytes of data transmission became an average of 321 milliseconds. It seems that the communication between my server and their servers became evidently longer, the transmission data seemed to be at a stable, upon transmission to these servers. I found another website called scielo.br, which when I pinged this server the transmission of data averaged at 739 milliseconds, which is significantly higher than the previous pinging commands, this transmission hit a max-cap of 1726 milliseconds, this seemed to show me some information that could potentially show that there is a problem with the transmission connection, because, during the transmission of the data, the minimum amount of time was 280 milliseconds, this makes me believe there were two possibilities of interruptions during my communication transmission. One issue could be that there was a disruption in my internet connection causing a longer delay sending out the data, or there could be a disruption going on at this website’s retrieval end or even their feedback response time. These could be potential issues, however, with just the pinging command there is no way of having any real answer as to why there was such a wide variety of transmission delays.
Ping Results:
Google.com – Packets Sent: 4, Received: 4, Lost: 0, Approximate round trip times – Min. 35ms, Max. 36ms, Average: 35ms
Weblio.jp – Packets Sent: 4, Received: 4, Lost: 0, Approximate round trip times – Min. 289ms, Max. 339ms, Average: 321ms
Scielo.br – Packets Sent: 4, Received: 4, Lost: 0, Approximate round trip times – Min. 280ms, Max. 1726, Average: 739ms
Traceroute Results:
Google.com – Over a maximum of 30 hops, range – 1ms – 34ms, hops 5,6, and 7 ping raised to 83-105 ms, then packet loss at hop number 8.
Weblio.jp – Over a maximum of 30 hops, range – 1ms – 218ms, hops 9, 11, 12, 13, and 16 all had about 100-220 ms, doubling its latency by hop number 16. Hops 10, 14, and 15 had packet losses.
Scielo.br – Over a maximum of 30 hops, range – 1ms –171 ms, hop number 10 had a packet loss, and hops 16, 17, and 18 ping raised to 170 ms.
During the traceroute command, Google’s website we can see the entire route from the starting location (my home) where data is transmitted from to the end result. During the transmission route, my ping raised around 100 ms from where it was averaging late 20s to mid-30s. Hop numbers 6 and 7 were where the transmission peaked and hop number 8 timed out. During the transmission with the website weblio.jp, the overall ping gradually increased from the start to the end of its route, by the time it hit hop number 9, ping doubled, thus making me believe that this is where the server started transmitting into a different geographic location, at hop number 10, the transmission hit a packet loss, and then the ping increased doubled again to 200ms, then more packet losses occurred at hops 14 and 15, and the transmission ended at hop 16, at 220 ms. With the scielo.br website, again ping gradually kept increasing from the start to finish, there was only one packet loss at hops number 10, and the ping gradually continued to rise after this, at hops 16, 17, and 18 ping reached 173 ms where the transmission’s route ended.
After reviewing the traceroutes round trip times, one could assume that the lower pings averaging 20-60ms would be within the country, and outside the country, we would see an increase by almost double or actually doubling in the roundtrip time. Realistically, after analyzing the difference between each website, we can identify that geographic location certainly impacts the roundtrip times, and it seems the further away the server is the ping will increase.
Identifying internet connection problems can be identified using the ping and traceroute commands, when pinging a server if there is a problem with the host server, we might see that there may not any responses from the server host. Another way that we can identify if there is a networking issue, using traceroute we can establish how long it takes for a packet of data to be sent to a host and how long it takes to return back, this is can be used to determine if there is an issue with the internet connection, as in most cases from the experimental attempts of our routing, anything within the countries origin of where we are pinging from is generally below 100 ms, if the connection exceeds 100ms than we could probably associate this with a problem, this would most likely only be applicable within the country as it seems that geographic location impacts the time for the data to be sent and received back, having an increased time of latency. The ping command may time out if the host that we are trying to ping has a network that is not established to receive the connection. Another option as to why we may see a timeout issue is if there might be a firewall that could potentially block the connection also.
No comments:
Post a Comment