Traveling Through a Network

Part 1: Ping Activity

Google.com

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Minimum = 14ms, Maximum = 17ms, Average = 15ms

 

Ca.yahoo.com

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Minimum = 19ms, Maximum = 20ms, Average = 19ms

Yahoo.jp

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Minimum = 120ms, Maximum = 186ms, Average = 152ms

 

Part 2: Traceroute Activity

Google.com

Hops: 15
Time Range: 1ms to 47ms
No failures, stable route

Ca.yahoo.com

Hops: 13
Time Range: 1ms to 28ms
3 hops timed out but route completed successfully

Yahoo.jp

Hops: 12
Time Range: 3ms to 237ms
Several timeouts occurred; route completed

Part 3: Traveling Through a Network Reflection Essay

Using ping and traceroute tools gave me an inside look at how data travels through a network. With ping, I saw the time it took for small data packets to reach a destination and return. The traceroute tool allowed me to follow the path those packets took across routers and networks, showing each hop in the journey. Google.com had the fastest response, likely because it is hosted close to my geographic location. Yahoo Japan had the slowest response and highest round-trip time, which reflects the longer distance and international routing. This proves a clear correlation between geographic distance and round-trip delays. Ping and traceroute are incredibly useful for troubleshooting network issues. Ping checks if a device is reachable and measures the speed, while traceroute helps identify where delays or failures occur. If a ping times out or a traceroute shows unreachable hops, it could be due to firewall settings blocking traffic or high congestion at a network point. Overall, these tools helped me visualize network communication and taught me how to interpret packet loss, delays and routing patterns. This knowledge is essential for identifying and solving internet connectivity issues effectively.