Michael C. Toren on Mon, 26 May 2003 14:50:29 -0400

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [tcptra-dev] tcptraceroute-1.5beta2 (was Re: [tcptra-dev] tcptraceroute-1.5beta1)

> ./tcptraceroute -q3 -f30 -d toren.net
> 30  www.toren.net ( [open]  64.092 ms

Okay, great -- so it looks like you're successfully able to use
tcptraceroute to trace the path to www.toren.net, a remote machine
accessible via your ethernet interface.  In an earlier message,
you included the following traceroute:

> $ sudo ./tcptraceroute --no-select
> Selected device en0, address, port 49529 for outgoing packets
> Tracing the path to on TCP port 80 (http), 30 hops max
>  1  * * *
> ^C

I'm wondering if perhaps the first hop, your Linksys device, isn't
generating ICMP time-exceeded messages?  Can you please try running
"tcptraceroute toren.net", and letting it run for the full 30 hops?

tcptraceroute-dev mailing list