Traveling Through a Network

 Part 1: Ping Activity

Google.com

Screenshot (13)-1.png

Packets: sent- 4, received- 4, lost- 0

Roundtrip times: Minimum- 4ms, Maximum- 6ms, Average- 5ms

Yahoo.co.jp

Screenshot (15)-1.png

Packets: sent- 4, received-4, lost- 0

Roundtrip times: Minimum- 180ms, Maximum- 181ms, Average- 180ms

News.cn

Screenshot (17).png

Packets: sent- 4, received- 0, lost-4

Roundtrip times: Not received

Part 2: Traceroute Activity

Google.com

Screenshot (14).png

20 total hops, 11 timed out

Yahoo.co.jp

Screenshot (21).png

14 total hops, 5 timed out

News.cn

30 total hops, 20 timed out

Screenshot (19).png

Screenshot (20).png

Part 3: Traveling Through a Network Reflection Essay

Reflecting on your experience using the ping and traceroute commands, describe how packets travel through the network. 

Both the ping and traceroute provide information about the path that packets take through the network. Traceroute also includes geographical location of the hops. But, a ping can indirectly indicate geographical location. Longer roundtrip times suggest greater distance between the source and the destination and vise versa.

Ping and traceroute commands can be helpful in troubleshooting internet connection issues by identifying the time it takes the source to reach the destination. A successful ping suggests a good internet connection because the roundtrip time is low. If a traceroute is unsuccessful, it suggests  a network or router problem because of congestion or a slow router.

A ping request or traceroute command might time out or return with an error message because firewalls were blocking the packets or the network is congested.

Comments

Popular posts from this blog

Computers in the Workplace

Network Security

Documenting A Day