It's not used any more. It was originally defined in RFC 1393, "Traceroute Using an IP Option" (http://tools.ietf.org/html/rfc1393), but then it was deprecated in RFC 6814, "Formally Deprecating Some IPv4 Options" (http://tools.ietf.org/html/rfc6814).
The general consensus was that you should not send an ICMP message about an ICMP message. That's why most implementations use UDP or TCP outbound, and then expect the ICMP reply back in. Some implementations, like Windows, send ICMP out and expect ICMP back in, but they still don't use the actual "traceroute" ICMP type code for it.
HTH,
Brian McGahan, CCIE #8593 (R&S/SP/Security)
bmcgahan_at_INE.com
Internetwork Expert, Inc.
http://www.INE.com
-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Sarad
Sent: Wednesday, January 23, 2013 10:21 PM
To: groupstudy
Subject: ICMP ACL parameters
Hi Guys,
As per my understanding to allow traceroute through a ACL we need to allow icmp port-unreachable & icmp time-exceeded and udp 33400 34400 based on the ACL direction.
Can somebody enlighten me the usage of *traceroute* parameter in a icmp ACL
Cheers
Sara
Blogs and organic groups at http://www.ccie.net
Received on Thu Jan 24 2013 - 09:49:30 ART
This archive was generated by hypermail 2.2.0 : Sun Feb 03 2013 - 16:27:17 ART