What Is Traceroute Command Used For and How Does It Work

What
is
1.
In
displaying
across
traceroute
command
used
for
and
how
computing,
traceroute
is
a
computer
network
the
route
(path)
and
measuring
transit
an
Internet
Protocol
does
diagnostic
delays
of
(IP)
it
work?
tool
for
packets
network.
2.
Traceroute sends a sequence of three Internet Control Message Protocol
(ICMP)
echo
request
packets
addressed
to
a
destination
host.
The
time-to-live
(TTL)
value,
also
known
as
hop
limit,
is
used
in
determining
the
intermediate
routers
being
traversed
towards
the
destination.
Routers
decrement
packets'
TTL
value
by
1
when
routing
and
discard
packets
whose
TTL
value
has
reached
zero,
returning
the
ICMP error message ICMP Time Exceeded. Common default values for TTL
are
128
(Windows
OS)
and
64
(Linux-based
OS).
3.
Traceroute
works
by
sending
packets
with
gradually
increasing
TTL
value,
starting
with
TTL
value
=
1.
The
first
router
receives
the
packet, decrements the TTL value
and
drops the packet because
it then
has TTL value zero. The router sends an ICMP Time Exceeded message
back to the source. The next set of packets are given a TTL value of
2,
so
the
first
router
forwards
the
packets,
but
the
second
router
drops
them
and
replies
with
ICMP
Time
Exceeded.
Proceeding
in
this
way, traceroute uses the returned ICMP Time Exceeded messages to build
a
list
of
routers
that
packets
traverse,
until
the
destination
is
reached and returns an ICMP Echo Reply message.
Perform traceroute between source and destination on the same
continent at three different hours of the day:
Firstrun:
%traceroute yahoo.com
traceroute
to yahoo.com (98.139.183.24),
30
hops
max,
60
byte
packets
1
10.124.96.65
(10.124.96.65)
955.423
ms
955.625
ms
965.368
ms
2
10.124.76.98
(10.124.76.98)
955.892
ms
965.348
ms
974.747
ms
3
10.124.76.131
(10.124.76.131)
974.871
ms
1165.105
ms
1174.659
ms
4
115.113.164.169.static-mumbai.vsnl.net.in (115.113.164.169)
1174.767
ms
1174.740
ms
1184.483
ms
5
172.29.250.33
(172.29.250.33)
1184.017
ms
1193.796
ms
1193.932
ms
6
ix-0-100.tcore1.MLV-Mumbai.as6453.net (180.87.38.5)
1194.087
ms
*
69.835
ms
7
if-9-5.tcore1.WYN-Marseille.as6453.net (80.231.217.17)
379.664
ms
329.773
ms
349.660
ms
8
*
*
*
9
if-5-2.tcore1.WV6-Madrid.as6453.net (80.231.200.6)
349.729
ms
349.790
ms
369.357
ms
10
if-8-2.tcore2.SV8-Highbridge.as6453.net (80.231.91.26)
389.055
ms
409.092
ms
360.022
ms
11
350.259
ms
350.591
ms
349.929
ms
12
if-6-2.tcore1.NJY-Newark.as6453.net (80.231.138.18)
349.676
ms
360.157
ms
340.043
ms
13
339.874
ms
369.320
ms
359.783
ms
14
if-3-2.tcore2.AEQ-Ashburn.as6453.net (216.6.87.9)
349.884
ms
349.679
ms
359.197
ms
15
216.6.51.26
(216.6.51.26)
339.098
ms
64.86.85.34
(64.86.85.34)
338.814
ms
209.58.27.54
(209.58.27.54)
368.813
ms
16
ae-6.pat2.dcp.yahoo.com (216.115.102.178)
408.517
ms
408.811
ms
349.293
ms
17
ae-2-d181.pat2.da3.yahoo.com (216.115.104.115)
359.117
ms
359.236
ms ae-7.pat2.che.yahoo.com (216.115.100.137)
359.753
ms
18
xe-1-2-0.pat2.bfy.yahoo.com (216.115.97.204)
369.670
ms
UNKNOWN-216-115-96-X.yahoo.com (216.115.96.117)
389.793
ms
ae-5.pat1.bfz.yahoo.com (216.115.96.65)
389.373
ms
19
ge-0-0-0.pat2.bfz.yahoo.com (216.115.97.209)
389.969
ms
ge-1-0-0.pat2.bfz.yahoo.com (216.115.97.207)
389.300
ms
ae-4.pat1.bfz.yahoo.com (216.115.97.211)
379.910
ms
20
ae-4.msr2.bf1.yahoo.com (216.115.100.73)
389.400
ms
po16.bas2-4-yst.bf1.yahoo.com (98.139.130.11)
369.600
ms
xe-8-0-0.clr2-a-gdc.bf1.yahoo.com (98.139.232.91)
389.032
ms
21
UNKNOWN-98-139-129-X.yahoo.com (98.139.129.173)
389.706
ms
xe-9-0-0.clr1-a-gdc.bf1.yahoo.com (98.139.232.101)
399.644
ms
et17-1.fab7-1-sat.bf1.yahoo.com (98.139.128.89)
359.515
ms
22
po-15.bas1-7-prd.bf1.yahoo.com (98.139.129.241)
389.655
ms
et-17-1.fab3-1-gdc.bf1.yahoo.com (98.139.128.41)
379.683
ms
et17-1.fab7-1-sat.bf1.yahoo.com (98.139.128.89)
359.565
ms
23
*
*
*
24
*
*
*
25
*
*
*
26
*
*
*
27
*
*
*
28
*
*
*
29
*
*
*
30 * * *
SecondRun:
traceroute
to yahoo.com (98.138.253.109),
30
hops
max,
60
byte
packets
1
10.124.96.65
(10.124.96.65)
78.258
ms
101.315
ms
101.193
ms
2
10.124.76.98
(10.124.76.98)
101.076
ms
117.978
ms
118.045
ms
3
10.124.76.131
(10.124.76.131)
118.032
ms
137.670
ms
137.360
ms
4
217.406
ms
217.475
ms
217.487
ms
5
172.29.250.33
(172.29.250.33)
217.636
ms
217.668
ms
217.704
ms
6
*
*
*
7
if-9-5.tcore1.WYN-Marseille.as6453.net (80.231.217.17)
343.470
ms
*
362.825
ms
8
*
*
*
9
if-5-2.tcore1.WV6-Madrid.as6453.net (80.231.200.6)
402.449
ms
402.830
ms
402.493
ms
10
442.184
ms
442.334
ms
359.825
ms
11
369.664
ms
359.998
ms
369.836
ms
12
379.677
ms
369.899
ms
350.247
ms
13
339.772
ms
359.373
ms
350.408
ms
14
if-3-2.tcore2.AEQ-Ashburn.as6453.net (216.6.87.9)
369.593
ms
350.178
ms
369.484
ms
15
64.86.85.34
(64.86.85.34)
340.337
ms
64.86.85.38
(64.86.85.38)
369.987
ms
64.86.85.34
(64.86.85.34)
359.794
ms
16
360.503
ms
ae-6.pat2.dce.yahoo.com (216.115.102.176)
349.693
ms
349.320
ms
17
ae-6.pat1.che.yahoo.com (216.115.96.81)
380.159
ms
379.634
ms
380.594
ms
18
ae-0.pat2.nez.yahoo.com (216.115.100.10)
349.543
ms
ae-3.pat2.dnx.yahoo.com (216.115.96.58)
379.101
ms
as-2.pat2.dnx.yahoo.com (216.115.100.65)
390.407
ms
19
xe-7-0-0.msr1.ne1.yahoo.com (216.115.100.5)
379.938
ms
399.278
ms
389.980
ms
20
xe-4-0-0.clr1-a-gdc.ne1.yahoo.com (98.138.144.21)
359.231
ms
360.536
ms xe-7-0-0.msr2.ne1.yahoo.com (216.115.100.7)
419.573
ms
21
419.445
ms
et-17-1.fab1-1-gdc.ne1.yahoo.com (98.138.0.79)
379.280
ms
399.333
ms
22
po-13.bas2-7-prd.ne1.yahoo.com (98.138.240.28)
359.765
ms
et-17-1.fab3-1-gdc.ne1.yahoo.com (98.138.0.77)
379.656
ms
po-10.bas2-7-prd.ne1.yahoo.com (98.138.240.22)
339.785
ms
23
*
* po-12.bas1-7-prd.ne1.yahoo.com (98.138.240.10)
379.838
ms
24
*
*
*
25
*
*
*
26
*
*
*
27
*
*
*
28
*
*
*
29
*
*
*
30 * * *
Thirdrun:
traceroute
to yahoo.com (206.190.36.45),
30
hops
max,
60
byte
packets
1
10.124.96.97
(10.124.96.97)
299.107
ms
299.202
ms
299.393
ms
2
10.124.76.98
(10.124.76.98)
299.499
ms
300.187
ms
300.358
ms
3
10.124.76.131
(10.124.76.131)
308.920
ms
308.683
ms
309.077
ms
4
309.288
ms
309.124
ms
309.357
ms
5
ix-0-100.tcore2.MLV-Mumbai.as6453.net (180.87.39.25)
309.583
ms
86.099
ms
85.727
ms
6
if-9-2.tcore2.CXR-Chennai.as6453.net (180.87.37.9)
376.300
ms
375.908
ms
369.840
ms
7
if-6-2.tcore2.SVW-Singapore.as6453.net (180.87.37.14)
400.100
ms
410.774
ms
399.733
ms
8
if-7-2.tcore2.LVW-LosAngeles.as6453.net (180.87.15.26)
379.587
ms
410.275
ms
389.624
ms
9
if-2-2.tcore1.LVW-LosAngeles.as6453.net (66.110.59.1)
409.736
ms
410.023
ms
419.480
ms
10
if-8-2.tcore2.DT8-Dallas.as6453.net (66.110.57.81)
439.681
ms
439.244
ms
349.803
ms
11
216.6.53.14
(216.6.53.14)
369.665
ms
66.198.2.10
(66.198.2.10)
359.750
ms
66.198.2.14
(66.198.2.14)
389.619
ms
12
ae-9.pat1.dnx.yahoo.com (216.115.96.79)
379.641
ms
400.047
ms
ae-5.pat2.pao.yahoo.com (216.115.101.130)
359.849
ms
13
ae-0.pat1.swp.yahoo.com (216.115.110.43)
389.667
ms
ae-6.pat2.gqb.yahoo.com (216.115.96.62)
379.828
ms
ae-0.pat1.swp.yahoo.com (216.115.110.43)
369.601
ms
14
389.509
ms
409.128
ms
419.405
ms
15
ae-1.msr2.gq1.yahoo.com (66.196.67.3)
419.207
ms
ae-1.msr1.gq1.yahoo.com (66.196.67.5)
438.932
ms
458.636
ms
16
et-17-1.fab5-1-gdc.gq1.yahoo.com (98.137.31.180)
379.406
ms
xe-9-0-0.clr1-a-gdc.gq1.yahoo.com (98.137.31.137)
409.659
ms
388.964
ms
17
po-14.bas1-7-prd.gq1.yahoo.com (206.190.32.23)
398.865
ms
409.553
ms
428.538
ms
18
428.630
ms
*
*
19
*
*
*
20
*
*
*
21
*
*
*
22
*
*
*
23
*
*
*
24
*
*
*
25
*
*
*
26
*
*
*
27
*
*
*
28
*
*
*
29
*
*
*
30 * * *
Try to identify the number of ISP networks that the traceroute packets pass through from source to
destination. Routers with the similar names and/or similar IP address should be considered as part of
the same ISP. In your experiments, do the largest delays occur at the peering interfaces between
adjacent
ISPs?
These answers are highly ISP dependent. Ive used Tata DOCOMO as my ISP to derive the resultsabove. Furthermore, using the results above we can deduce that :-
(a)
The traffic from India to Yahoo.com is going through static.vsnl.net.in ( our international
gateway.
(b)
We can also infer that routing is dynamic from the fact that the route is resolved in a different
way each time. If you see the traces above #1 through #4 are common 'hops' but after that the routing
is determined by TCP/IP traffic through the various backbones.

What Is Traceroute Command Used For and How Does It Work

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

What Is Traceroute Command Used For and How Does It Work

Caricato da

Copyright:

Formati disponibili

What

Potrebbero piacerti anche