1 .\" Copyright (c) 1989, 1995, 1996, 1997, 1999, 2000
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms are permitted
5 .\" provided that the above copyright notice and this paragraph are
6 .\" duplicated in all such forms and that any documentation,
7 .\" advertising materials, and other materials related to such
8 .\" distribution and use acknowledge that the software was developed
9 .\" by the University of California, Berkeley. The name of the
10 .\" University may not be used to endorse or promote products derived
11 .\" from this software without specific prior written permission.
12 .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
13 .\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
14 .\" WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
16 .Dd September 21, 2000
21 .Nd print the route packets take to network host
36 .Op Fl z Ar pausemsecs
40 The Internet is a large and complex aggregation of
41 network hardware, connected together by gateways.
42 Tracking the route one's packets follow (or finding the miscreant
43 gateway that's discarding your packets) can be difficult.
45 utilizes the IP protocol `time to live' field and attempts to elicit an
48 response from each gateway along the path to some
51 The only mandatory parameter is the destination host name or IP number.
52 The default probe datagram length is 40 bytes, but this may be increased
53 by specifying a packet size (in bytes) after the destination host
59 Set the initial time-to-live used in the first outgoing probe packet.
61 Set the "don't fragment" bit.
63 Enable socket level debugging.
65 Specify a loose source route gateway (8 maximum).
67 Specify a network interface to obtain the source IP address for
68 outgoing probe packets. This is normally only useful on a multi-homed
71 flag for another way to do this.)
77 datagrams. (A synonym for "-P icmp").
79 Set the initial time-to-live value used in outgoing probe packets.
80 The default is 1, i.e., start with the first hop.
82 Set the max time-to-live (max number of hops) used in outgoing probe
83 packets. The default is
85 hops (the same default used for
89 Disables the increment of the destination port (see -p). Useful for using tcpdump through firewalls.
91 Print hop addresses numerically rather than symbolically and numerically
92 (saves a nameserver address-to-name lookup for each gateway found on the
95 Send packets of specified IP protocol. The currently supported protocols
104 Other protocols may also be specified (either by name or by number), though
106 does not implement any special knowledge of their packet formats. This
107 option is useful for determining which router along a path may be
108 blocking packets based on IP protocol number. But see BUGS below.
110 Protocol specific. For
116 number used in probes (default is 33434).
118 hopes that nothing is listening on
124 at the destination host (so an
128 be returned to terminate the route tracing). If something is
129 listening on a port in the default range, this option can be used
130 to pick an unused port range.
132 Set the number of probes per ``ttl'' to
134 (default is three probes).
136 Bypass the normal routing tables and send directly to a host on an attached
138 If the host is not on a directly-attached network,
139 an error is returned.
140 This option can be used to ping a local host through an interface
141 that has no route through it (e.g., after the interface was dropped by
144 Use the following IP address
145 (which must be given as an IP number, not
146 a hostname) as the source address in outgoing probe packets. On
147 hosts with more than one IP address, this option can be used to
148 force the source address to be something other than the IP address
149 of the interface the probe packet is sent on. If the IP address
150 is not one of this machine's interface addresses, an error is
151 returned and nothing is sent.
154 flag for another way to do this.)
156 Print a summary of how many probes were not answered for each hop.
160 in probe packets to the following value (default zero). The value must be
161 a decimal integer in the range 0 to 255. This option can be used to
162 see if different types-of-service result in different paths. (If you
165 or later system, this may be academic since the normal network
166 services like telnet and ftp don't let you control the
171 meaningful \- see the IP spec for definitions. Useful values are
178 Verbose output. Received
186 Set the time (in seconds) to wait for a response to a probe (default 5 sec.).
188 Toggle IP checksums. Normally, this prevents traceroute from calculating
189 IP checksums. In some cases, the operating system can overwrite parts of
190 the outgoing packet but not recalculate the checksum (so in some cases
191 the default is to not calculate checksums and using
193 causes them to be calculated). Note that checksums are usually required
194 for the last hop when using
198 ). So they are always calculated when using ICMP.
199 .It Fl z Ar pausemsecs
200 Set the time (in milliseconds) to pause between probes (default 0).
201 Some systems such as Solaris and routers such as Ciscos rate limit
202 ICMP messages. A good value to use with this this is 500 (e.g. 1/2 second).
205 This program attempts to trace the route an IP packet would follow to some
206 internet host by launching
209 packets with a small ttl (time to live) then listening for an
211 "time exceeded" reply from a gateway. We start our probes
212 with a ttl of one and increase by one until we get an
215 (which means we got to "host") or hit a max (which
218 hops & can be changed with the
223 flag) are sent at each ttl setting and a
224 line is printed showing the ttl, address of the gateway and
225 round trip time of each probe. If the probe answers come from
226 different gateways, the address of each responding system will
227 be printed. If there is no response within a 5 sec. timeout
228 interval (changed with the
230 flag), a "*" is printed for that
233 We don't want the destination
236 probe packets so the destination port is set to an
237 unlikely value (if some clod on the destination is using that
238 value, it can be changed with the
242 A sample use and output might be:
244 [yak 71]% traceroute nis.nsf.net.
245 traceroute to nis.nsf.net (35.1.1.48), 64 hops max, 38 byte packet
246 1 helios.ee.lbl.gov (128.3.112.1) 19 ms 19 ms 0 ms
247 2 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms
248 3 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 39 ms 19 ms
249 4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 39 ms 40 ms 39 ms
250 5 ccn-nerif22.Berkeley.EDU (128.32.168.22) 39 ms 39 ms 39 ms
251 6 128.32.197.4 (128.32.197.4) 40 ms 59 ms 59 ms
252 7 131.119.2.5 (131.119.2.5) 59 ms 59 ms 59 ms
253 8 129.140.70.13 (129.140.70.13) 99 ms 99 ms 80 ms
254 9 129.140.71.6 (129.140.71.6) 139 ms 239 ms 319 ms
255 10 129.140.81.7 (129.140.81.7) 220 ms 199 ms 199 ms
256 11 nic.merit.edu (35.1.1.48) 239 ms 239 ms 239 ms
259 Note that lines 2 & 3 are the same. This is due to a buggy
260 kernel on the 2nd hop system \- lbl-csam.arpa \- that forwards
261 packets with a zero ttl (a bug in the distributed version
264 Note that you have to guess what path
265 the packets are taking cross-country since the
268 doesn't supply address-to-name translations for its
271 A more interesting example is:
273 [yak 72]% traceroute allspice.lcs.mit.edu.
274 traceroute to allspice.lcs.mit.edu (18.26.0.115), 64 hops max
275 1 helios.ee.lbl.gov (128.3.112.1) 0 ms 0 ms 0 ms
276 2 lilac-dmc.Berkeley.EDU (128.32.216.1) 19 ms 19 ms 19 ms
277 3 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 19 ms 19 ms
278 4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 19 ms 39 ms 39 ms
279 5 ccn-nerif22.Berkeley.EDU (128.32.168.22) 20 ms 39 ms 39 ms
280 6 128.32.197.4 (128.32.197.4) 59 ms 119 ms 39 ms
281 7 131.119.2.5 (131.119.2.5) 59 ms 59 ms 39 ms
282 8 129.140.70.13 (129.140.70.13) 80 ms 79 ms 99 ms
283 9 129.140.71.6 (129.140.71.6) 139 ms 139 ms 159 ms
284 10 129.140.81.7 (129.140.81.7) 199 ms 180 ms 300 ms
285 11 129.140.72.17 (129.140.72.17) 300 ms 239 ms 239 ms
287 13 128.121.54.72 (128.121.54.72) 259 ms 499 ms 279 ms
292 18 ALLSPICE.LCS.MIT.EDU (18.26.0.115) 339 ms 279 ms 279 ms
295 Note that the gateways 12, 14, 15, 16 & 17 hops away
298 "time exceeded" messages or send them
299 with a ttl too small to reach us. 14 \- 17 are running the
301 C Gateway code that doesn't send "time exceeded"s. God
302 only knows what's going on with 12.
304 The silent gateway 12 in the above may be the result of a bug in
307 network code (and its derivatives): 4.x (x <= 3)
308 sends an unreachable message using whatever ttl remains in the
309 original datagram. Since, for gateways, the remaining ttl is
312 "time exceeded" is guaranteed to not make it back
313 to us. The behavior of this bug is slightly more interesting
314 when it appears on the destination system:
316 1 helios.ee.lbl.gov (128.3.112.1) 0 ms 0 ms 0 ms
317 2 lilac-dmc.Berkeley.EDU (128.32.216.1) 39 ms 19 ms 39 ms
318 3 lilac-dmc.Berkeley.EDU (128.32.216.1) 19 ms 39 ms 19 ms
319 4 ccngw-ner-cc.Berkeley.EDU (128.32.136.23) 39 ms 40 ms 19 ms
320 5 ccn-nerif35.Berkeley.EDU (128.32.168.35) 39 ms 39 ms 39 ms
321 6 csgw.Berkeley.EDU (128.32.133.254) 39 ms 59 ms 39 ms
328 13 rip.Berkeley.EDU (128.32.131.22) 59 ms ! 39 ms ! 39 ms !
331 Notice that there are 12 "gateways" (13 is the final
332 destination) and exactly the last half of them are "missing".
333 What's really happening is that rip (a Sun-3 running Sun OS3.5)
334 is using the ttl from our arriving datagram as the ttl in its
336 reply. So, the reply will time out on the return path
337 (with no notice sent to anyone since
341 until we probe with a ttl that's at least twice the path
342 length. I.e., rip is really only 7 hops away. A reply that
343 returns with a ttl of 1 is a clue this problem exists.
345 prints a "!" after the time if the ttl is <= 1.
346 Since vendors ship a lot of obsolete
351 software, expect to see this problem
352 frequently and/or take care picking the target host of your
355 Other possible annotations after the time are
360 (host, network or protocol unreachable),
362 (source route failed),
364 (fragmentation needed \- the RFC1191 Path MTU Discovery value is displayed),
366 (communication administratively prohibited),
368 (host precedence violation),
370 (precedence cutoff in effect), or
372 (ICMP unreachable code <num>).
373 These are defined by RFC1812 (which supersedes RFC1716).
374 If almost all the probes result in some kind of unreachable,
376 will give up and exit.
378 This program is intended for use in network testing, measurement
380 It should be used primarily for manual fault isolation.
381 Because of the load it could impose on the network, it is unwise to use
383 during normal operations or from automated scripts.
385 Implemented by Van Jacobson from a suggestion by Steve Deering. Debugged
386 by a cast of thousands with particularly cogent suggestions or fixes from
387 C. Philip Wood, Tim Seaver and Ken Adelman.
392 When using protocols other than UDP, functionality is reduced.
393 In particular, the last packet will often appear to be lost, because
394 even though it reaches the destination host, there's no way to know
395 that because no ICMP message is sent back.
398 should listen for a RST from the destination host (or an intermediate
399 router that's filtering packets), but this is not implemented yet.