Date: Mon, 10 Mar 2008 19:55:49 -0700 From: Patrick Mahan <mahan@mahan.org> To: Jonathan Chen <jonc@chen.org.nz> Cc: Zbigniew Szalbot <zszalbot@gmail.com>, Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>, freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: traceroute problems Message-ID: <47D5F4B5.1030309@mahan.org> In-Reply-To: <20080311023822.GA55240@osiris.chen.org.nz> References: <94136a2c0803101454l6ca76c99ma1fa1083d7ea2137@mail.gmail.com> <20080310231502.V7454@wojtek.tensor.gdynia.pl> <94136a2c0803101520p4f044ce4lae76975f899296e7@mail.gmail.com> <20080310232639.K7504@wojtek.tensor.gdynia.pl> <20080311023822.GA55240@osiris.chen.org.nz>
next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan Chen presented these words - circa 3/10/08 7:38 PM-> > On Mon, Mar 10, 2008 at 11:30:05PM +0100, Wojciech Puchar wrote: > > [...] >> traceroute uses UDP packets, no special port numbers. > > traceroute(8) indicates that the default UDP port number used is > udp/33434, incrementing for each hop out. The incrementing is the TTL count in the IP header, not the port number. It works by sending out a UDP packet for a (generally) unused port with the TTL field to a specific number and looking for ICMP errors to indicate how far the packet went (the last node address is contained in the ICMP error reply). However, be warned, some network administrators disable their routers from sending back these types of ICMP messages to prevent you from learning about their routing paths. In these cases, you get back the "1 * * *" type of output from traceroute. Also, by default traceroute attempts to do a reverse DNS on the IP address, so you can speed things up by doing a 'traceroute -n' to avoid this look-up. Patrick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47D5F4B5.1030309>