Traveling through the network; Week 3

-

 Part 1 - PING:

ping 1

ping 2

ping 3

Part 2 - TRACEPORT:

ping 4

ping 5

ping 6

 

 

Running the ping and traceroute commands gave me a better understanding of how data moves across a network. The ping command sends packets to a specific IP address and calculates the roundtrip time (RTT), which tells you how fast the connection is and if the destination is reachable. It’s a simple but effective tool to test network performance. On the other hand, traceroute shows the exact path that packets take to get to the destination, listing every router or "hop" along the way. When I tested google.com, amazon.ca, and amazon.in, there were some clear differences in response times. Google returned the fastest RTTs, mostly ranging between 16–21 ms. Amazon Canada was somewhere in the middle (16-31ms), and Amazon India was the slowest, with RTTs mostly between 102–134 ms. These results make sense to me, since the farther the server is physically, the longer it takes for data to travel there and back. The traceroute results helped back this up. For example, the path to Amazon India included over a dozen hops, with several transitions through different network providers and a jump across the Atlantic. This helped visualize how each extra step adds potential delay; and where those delays start to pile up.

Overall, these two commands are super helpful for troubleshooting internet issues. If the ping fails, it might mean the server is down or blocked by a firewall. If the traceroute shows delays/failures during specific hops, it can help narrow down where the problem is occurring. Both tools give great insight into how internet traffic works and where problems might be popping up. 



The response I received from my Professor: "Good response in this discussion."

Comments

Post a Comment

Popular posts from this blog

Week 5 - The Final Post

-
It’s wild to think how something as everyday as a mobile app is rooted in so many deep IT fundamentals. After learning more throughout this course, I now see how connected my blog topic is to everything we’ve studied—from the history of computers to networks and databases. Web and mobile apps aren’t just creative tools or job-generating platforms; they result from decades of IT evolution, hardware innovation, and software development (Hanif et al., 2019). Tied to Tech’s Origins and Operation    Web and mobile apps wouldn’t exist without the evolution of computing. Applications have gone from running on massive mainframe computers to living in the cloud today. They remain closely tied to the foundational IT principles of input/output, software architecture, networking, and programming logic. We witness a modern take on decades of computer science advancement each time we tap an app. Hardware Still Matters    Even though apps seem simple, they rely on essential hardwar...
Read more

A day in my life; Week 2

-
An everyday normal day in my life:  1. Go to my job – I spent a good portion of my day handling tasks related to my job in insurance. This included responding to client inquiries, updating policy details, and ensuring coverage accuracy. It's always busy, but I enjoy the challenges it brings and meeting new people. 2. Took the dogs for a walk – I took my two golden retrievers for a walk when I get out of work. It’s not only good for them but also gives me a mental break and a chance to enjoy some fresh air. 3. Cooked dinner – Most nights I prepared a home-cooked meal. It’s usually fairly simple, but I find cooking to be a relaxing and rewarding task, especially after a long day. 4. Work on marketing material – I spent some time creating and refining marketing content aimed at attracting new clients. This included writing a few posts for social media to promote myself. 5. Watch some of a series on Netflix – After a long day, I end my day by watching a few episodes of a seri...
Read more