Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

The ping program allows you to send a test packet to a given location and see ho

ID: 3673575 • Letter: T

Question

The ping program allows you to send a test packet to a given location and see how
long it takes to get there and back. Try using ping to see how long it takes to get from
your location to several known locations. From these data, plot the one-way transit
time over the Internet as a function of distance. It is best to use universities since the
location of their servers is known very accurately. For example, berkeley.edu is in
Berkeley, California; mit.edu is in Cambridge, Massachusetts; vu.nl is in Amsterdam;
The Netherlands; www.usyd.edu.au is in Sydney, Australia; and www.uct.ac.za is in
Cape Town, South Africa.

Explanation / Answer

For this problem, I will made assumptions:

1. The server that I am pinging is located on the campus of the respective school.

2. The distance information (obtained through Mapquest.com) from my house to the respective campus is accurate (or at least close enough).

Below is a table of the summarizing the ping results and distances. The average one-way transit time was obtained taking half of the average round trip time.

C:Documents and Settingsdmin>ping berkeley.edu
Pinging berkeley.edu [169.229.131.92] with 32 bytes of data:
Reply from 169.229.131.92: bytes=32 time=15ms TTL=50
Reply from 169.229.131.92: bytes=32 time=15ms TTL=50
Reply from 169.229.131.92: bytes=32 time=17ms TTL=50
Reply from 169.229.131.92: bytes=32 time=14ms TTL=50
Ping statistics for 169.229.131.92:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 17ms, Average = 15ms

C:Documents and Settingsdmin>ping mit.edu

Pinging stanford.edu [171.67.20.37] with 32 bytes of data:
Reply from 171.67.20.37: bytes=32 time=25ms TTL=49
Reply from 171.67.20.37: bytes=32 time=15ms TTL=49
Reply from 171.67.20.37: bytes=32 time=25ms TTL=49
Reply from 171.67.20.37: bytes=32 time=23ms TTL=49
Ping statistics for 171.67.20.37:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:

Minimum = 15ms, Maximum = 25ms, Average = 22ms

C:Documents and Settingsdmin>ping vu.nl
Pinging ucla.edu [169.232.55.135] with 32 bytes of data:
Reply from 169.232.55.135: bytes=32 time=27ms TTL=49
Reply from 169.232.55.135: bytes=32 time=27ms TTL=49
Reply from 169.232.55.135: bytes=32 time=20ms TTL=49
Reply from 169.232.55.135: bytes=32 time=20ms TTL=49
Ping statistics for 169.232.55.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 27ms, Average = 23ms

C:Documents and Settingsdmin>ping www.uct.ac.za
Pinging princeton.edu [128.112.128.81] with 32 bytes of data:
Reply from 128.112.128.81: bytes=32 time=105ms TTL=46
Reply from 128.112.128.81: bytes=32 time=81ms TTL=46
Reply from 128.112.128.81: bytes=32 time=83ms TTL=46
Reply from 128.112.128.81: bytes=32 time=86ms TTL=46
Ping statistics for 128.112.128.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 105ms, Average = 88ms

C:Documents and Settingsdmin>ping ucla.edu
Pinging ucla.edu [169.232.55.135] with 32 bytes of data:
Reply from 169.232.55.135: bytes=32 time=27ms TTL=49
Reply from 169.232.55.135: bytes=32 time=27ms TTL=49
Reply from 169.232.55.135: bytes=32 time=20ms TTL=49
Reply from 169.232.55.135: bytes=32 time=20ms TTL=49
Ping statistics for 169.232.55.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 27ms, Average = 23ms

C:Documents and Settingsdmin>ping uiowa.edu
Pinging uiowa.edu [128.255.56.76] with 32 bytes of data:
Reply from 128.255.56.76: bytes=32 time=79ms TTL=46
Reply from 128.255.56.76: bytes=32 time=76ms TTL=46
Reply from 128.255.56.76: bytes=32 time=73ms TTL=46
Reply from 128.255.56.76: bytes=32 time=73ms TTL=46
Ping statistics for 128.255.56.76:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 79ms, Average = 75ms

C:Documents and Settingsdmin>ping www.usyd.edu.au
Pinging utah.edu [155.97.155.159] with 32 bytes of data:
Reply from 155.97.155.159: bytes=32 time=72ms TTL=241
Reply from 155.97.155.159: bytes=32 time=72ms TTL=241
Reply from 155.97.155.159: bytes=32 time=73ms TTL=241
Reply from 155.97.155.159: bytes=32 time=72ms TTL=241
Ping statistics for 155.97.155.159:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 73ms, Average = 72ms

CAMPUS ADDRESS AVERAGE TIME DISTANCE Cambridge mit.edu 11 ms 20 mi UC Berkeley berkeley.edu 7.5 ms
43 mi Amsterdam vu.nl 11.5 ms 336 mi Sydney www.usyd.edu.au 16.5 ms 661 mi
University of Utah utah.edu 36 ms 764 mi Cape Town www.uct.ac.za 44 ms 2936 mi
University of Iowa uiowa.edu 37.5 ms 1940 mi Michigan State University msu.edu 38 ms 2363 mi
Hire Me For All Your Tutoring Needs
Integrity-first tutoring: clear explanations, guidance, and feedback.
Drop an Email at
drjack9650@gmail.com
Chat Now And Get Quote