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

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