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