I'd say there was an access-list or firewall blocking ICMP-echo replies, but
not TTL expired messages.
This is a guess. This is only a guess. In the event of a real answer, the
statements just typed would have been followed by supporting documentation.
Ejay Hire
-----Original Message-----
From: Watson, Rick, CTR, OUSDC [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 21, 2001 11:53 AM
To: [EMAIL PROTECTED]
Subject: Re: Weird trace results [7:5259]
All,
When performing a trace on an IP address (for "testing purposes we'll use
10.1.2.3) this is the result I get:
router#trace 10.1.2.3
Type escape sequence to abort.
Tracing the route to 10.1.2.3
1 192.1.2.2 4 msec
192.1.2.10 4 msec
192.1.2.2 4 msec
2 10.1.2.3 0 msec 4 msec 4 msec
3 * * *
4 * * *
5 * * *
6 * * *
This to me shows that I am still trying to find a path to the IP
address...but if the IP Address is returned at the 2nd hop, why is the trace
still continuing? I thought that it would stop when the trace has the
"path". Also note that when a "ping" is performed it returns the infamous
"....."
This has really got me perplexed, and any help would be greatly appreciated.
Maybe I am just not understanding something about the trace command/ICMP.
Rick Watson
Network Engineer
Advanced Systems Development, Inc.
OUSD(Comptroller)
703.697.5710 office
800.309.7782 pager ([EMAIL PROTECTED])
[EMAIL PROTECTED]
FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=5292&t=5259
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
