Just from curiosity....
Anyone have any insights on what causes the following interesting data from a traceroute? 10 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 39 ms 36 ms 38 ms 11 * cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * 12 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 38 ms * * 13 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 41 ms * * 14 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 194 ms * * 15 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * * 16 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * 37 ms 17 * cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 37 ms * 18 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 37 ms * 35 ms
You see this behavior because your traceroute program does not understand the ICMP "administratively prohibited" (ICMP type 3, code 13 - defined in RFC 1812) messages being sent back to it from cpe1.reston.mci.net. Cisco routers typically return ICMP messages of this nature to the source of traffic which is being blocked by a traffic-filtering ACL on the Cisco router. - roy - ------------------------------------------------------------------------- | roy alcala | MCI | | IP Development | 2100 Reston Parkway | | roy@mci.net | Reston, Virginia 22091 | | beep-roy@mci.net (pager) | (703) 715-7425 | | (800) SKY-PAGE PIN 1633689 | (703) 715-7066 FAX | -------------------------------------------------------------------------
Anyone have any insights on what causes the following interesting data from a traceroute?
10 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 39 ms 36 ms 38 ms 11 * cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * 12 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 38 ms * * 13 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 41 ms * * 14 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 194 ms * * 15 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * * 16 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * 37 ms 17 * cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 37 ms * 18 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 37 ms * 35 ms
ftp://ftp.aces.com/software/traceroute/traceroute_new.c ftp://ftp.aces.com/software/traceroute/0_readme.txt This BETA version incorporates two new changes: 1: It will show a !A for administratively-prohibited packets (see below) 2: It will allow modification of a line terminator from standard <LF> to anything else, allowing, for instance, dynamic access from web browsers (see www.opus1.com/www/traceroute.html) Feel free to test. Ehud
You see this behavior because your traceroute program does not understand the ICMP "administratively prohibited" (ICMP type 3, code 13 - defined in RFC 1812) messages being sent back to it from cpe1.reston.mci.net.
Cisco routers typically return ICMP messages of this nature to the source of traffic which is being blocked by a traffic-filtering ACL on the Cisco router.
- roy -
------------------------------------------------------------------------- | roy alcala | MCI | | IP Development | 2100 Reston Parkway | | roy@mci.net | Reston, Virginia 22091 | | beep-roy@mci.net (pager) | (703) 715-7425 | | (800) SKY-PAGE PIN 1633689 | (703) 715-7066 FAX | -------------------------------------------------------------------------
Anyone have any insights on what causes the following interesting data from a traceroute?
10 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 39 ms 36 ms 38 ms 11 * cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * 12 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 38 ms * * 13 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 41 ms * * 14 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 194 ms * * 15 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * * 16 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * 37 ms 17 * cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 37 ms * 18 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 37 ms * 35 ms
ftp://ftp.aces.com/software/traceroute/traceroute_new.c ftp://ftp.aces.com/software/traceroute/0_readme.txt
It is somewhat unfortuante that there are lots of versions about, and development seems to be proceeding with multiple variants. [oh well] There are at least 3 that I know of. Yours, LBL traceroute (the original), and Eric Wassenaar's traceroute. LBL traceroute is available from ftp.ee.lbl.gov as traeroute.tar.Z; notably it recently added support for sending ICMP problems (marching through firewalls), and it does recognize ICMP administratively unreachable packets. For some time LBL had not released any new versions, but began doing so again at the tail end of 1995. Eric Wassenaar's traceroute is available from ftp.nikhef.nl as /pub/network/traceroute.tar.Z, and is billed as having these features: o Optional ttl reporting. o Optional use of the loose source routing facility, to show the route between arbitrary destinations. o Enhanced portability, to run on a variety of platforms. o Improved timeout handling during icmp packet catching. o Option to probe all addresses of multi-homed destinations. o Option to disable fragmentation and perform MTU discovery. o Recognize various new icmp packet types. o Round-trip time reporting in fractional milliseconds. o Option to display the Autonomous System number for each hop. o Option to display the network name for each hop. o Configurable default options via environment variables. o Optional setting of initial ttl to skip first hops. o Optional min/avg/max rtt statistics summary for each hop. o Include standard deviation in rtt statistics summary. o Cache nameserver lookups to minimize DNS queries. I apologize for this foray into something that people might possibly consider useful on this mailing list; please return to the regularly scheduled drivel. --jhawk
It is somewhat unfortuante that there are lots of versions about, and development seems to be proceeding with multiple variants. [oh well]
There are at least 3 that I know of. Yours, LBL traceroute (the original), and Eric Wassenaar's traceroute.
Then maybe there would be interest in converging to one version? I sure would like to see just one version - I've put off installing a new version of traceroute a couple of times since I could not figure out which one to put up. --asp@partan.com (Andrew Partan)
filtering. what was the first part of the tracereoute. Jeff Young young@mci.net
Return-Path: owner-nanog@merit.edu Received: from merit.edu (merit.edu [35.1.1.42]) by postoffice.Reston.mci.net (8.7.5/8.7.3) with ESMTP id RAA15631; Fri, 17 Jan 1997 17:35:33 -0500 (EST) Received: from localhost (daemon@localhost) by merit.edu (8.8.4/merit-2.0) with SMTP id RAA08085; Fri, 17 Jan 1997 17:31:23 -0500 (EST) Received: by merit.edu (bulk_mailer v1.5); Fri, 17 Jan 1997 17:29:00 -0500 Received: (from daemon@localhost) by merit.edu (8.8.4/merit-2.0) id RAA08021 for nanog-outgoing; Fri, 17 Jan 1997 17:28:59 -0500 (EST) Received: from news.acrux.net (pluto.acrux.net [207.51.199.3]) by merit.edu (8.8.4/merit-2.0) with ESMTP id RAA08012 for <nanog@merit.edu>; Fri, 17 Jan 1997 17:28:55 -0500 (EST) Received: from pluto (pluto [207.51.199.3]) by news.acrux.net (8.8.3/8.8.3) with SMTP id QAA21288; Fri, 17 Jan 1997 16:26:47 -0600 (CST) Date: Fri, 17 Jan 1997 16:26:46 -0600 (CST) From: Brian Tackett <cym@acrux.net> X-Sender: cym@pluto To: nanog@merit.edu cc: Rob Barron <rbarron@acrux.net> Subject: Just from curiosity.... In-Reply-To: <199701172000.MAA26538@lovefm.cisco.com> Message-ID: <Pine.GSO.3.93.970117162448.21258A-100000@pluto> MIME-Version: 1.0 Sender: owner-nanog@merit.edu Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Length: 657
Anyone have any insights on what causes the following interesting data from a traceroute?
10 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 39 ms 36 ms 38 ms 11 * cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * 12 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 38 ms * * 13 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 41 ms * * 14 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 194 ms * * 15 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * * 16 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 36 ms * 37 ms 17 * cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 37 ms * 18 cpe1-fddi4-0.Reston.mci.net (204.70.176.102) 37 ms * 35 ms
participants (6)
-
Andrew Partan -
Brian Tackett -
Ehud Gavron -
Jeff Young -
John Hawkinson -
roy alcala