Traveling through a Network Post#4

  

For the ping command using Google, the router passes through only one which is the 172.217.8.142 address. It first looks up and displays the IP address that relates with its domain name. The lines that follow are four replies from the destination IP address. The round-trip time or each echo response (in milliseconds) are 16ms, 17ms and 22ms. No error messages on the output. The overall statistics are zero loss packets and the success rates and the range the range or round-trip times is 18 milliseconds.

For the ping command using Telekom.de (Germany), the router passes through only one which is the 80.158.67.40 address. It first looks up and displays the IP address that relates to its domain name. The lines that follow are four replies with a “Request time out”. The round-trip time or each echo response is zero. The overall statistics is 100 percent loss packets with no success rates and no round-trip times.

For the ping command using Cyberops.in (India), the router passes through only one which is the 1104.238.80.162 address. It first looks up and displays the IP address that relates to its corresponding domain name. The lines that follow are four replies from the destination IP address. The round-trip time or each echo response (in milliseconds) are 89ms, 86ms and 85ms. No error messages on the output. The overall statistics are zero loss packets and the range the range or round-trip times is 86 milliseconds.

Traceroute

For Google, the traceroute command shows each line representing a hop to a router that its further away, in this case it hits my home router, followed by my IPS (Comcast) and routes total of 12 hops. The traceroute was successful because the final line represents the destination IP address that the domain name resolve to its IP. The round-trip time that it takes for a packet to travel to each router is between 13 milliseconds and 20 milliseconds. Traceroute send out three packets to each hop, and from the results its shows a consistent connection.

For CyberOps.in (India), the traceroute command shows each line representing a hop to a router that its further away, in this case it hits my home router, followed by my IPS (Comcast) and routes total of 16 hops. The traceroute was successful because the final line represents the destination IP address that the domain name resolve to its IP which is 104.238.80.162. The round-trip time that it takes for a packet to travel to each router is between 15 milliseconds and 426 milliseconds. Traceroute send out three packets to each hop, and from the results it shows a consistent connection yet a longer route since it is in India.

For Telekom.de (Germany) the traceroute command shows each line representing a hop to a router that its further away, and routes total of 16 hops ending Germany’s location. The traceroute was not successful because the final line did not represent the destination IP address that the domain name resolve to its IP , it ends with a different IP of 87.19.235.70, yet it hits Deutschland ISP of DTAG.DE. The round-trip time that it takes for a packet to travel to each router is between 13 milliseconds and 145 milliseconds. The icon * tells me the command timed out before receiving a response, which is different from India. This indicates * packet loss and unsuccessful hop process. 

One possible reason why a ping can be useful to troubleshoot is to find out if the IP is live or the device in question is on Online, or if the IP has been changed to a new one. For Traceroute, you can see if the route ends prior to where you are trying to reach, this could be a Switch or Router is dead.