Post #4 – Traveling Through a Network



What a Struggle....

This was actually my least favorite part of the course. I was completely lost and confused. I had never heard of the terms "Ping Command" or " Traceroute". I really didn't score well on this assignment, but I was able to complete the assignment partially. 

This week, I learned how data travels across the internet using two important tools: ping and traceroute. These commands introduced me to understanding how packets move from my computer to websites around the world.


While using the Ping Command, I performed test on the following websites:

  • Google.com (Packets: Sent = 4, Received, =4 Lost = 0, Maximum = 149ms)
  • BPN.com    ( Packets: Sent =4, Received = 4, Lost = 0, Maximum = 51ms)
  • Baidu.com   ( Packets: Sent =4, Received = 4, Lost = 0, Maximum = 291)








I also had to use the command Traceroute for the very first time to see the path that the packets take to reach each of the following websites.

  • Google.com: (20 hops, smooth route, final latency ~21 ms) 
  • Baidu.com: (23 hops, Consistent RTT= 231 )
  • Nic.br:      ((Brazil) – Reached at hop 4, latency between 202–283 ms )













This week, I learned how data travels across the internet using two tools called ping and traceroute. These commands helped me see how packets move from my computer to websites around the world, and how long it takes for them to get there and back.

Using the ping command, I learned how to test several websites. Google.com responded quickly with an average roundtrip time of 12 milliseconds. BPN.com was slightly slower at 22 milliseconds, and Baidu.com which is located in China had a much higher latency of 266 milliseconds. That showed me how distance affects speed.

Next, I used the traceroute command to see the path my packets took. Google.com had a smooth route with 20 hops and low latency. BPN.com followed a similar path. Baidu.com took a longer route across the Pacific Ocean, which explained the higher latency.


I even traced routes to Brazil (nic.br) and Asia (www.whsifen.com), and both showed higher roundtrip times well over 200 milliseconds because of the long distance and international routing.

From these tests, I learned that roundtrip time increases with geographical distance. Servers that are closer respond faster. Servers that are overseas take longer because the data has to travel through more routers and across oceans.

Ping and traceroute are great tools for troubleshooting internet problems. Ping tells you if a server is reachable and how stable the connection is. Traceroute shows me where delays or failures happen along the way. Sometimes these tools don’t work sometimes because a firewall blocks them or because the network is too congested to respond.

Overall, this assignment helped me understand how the internet really works. It’s not just clicking a link but it’s a journey of packets across routers, networks, and continents. Now I know a little bit more about how to test and troubleshoot connections like a tech pro.


Comments

Popular posts from this blog

Post #2 – My Review of the Samsung Health App

From Pest to Protect: About Me

Post #1- " A Programmer in the Making"