Traveling Through a Network
For this exercise and in addition to pinging Google, I chose to ping
and
sina.com.cn
Below is the information and screenshot of my results.
Part 1:
Ping Activity
GOOGLE:
Pinging
google.com [142.250.68.14] with 32 bytes of data:
Reply from
142.250.68.14: bytes=32 time=30ms TTL=59
Reply from
142.250.68.14: bytes=32 time=26ms TTL=59
Reply from
142.250.68.14: bytes=32 time=27ms TTL=59
Reply from
142.250.68.14: bytes=32 time=34ms TTL=59
Ping statistics
for 142.250.68.14:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate
round trip times in milli-seconds:
Minimum = 26ms, Maximum = 34ms, Average = 29ms
ONLYMELBORUNE.COM.AU:
Pinging
www.onlymelbourne.com.au [104.26.8.2] with 32 bytes of data:
Reply from
104.26.8.2: bytes=32 time=104ms TTL=58
Reply from
104.26.8.2: bytes=32 time=29ms TTL=58
Reply from
104.26.8.2: bytes=32 time=30ms TTL=58
Reply from
104.26.8.2: bytes=32 time=34ms TTL=58
Ping statistics
for 104.26.8.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate
round trip times in milli-seconds:
Minimum = 29ms, Maximum = 104ms, Average = 49ms
SINA.COM.CN:
Pinging
sina.com.cn [36.51.254.91] with 32 bytes of data:
Reply from
36.51.254.91: bytes=32 time=239ms TTL=53
Reply from
36.51.254.91: bytes=32 time=236ms TTL=53
Reply from
36.51.254.91: bytes=32 time=237ms TTL=53
Reply from
36.51.254.91: bytes=32 time=239ms TTL=53
Ping statistics
for 36.51.254.91:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate
round trip times in milli-seconds:
Minimum = 236ms, Maximum = 239ms, Average = 237ms
Part 2: Traceroute Activity
GOOGLE:
Router passes: 9
Round-trip: between 4-32 ms
Failures: 0
ONLYMELBORUNE.COM.AU:
Router passed: 8
Round-trip: between 3-52 ms
Failures: 1
SINA.COM.CN:
Router passes: 14
Round-trip: between 4-300 ms
Failures: 2
According to Liu (2012),"Ping and Traceroute utility has been a fundamental tool for a network service provider or an enterprise network operator to run its IPv4 network for various kinds of services, data/voice/video. (pa. 1). I use ping and traceroutes on a weekly basis, but typically within my work environment. Using the ping and traceroutes for the internet is something I rarely do and was interesting to see the results. It was amazing to see the difference between running those commands on a site within the U.S. compared to a location outside of the states. As for how packets travel, our textbook states “A computer communicates via the Internet by sending a packet, containing information like an address for a destination computer, the data size, and the data itself.”. (Vahid, 2019). This means when there is an attempt to communicate with a website via a desktop, laptop, or mobile device, there is a connection to that specific website/server via a message (aka, packet) which is essentially like the shaking of hands to allow entry to that site.
In comparing the
ping and traceroute commands, the ping gives a quick overview of the specific
site or IP address while the traceroute provides more detail on the “trip”. A
ping shows that the site or address requested either does or does not exist. It
will typically return with the IP (Internet Protocol) address for that site. As
mentioned, most of my pings and traceroutes are local, so it was really
enlightening to see the results of those commands to a site outside of the
United States. When running the commands on Google, the passes weren’t that
much different from those addresses outside of the U.S. The major difference
was when looking at the time it took to hop from router to router. Google
stayed within a decent range while the sites outside in another country took as
much as 300 milliseconds. In human terms, that doesn’t seem long but in
computer and network terms, that could mean an eternity.
The ping and
traceroute commands are very handy tools when attempting to find if an address
exists. This could be for a website, network router, server, or even a
computer. At work, I will use these commands to test if a PC or server is
connected to our network and find out the IP address it is returning. If I by
chance only have the IP address of a server or PC, I can use the traceroute to
find out the assigned name of that PC or server.
One reason a
ping or traceroute could come back with a timeout is if the PC or server is not
connected to the network. This could indicate an issue with the cabling, the
NIC card, the network port, or even the router. Another reason for a failed
ping or traceroute is if there is an error or typo in the address. If there is
even one number off from the actual correct address, this could result in a
failed attempt.
Resources
Liu, C. J. (2012). Enhanced IPv6 ping and traceroute. 2012 21st Annual Wireless & Optical Communications Conference (WOCC), 51–58. https://doi.org/10.1109/WOCC.2012.6198147
Vahid, F., & Lysecky, S. (2019). Computing technology for all. zyBooks.


Comments
Post a Comment