Date: Tue, 11 Mar 2008 07:23:49 +0100 (CET) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Patrick Mahan <mahan@mahan.org> Cc: Zbigniew Szalbot <zszalbot@gmail.com>, freebsd-questions <freebsd-questions@freebsd.org>, Jonathan Chen <jonc@chen.org.nz> Subject: Re: traceroute problems Message-ID: <20080311072300.K2678@wojtek.tensor.gdynia.pl> In-Reply-To: <47D5F4B5.1030309@mahan.org> 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> <47D5F4B5.1030309@mahan.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. > many commercial firewalls, including those in integrated devices, tend to block everything excluding often used services. some even block ICMP ping.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080311072300.K2678>