I seem to recall someone doing a paper on
ICMP and traceroute -at times-, as not always being indicative of
actual network performance...
Does anyone remember who, or where,
that link is ?
Thanks in Advance.
I seem to recall someone doing a paper on
ICMP and traceroute -at times-, as not always being indicative of
actual network performance...
Does anyone remember who, or where,
that link is ?
Thanks in Advance.
John Starta wrote:
If you locate this, please forward the link along.
I haven't found the original, it was dated about
97-99... NLANR, perhaps ???
But, there are more recent write ups...
Here are two I encountered:
<http://www.inetdaemon.com/tools/ping_is_not.html>
This one explains why PING -may- be bad, but regular
performance, OK...
(Call it the end user explanation of ACL-CAR intervention)
:)
And this one,( more what I was looking for..)
a detailed explanation of the caveats of clever
tracerouting providing Bogus Data.
<http://homepage.ntlworld.com/robin.d.h.walker/cmtips/traceroute.html>
I needed something for a rookie tech who was "whining"
about a site tracerouting with an intervening router
- appearing - slow (An exchange BGP router, go figure),
but an end to end of -38 ms-, -consistent- and with -no- loss.
He didn't believe the explanation of the BGP rumble...
and I was growing frustrated with the need for detail,
when it just wasn't registering !
:(
"When the Judge is a blind man, it can be -exasperating-
trying defend your choice of the Winner of the Art fair."
:P
Richard Irving wrote:
...Oooops...
"When the Judge is a blind man, it can be -exasperating-
trying _to_ defend your choice of the Winner of the Art fair."
:P
And to that I add the Maxim:
"The probability of a Typo is in inverse proportion of
the time spent composing, and in direct proportion
to the level of frustration inherent in the author."
:D