From: John Beckett 

Randall Parker > [randall{at}localhost ~]$ traceroute 4.2.2.2
> traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 40 byte packets
>   1  FVG318 (192.168.1.46)  2.428 ms   4.222 ms   9.874 ms
>   2  dslrouter (192.168.1.1)  28.859 ms   27.330 ms   35.229 ms
>   3  * * *
>   4  * * *
>   5  * * *
>   6  * * *
>   7  * * *
>   8  * * *
>   9  * * *
> 10  * * *
> 11  * * *
> 12  vnsc-bak.sys.gtei.net (4.2.2.2)  77.477 ms   72.217 ms   62.809 ms
> [randall{at}localhost ~]$

Interesting. Since you are enjoying all this hardcore command stuff so much
, try the following to send ICMP Echo request packets (like
Windows does), instead of sending UDP packets to non-existent ports (-I is
an uppercase i):

traceroute -I -n 4.2.2.2

With no -I, Linux is sending out UDP packets to a high port (33434 for the
first hop, incremented for each next hop). With -I, it is sending an ICMP
packet with "echo request" type.

For both -I and no -I, you should be getting ICMP error packets back.

Your display is certainly possible, although rather unlikely. On face
value, it says that:
- The first two routers responded with an ICMP time exceeded.
- Routers 3 to 11 are configured to NOT respond in this way.
- The target (4.2.2.2) responded with an ICMP port unreachable message.

Another (far fetched) possibility is that your firewall blocks the port
numbers that were used for routers 3 to 11, but not the port numbers for
the successful packets (the ports increment for each hop).

The "dslrouter (192.168.1.1)" makes sense, but I wonder what
"FVG318 (192.168.1.46)" is.

--- BBBS/NT v4.01 Flag-5