[93116] in North American Network Operators' Group
Re: Extreme Slowness
daemon@ATHENA.MIT.EDU (Jeremy Chadwick)
Thu Oct 26 19:56:49 2006
Date: Thu, 26 Oct 2006 16:55:55 -0700
From: Jeremy Chadwick <nanog@jdc.parodius.com>
To: nanog@merit.edu
Mail-Followup-To: nanog@merit.edu
In-Reply-To: <CE3DA2DD-7BDA-42B4-80A9-FF2814532147@digitalrage.org>
Errors-To: owner-nanog@merit.edu
On Thu, Oct 26, 2006 at 06:01:43PM -0400, Elijah Savage wrote:
> For FYI :) I realize that ICMP is not the best way to test and it is
> not a true indication of slowness or the presence of a problem.
Which begs the same question I've asked in the recent past: then
what *is* a good diagnostic tool? If ICMP "is not the best way to
test", then what is? What other globally-implemented layer 3 or
below protocols do we have available for troubleshooting?
Sure, UDP-based traceroute still relies on ICMP TTL exceeded
responses to work. I've no idea what TCP traceroute relies on,
as I haven't looked at it.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
