| Joel L. Breazeale on Mon, 26 May 2003 15:01:05 -0400 |
|
Michael,
Just to be sure you have this straight... The model of LinkSys
router/firewall is BEFSX41.
Here's the output you want to see:
# ./tcptraceroute toren.net
Selected device en0, address 192.168.1.200, port 49223 for outgoing packets
Tracing the path to toren.net (207.8.132.197) on TCP port 80 (http), 30 hops max
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 www.toren.net (207.8.132.197) [open] 59.648 ms 60.121 ms 62.632 ms
#
[I'll give you the other set of output you want in a separate reply.]
--Joel
> > ./tcptraceroute -q3 -f30 -d toren.net
> [...]
> > 30 www.toren.net (207.8.132.197) [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 66.135.192.87
> > Selected device en0, address 192.168.1.200, port 49529 for outgoing packets
> > Tracing the path to 66.135.192.87 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?
>
> Thanks,
> -mct
> _______________________________________________
> tcptraceroute-dev mailing list
> tcptraceroute-dev@netisland.net
> https://lists.netisland.net/mailman/listinfo/tcptraceroute-dev
>
_______________________________________________
tcptraceroute-dev mailing list
tcptraceroute-dev@netisland.net
https://lists.netisland.net/mailman/listinfo/tcptraceroute-dev
|
|