traceroute.8

来自「早期freebsd实现」· 8 代码 · 共 337 行

8
337
字号
.\" Copyright (c) 1990, 1991, 1993.\"	The Regents of the University of California.  All rights reserved..\".\" This code is derived from software contributed to Berkeley by.\" Van Jacobson..\".\" Redistribution and use in source and binary forms, with or without.\" modification, are permitted provided that the following conditions.\" are met:.\" 1. Redistributions of source code must retain the above copyright.\"    notice, this list of conditions and the following disclaimer..\" 2. Redistributions in binary form must reproduce the above copyright.\"    notice, this list of conditions and the following disclaimer in the.\"    documentation and/or other materials provided with the distribution..\" 3. All advertising materials mentioning features or use of this software.\"    must display the following acknowledgement:.\"	This product includes software developed by the University of.\"	California, Berkeley and its contributors..\" 4. Neither the name of the University nor the names of its contributors.\"    may be used to endorse or promote products derived from this software.\"    without specific prior written permission..\".\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION).\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF.\" SUCH DAMAGE..\".\"     @(#)traceroute.8	8.1 (Berkeley) 6/6/93.\".Dd June 6, 1993.Dt TRACEROUTE 8.Os BSD 4.3.Sh NAME.Nm traceroute.Nd print the route packets take to network host.Sh SYNOPSIS.Nm traceroute.Op Fl m Ar max_ttl.Op Fl n.Op Fl p Ar port.Op Fl q Ar nqueries.Op Fl r.Bk -words.Op Fl s Ar src_addr.Ek.Op Fl t Ar tos.Op Fl w Ar waittime.Ar host.Op Ar packetsize.Sh DESCRIPTIONThe Internet is a large and complex aggregation ofnetwork hardware, connected together by gateways.Tracking the route one's packets follow (or finding the miscreantgateway that's discarding your packets) can be difficult..Nm Tracerouteutilizes the IP protocol `time to live' field and attempts to elicit an.Tn ICMP.Dv TIME_EXCEEDEDresponse from each gateway along the path to somehost..PpThe only mandatory parameter is the destination host name or IP number.The default probe datagram length is 38 bytes, but this may be increasedby specifying a packet size (in bytes) after the destination hostname..PpOther options are:.Bl -tag -width Ds.It Fl m Ar max_ttlSet the max time-to-live (max number of hops) used in outgoing probepackets.  The default is 30 hops (the same default used for.Tn TCPconnections)..It Fl nPrint hop addresses numerically rather than symbolically and numerically(saves a nameserver address-to-name lookup for each gateway found on thepath)..It Fl p Ar portSet the base.Tn UDP.Ar portnumber used in probes (default is 33434)..Nm Traceroutehopes that nothing is listening on.Tn UDPports.Em baseto.Em base+nhops-1at the destination host (so an.Tn ICMP.Dv PORT_UNREACHABLEmessage willbe returned to terminate the route tracing).  If something islistening on a port in the default range, this option can be usedto pick an unused port range..It Fl q Ar nqueriesSet the number of probes per ``ttl'' to.Ar nqueries(default is three probes)..It Fl rBypass the normal routing tables and send directly to a host on an attachednetwork.If the host is not on a directly-attached network,an error is returned.This option can be used to ping a local host through an interfacethat has no route through it (e.g., after the interface was dropped by.Xr routed 8 ) ..It Fl s Ar src_addrUse the following IP address(which must be given as an IP number, nota hostname) as the source address in outgoing probe packets.  Onhosts with more than one IP address, this option can be used toforce the source address to be something other than the IP addressof the interface the probe packet is sent on.  If the IP addressis not one of this machine's interface addresses, an error isreturned and nothing is sent..It Fl t Ar tosSet the.Em type-of-servicein probe packets to the following value (default zero).  The value must bea decimal integer in the range 0 to 255.  This option can be used tosee if different types-of-service result in different paths.  (If youare not running a.Bx 4.3 tahoeor later system, this may be academic since the normal networkservices like telnet and ftp don't let you control the.Dv TOS ) .Not all values of.Dv TOSare legal ormeaningful \- see the IP spec for definitions.  Useful values areprobably.Ql \-t 16(low delay) and.Ql \-t 8(high throughput)..It Fl vVerbose output.  Received.Tn ICMPpackets other than.Dv TIME_EXCEEDEDand.Dv UNREACHABLE Ns sare listed..It Fl wSet the time (in seconds) to wait for a response to a probe (default 3sec.)..El.PpThis program attempts to trace the route an IP packet would follow to someinternet host by launching.Tn UDPprobepackets with a small ttl (time to live) then listening for an.Tn ICMP"time exceeded" reply from a gateway.  We start our probeswith a ttl of one and increase by one until we get an.Tn ICMP"port unreachable"(which means we got to "host") or hit a max (whichdefaults to 30 hops & can be changed with the.Fl mflag).  Threeprobes (changed with.Fl qflag) are sent at each ttl setting and aline is printed showing the ttl, address of the gateway andround trip time of each probe.  If the probe answers come fromdifferent gateways, the address of each responding system willbe printed.  If there is no response within a 3 sec. timeoutinterval (changed with the.Fl wflag), a "*" is printed for thatprobe..PpWe don't want the destinationhost to process the.Tn UDPprobe packets so the destination port is set to anunlikely value (if some clod on the destination is using thatvalue, it can be changed with the.Fl pflag)..PpA sample use and output might be:.Bd -literal[yak 71]% traceroute nis.nsf.net.traceroute to nis.nsf.net (35.1.1.48), 30 hops max, 56 byte packet1  helios.ee.lbl.gov (128.3.112.1)  19 ms  19 ms  0 ms2  lilac-dmc.Berkeley.EDU (128.32.216.1)  39 ms  39 ms  19 ms3  lilac-dmc.Berkeley.EDU (128.32.216.1)  39 ms  39 ms  19 ms4  ccngw-ner-cc.Berkeley.EDU (128.32.136.23)  39 ms  40 ms  39 ms5  ccn-nerif22.Berkeley.EDU (128.32.168.22)  39 ms  39 ms  39 ms6  128.32.197.4 (128.32.197.4)  40 ms  59 ms  59 ms7  131.119.2.5 (131.119.2.5)  59 ms  59 ms  59 ms8  129.140.70.13 (129.140.70.13)  99 ms  99 ms  80 ms9  129.140.71.6 (129.140.71.6)  139 ms  239 ms  319 ms10  129.140.81.7 (129.140.81.7)  220 ms  199 ms  199 ms11  nic.merit.edu (35.1.1.48)  239 ms  239 ms  239 ms.EdNote that lines 2 & 3 are the same.  This is due to a buggykernel on the 2nd hop system \- lbl-csam.arpa \- that forwardspackets with a zero ttl (a bug in the distributed versionof 4.3.Tn BSD ) .Note that you have to guess what paththe packets are taking cross-country since the.Tn NSFNet(129.140)doesn't supply address-to-name translations for its.Tn NSS Ns es ..PpA more interesting example is:.Bd -literal[yak 72]% traceroute allspice.lcs.mit.edu.traceroute to allspice.lcs.mit.edu (18.26.0.115), 30 hops max1  helios.ee.lbl.gov (128.3.112.1)  0 ms  0 ms  0 ms2  lilac-dmc.Berkeley.EDU (128.32.216.1)  19 ms  19 ms  19 ms3  lilac-dmc.Berkeley.EDU (128.32.216.1)  39 ms  19 ms  19 ms4  ccngw-ner-cc.Berkeley.EDU (128.32.136.23)  19 ms  39 ms  39 ms5  ccn-nerif22.Berkeley.EDU (128.32.168.22)  20 ms  39 ms  39 ms6  128.32.197.4 (128.32.197.4)  59 ms  119 ms  39 ms7  131.119.2.5 (131.119.2.5)  59 ms  59 ms  39 ms8  129.140.70.13 (129.140.70.13)  80 ms  79 ms  99 ms9  129.140.71.6 (129.140.71.6)  139 ms  139 ms  159 ms10  129.140.81.7 (129.140.81.7)  199 ms  180 ms  300 ms11  129.140.72.17 (129.140.72.17)  300 ms  239 ms  239 ms12  * * *13  128.121.54.72 (128.121.54.72)  259 ms  499 ms  279 ms14  * * *15  * * *16  * * *17  * * *18  ALLSPICE.LCS.MIT.EDU (18.26.0.115)  339 ms  279 ms  279 ms.EdNote that the gateways 12, 14, 15, 16 & 17 hops awayeither don't send.Tn ICMP"time exceeded" messages or send themwith a ttl too small to reach us.  14 \- 17 are running the.Tn MITC Gateway code that doesn't send "time exceeded"s.  Godonly knows what's going on with 12..PpThe silent gateway 12 in the above may be the result of a bug inthe 4.[23].Tn BSDnetwork code (and its derivatives):  4.x (x <= 3)sends an unreachable message using whatever ttl remains in theoriginal datagram.  Since, for gateways, the remaining ttl iszero, the.Tn ICMP"time exceeded" is guaranteed to not make it backto us.  The behavior of this bug is slightly more interestingwhen it appears on the destination system:.Bd -literal1  helios.ee.lbl.gov (128.3.112.1)  0 ms  0 ms  0 ms2  lilac-dmc.Berkeley.EDU (128.32.216.1)  39 ms  19 ms  39 ms3  lilac-dmc.Berkeley.EDU (128.32.216.1)  19 ms  39 ms  19 ms4  ccngw-ner-cc.Berkeley.EDU (128.32.136.23)  39 ms  40 ms  19 ms5  ccn-nerif35.Berkeley.EDU (128.32.168.35)  39 ms  39 ms  39 ms6  csgw.Berkeley.EDU (128.32.133.254)  39 ms  59 ms  39 ms7  * * *8  * * *9  * * *10  * * *11  * * *12  * * *13  rip.Berkeley.EDU (128.32.131.22)  59 ms !  39 ms !  39 ms !.EdNotice that there are 12 "gateways" (13 is the finaldestination) and exactly the last half of them are "missing".What's really happening is that rip (a Sun-3 running Sun OS3.5)is using the ttl from our arriving datagram as the ttl in its.Tn ICMPreply.  So, the reply will time out on the return path(with no notice sent to anyone since.Tn ICMP'saren't sent for.Tn ICMP's )until we probe with a ttl that's at least twice the pathlength.  I.e., rip is really only 7 hops away.  A reply thatreturns with a ttl of 1 is a clue this problem exists..Nm Tracerouteprints a "!" after the time if the ttl is <= 1.Since vendors ship a lot of obsolete.Pf ( Tn DEC Ns \'sUltrix, Sun 3.x) ornon-standard.Pq Tn HPUXsoftware, expect to see this problemfrequently and/or take care picking the target host of yourprobes.Other possible annotations after the time are.Sy !H ,.Sy !N ,.Sy !P(got a host, network or protocol unreachable, respectively),.Sy !Sor.Sy !F(source route failed or fragmentation needed \- neither of these shouldever occur and the associated gateway is busted if you see one).  Ifalmost all the probes result in some kind of unreachable,.Nm traceroutewill give up and exit..PpThis program is intended for use in network testing, measurementand management.It should be used primarily for manual fault isolation.Because of the load it could impose on the network, it is unwise to use.Nm tracerouteduring normal operations or from automated scripts..Sh AUTHORImplemented by Van Jacobson from a suggestion by Steve Deering.  Debuggedby a cast of thousands with particularly cogent suggestions or fixes fromC. Philip Wood, Tim Seaver and Ken Adelman..Sh SEE ALSO.Xr netstat 1 ,.Xr ping 8.Sh HISTORYThe.Nmcommand.Bt

⌨️ 快捷键说明

复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?