Traveling Through a Network

When a package travels through a network, it follows a specific path from the source to the destination. This is determined by the network routing protocols and the configuration of routers along the way; the package hops from one router to another until it reaches its destination. Pinging is a command used to test the connectives and round-trip time (RTT) between two devices and provides information about the latency and stability of the connection.  Tracing, on the other hand, is a command to trace the route packets take from the source to the destination. It shows the IP addresses of the routers through which the packets pass. Tracing helps identify any network issues or bottlenecks along the path. Analyzing this path revealed by the tracing command, we can observe how the packets traverse different routers and networks. It helps us understand the geographical route taken by the packets and identify any potential delays or issues along the way. It is a bit confusing to analyze ping and traceroute results at first. To compare the different destinations, start by looking at the IP addresses of the routers in the traceroute results. I noticed differences in the sequence or number of hops. Additionally, I paid attention to the round-trip time (RTT) values from the ping results. Higher RTT values can indicate longer delays or network congestion. By examining these factors, I started identifying variations in the paths and potential differences in network performance.

So, ping and traceroute are super handy for figuring out what's up with your internet connection. Ping checks if you can reach another computer over the network and measures how long it takes for a message to get there and back. Traceroute shows your message's path to reach another computer, helping identify where problems are happening. Two reasons why ping or traceroute might fail? One could be network congestion- too much traffic can cause timeouts. Another reason might be incorrect routing or a downed server along the path your data in its tracks and gives an error. 

Pinging Google

Tracing Route to Google