1TRACEPATH(8)           System Manager's Manual: iputils           TRACEPATH(8)
2
3
4

NAME

6       tracepath,  tracepath6  - traces path to a network host discovering MTU
7       along this path
8

SYNOPSIS

10       tracepath destination [ port]
11
12

DESCRIPTION

14       It traces path to destination discovering MTU along this path.  It uses
15       UDP  port  port or some random port.  It is similar to traceroute, only
16       does not not require superuser privileges and has no fancy options.
17
18       tracepath6 is good replacement for traceroute6 and classic  example  of
19       application  of  Linux  error  queues.  The situation with tracepath is
20       worse, because commercial IP routers do not return  enough  information
21       in  icmp  error  messages.  Probably, it will change, when they will be
22       updated.  For now it uses Van Jacobson's trick, sweeping a range of UDP
23       ports to maintain trace history.
24

OUTPUT

26       root@mops:~ # tracepath6 3ffe:2400:0:109::2
27        1?: [LOCALHOST]                              pmtu 1500
28        1:  dust.inr.ac.ru                   0.411ms
29        2:  dust.inr.ac.ru        asymm  1   0.390ms pmtu 1480
30        2:  3ffe:2400:0:109::2               463.514ms reached
31            Resume: pmtu 1480 hops 2 back 2
32
33       The  first  column  shows TTL of the probe, followed by colon.  Usually
34       value of TTL is obtained from reply from network, but  sometimes  reply
35       does not contain necessary information and we have to guess it. In this
36       case the number is followed by ?.
37
38       The second column shows the network hop, which replied  to  the  probe.
39       It  is  either  address of router or word [LOCALHOST], if the probe was
40       not sent to the network.
41
42       The rest of line shows miscellaneous information about path to the cor‐
43       respinding  hetwork  hop.  As rule it contains value of RTT.  Addition‐
44       ally, it can show Path MTU, when it changes.  If the path is asymmetric
45       or  the  probe  finishes  before  it  reach  prescribed hop, difference
46       between number of hops in forward and backward direction is shown  fol‐
47       loing  keyword async. This information is not reliable.  F.e. the third
48       line shows asymmetry of 1, it is because the first probe with TTL of  2
49       was rejected at the first hop due to Path MTU Discovery.
50
51       Te  last line summarizes information about all the path to the destina‐
52       tion, it shows detected Path MTU, amount of hops to the destination and
53       our guess about amount of hops from the destination to us, which can be
54       different when the path is asymmetric.
55

SEE ALSO

57       traceroute(8), traceroute6(8), ping(8).
58

AUTHOR

60       tracepath was written by Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>.
61

SECURITY

63       No security issues.
64
65       This lapidary deserves to be elaborated.  tracepath is not a privileged
66       program,  unlike  traceroute, ping and other beasts of this kind.  tra‐
67       cepath may be executed by everyone who  has  some  access  to  network,
68       enough  to  send  UDP datagrams to investigated destination using given
69       port.
70

AVAILABILITY

72       tracepath is part of  iputils  package  and  the  latest  versions  are
73       available  in source form at http://www.skbuff.net/iputils/iputils-cur
74       rent.tar.bz2.
75
76
77
78iputils-070202                   06 April 2007                    TRACEPATH(8)
Impressum