based on instructions need to perfrom it and then present report with
Search for question
Question
Based on instructions need to perfrom it and then present
report with explanations, screenshots and raw data.
Report and raw data are most important
Report Format
Write an experiment report (approximately 7-15 pages) that
describes your methodology and
results. Avoid verbose discussion of the results. Also, include
any additional results, insight, and
analysis of the results. Do not include raw results and
command runs in your report. In general,
your report should include the following components:
Abstract (summary) of your experiment and findings
Introduction (background and hypothesis)
Methodology used.
Results (plots and findings)
Conclusions
Answer to: What did you learn?/n Instructions
Please follow the pdf for all the instructions, please read the project
description very carefully.
Everything is in the pdf instructions, but I am also writing this again here below for better
understanding....
From the description:
Please submit the report in word or pdf format, and raw DATA files compressed as a
single file. Do not include raw ping or traceroute in the report document.
Timeouts might happen to some hosts during the day, but if a timeout occurs several
times in, say, two days a new host should be selected as soon as possible. Also, from the
description:
In addition, you should avoid routers and hosts that disable or don't support ICMP
functions (e.g., hosts that timeout without a response).
Also,
If a host doesn't complete the trace within the 30 hops for a few times, yes you
should pick a new one. However, if a website completes the trace most of the time
except few times, then there might be a network issue, and this would be part of
the hypothesis that you would have in your report.
Again,
There are two deliverables, the summary of the runs with comments and
discussion in the word or pdf document, and there is another deliverable that is the
raw commands./n CIS 427 Winter 2024
Project 3
Analyzing Network Delay and Routing Changes Over Time
Introduction
In this assignment, we will investigate the impact of network delays and delay variations on
applications like voice over IP and time-sensitive financial transactions. We will focus on
changes in network delays and jitter over a wide range of Internet paths and analyze them over
time. We will observe how routing changes can result in a rise in roundtrip delay for converged
paths. To identify network issues, we will employ the traceroute utility (for Linux systems)
and the tracert utility (for Windows systems), as well as the ping utility. Our goal is to assess
link latency for a five-day period and investigate how the latency and number of hops differ
throughout the day and week.
The Assignment
This assignment can be completed individually or by a group of two. In the case of a group
assignment, the group must work on a minimum of 10 target hosts per group, and an individual
student must work on at least 6 target hosts. It is important to note that this assignment is not
a continuation of programming assignments 1 or 2. If you choose to switch groups, please let
the instructor know as soon as possible and before submitting any work to canvas.
Routing measurement
Traceroute is a computer network diagnostic tool that is used to trace the path taken by a data
packet from its source to its destination over the Internet. The tool works by sending packets
with increasing Time-To-Live (TTL) values to the destination and recording the IP addresses of
the routers that the packet passes through before reaching its destination. By analyzing the list
of routers and their response times, traceroute can provide valuable information about the
path and performance of data packets traveling across the Internet. Traceroute is commonly
used by network administrators and internet service providers to troubleshoot network issues,
optimize network performance, and detect network congestion or outages.
The traceroute command on Windows. Open a command line (cmd or PowerShell) and run:
C:\> tracert www.yahoo.com
tries to determine the path from the source machine to www.yahoo.com. (Note that the command
should be traceroute www.yahoo.com, for Linux/UNIX based OS). The machine encountered on the
1 path after the first hop fob.net.umd.umich.edu [141.215.80.1], the next hop is i-cw-
elb.net.umd.umich.edu [141.215.2.33], and so on. In all, it takes 15 hops to reach
p13.www.dcn.yahoo.com.
C:\tracert www.yahoo.com
Tracing route to www.yahoo.akadns.net [216.109.118.71]
over a maximum of 30 hops:
1
<1 ms
<1 ms
<1 ms
fob.net.umd.umich.edu [141.215.80.1]
2
<1 ms
<1 ms
<1 ms
3
<1 ms
<1 ms
<1 ms
141.215.2.130
4
1 ms
1 ms
<1 ms
5
12 ms
12 ms
13 ms
198.108.22.165
6
24 ms
12 ms
12 ms
7
16 ms
15 ms
13 ms
8
82 ms
38 ms
39 ms
9
54 ms
40 ms
40 ms
10
51 ms
43 ms
44 ms
11
47 ms
45 ms
45 ms
12
45 ms
47 ms
46 ms
13
52 ms
47 ms
45 ms
i-cw-elb.net.umd.umich.edu [141.215.2.33]
i-merit.net.umd.umich.edu [141.215.2.2]
g1.ba21.b002281-1. ord01.atlas.cogentco.com [66.28.21.233]
p12-0.core02.ord01.atlas.cogentco.com [154.54.2.241]
p6-0.core02.jfk02.atlas.cogentco.com [66.28.4.85]
p14-0.core01.ph101.atlas.cogentco.com [66.28.4.2]
p4-0.core01.dca01.atlas.cogentco.com [66.28.4.17]
p2-0.core01.iad01.atlas.cogentco.com [154.54.2.202]
yahoo.iad01.atlas.cogentco.com [154.54.10.2]
ae1.p400.msr1.dcn.yahoo.com [216.115.96.181]
14
48 ms
47 ms
50 ms
15
45 ms
46 ms
78 ms
ge5-2.bas1-m.dcn.yahoo.com [216.109.120.151]
p8.www.dcn.yahoo.com [216.109.118.71]
Trace complete.
For this part of the assignment, you will monitor the routing stability of the Internet using
traceroute. Choose your destination hosts (`targets'). The targets should be distributed around
the world. Please do not monitor hosts of the .MIL domain. In addition, you should avoid
routers and hosts that disable or don't support ICMP functions (e.g., hosts that timeout
without a response).
1. Using traceroute from a fixed machine, monitor, and record the routing path to each
target for an entire 5 days. You should perform at least 3 measurements every day, for a
total of about 15 measurements per target for the duration of the 5 days.
2. You should perform all your measurements from a fixed location, for example at home
or on campus. Alternatively, you can log into the UMD Login server
(login.umd.umich.edu) and perform the measurement from the server.
3. Some host names may be dynamically mapped to several geographically dispersed
servers (e.g., www.cnn.com). Therefore, after you learn the IP address of a host name,
you need to use the IP address instead of the host name (e.g. tracert 23.235.40.73).
4. For which targets do you observe the same routing path in all measurements? For which
targets do you observe several different paths? Comment on the stability of the routes
that you have monitored.
2 5. For the paths that do tend to change, what is the nature of the routing change (e.g.,
differences in the number of hops, differences in the network providers that traffic goes
through, or differences in the exact router interfaces that traffic goes through)? Hint: To
identify the Autonomous System Number or ISP for each router, you can use the
command "whois -h whois.arin.net ASN" or "whois -h radb.ra.net IPaddr" or visit
http://www.arin.net/whois/ for more information.
6. For a path that is not stable, attempt to (roughly) estimate how often the route
changes. You may need to perform more frequent measurements to those targets.
Loss and Round-Trip Time (RTT) measurements
The ping utility is a valuable network testing tool that operates by transmitting a brief message
of the echo-request type to a host via the Internet Control Message Protocol (ICMP). This
protocol is used to send and receive error messages and operational information about
network conditions. A host that supports ICMP, which is most hosts, will receive an echo-
request message and reply by sending an echo-response message back to the original host.
The following is a sample output of an execution of ping:
C:\ping -n 120 amazon.in
Pinging amazon.in [52.95.116.115] with 32 bytes of data:
Reply from 52.95.116.115: bytes=32 time=113ms TTL=223
Reply from 52.95.116.115: bytes=32 time=195ms TTL=223
Reply from 52.95.116.115: bytes=32 time=117ms TTL=223
Reply from 52.95.116.115: bytes=32 time=182ms TTL=223
Reply from 52.95.116.115: bytes=32 time=188ms TTL=223
Reply from 52.95.116.115: bytes=32 time=190ms TTL=223
Reply from 52.95.116.115: bytes=32 time=195ms TTL=223
Ping statistics for 52.95.116.115:
Packets Sent = 120, Received = 120, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 113ms, Maximum = 205ms, Average = 167ms
In this part of the assignment, you will monitor the loss and delay performance characteristics
of some Internet paths using ping. You can use the same set of targets as in the previous part
of the assignment. It is better, however, to choose targets that do not experience frequent
routing changes.
3 1. As in the previous part of the assignment, measure the loss rate and RTTS for each
target for the duration of 5 days. You should perform at least 2 measurements every
day, for a total of about 10 measurements per target for the duration of the 5 days.
Each measurement should send 120 echo requests by using the -n count (number of
echo requests to send) option.
2. Use the previous measurements to classify your targets as `loss free', `minor losses' (0 <
loss rate<5%), `significant losses' (5% < loss rate <10%), and `major losses' (loss rate >
10%). Does this classification remain the same throughout the 5 days for each target?
3. Measure the minimum/maximum/mean RTT for each target.
4. Plot the loss rate and RTTs for each target as a function of time. Do you observe any
significant changes between different times-of-day or days-of-week?
Deliverables
Write an experiment report (approximately 7-15 pages) that describes your methodology and
results. Avoid verbose discussion of the results. Also, include any additional results, insight, and
analysis of the results. Do not include raw results and command runs in your report. In general,
your report should include the following components:
Abstract (summary) of your experiment and findings
Introduction (background and hypothesis)
Methodology used.
●
●
●
Results (plots and findings)
●
Conclusions
Answer to: What did you learn?
Please submit the report in word or pdf format, and raw DATA files compressed as a single file
to Canvas. Do not include raw ping or traceroute in the report document.
4