Packets Traveling Through a Network

 For this post, I have decided to perform a few Ping and trace commands and analyze their results. As you can see in this screenshot, I pinged  Google.com. and the result shows 4 packets were sent and received and 0 was loss. The range of response speed was a minimum of 6ms, maximum of 8ms and an average of 7ms

I did the same for Yahoo.fr and saw a big difference where 4 packets, four were received and 0 were loss. The range of response speed was a minimum of 89ms, maximum of 91ms and an average of 90ms.

I also traceroute Google.com, and youtube.com and the result shows that it takes 2 hops. The first hop is within my local network. Here, I have the hop number (1), the domain name/IP address (in this case a home router), then RTT1, RTT2, and RTT3 (Round Trip Time - the time it takes for a packet to get to the hop and back to the computer, in milliseconds). The only difference is that the round trip for google.com takes a little bit longer than YouTube

Reflecting on my experience using the ping and traceroute commands, Packets travel through the networks when someone send a request from a device and receive a response from the destination device. Ping and tracert helps the user to identify any issues that may persist in relevance to connectivity between two IP addresses. While ping is an easier concept that emphasizes on whether the echo request is successfully responded to, the Traceroute command ensure to analyze the precise location where the packet is lost thereby leading to disintegration of connectivity. Since both commands Ping and tracert helps the user to identify any issues that may persist in relevance to connectivity between two IP addresses. It signals that both commands operate on the networks layer which has two main functions. One is breaking up segments into network packets, and reassembling the packets on the receiving end. The other is routing packets by discovering the best path across a physical network.  Based on research I conducted on the OSI model, the network layer uses network addresses (typically Internet Protocol addresses) to route packets to a destination node

When I compare the ping and traceroute results, it first looks up and displays the IP address that corresponds with the domain name.  The lines that follow show how many times the server at the destination IP address replied. If the communication was successful, you will see the round-trip time of each echo response in milliseconds. As opposed to traceroute, that sends out three packets to each hop (times between each router) Where the first line of the results shows your home router, and the next line represents your internet service provider (ISP). It also shows two vertical line where each represents a hop to a router. When pinging a device, sometimes the ping might time out for the following reasons:

·        You have Incorrect Network Adapter or Firewall Settings on your

·        The remote host is down

·        There’s no route back to your computer

·        The firewall installed on the destination host may be blocking your ICMP request

In Conclusion, the relationship between the roundtrip time and geographical location varies based on the physical location. Response times in millisecond from the gateway is shorter than the one from the destination server.

<script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-4489055007945767"

     crossorigin="anonymous"></script>