Michael C. Toren on Mon, 26 May 2003 04:58:05 -0400 |
> I used --no-select and found better results for 127.0.0.1 and 24.163.210.43. > Side-by-side results follow: [..] > $ sudo ./tcptraceroute --no-select 127.0.0.1 > Selected device lo0, address 127.0.0.1, port 49518 for outgoing packets > Tracing the path to 127.0.0.1 on TCP port 80 (http), 30 hops max > 1 localhost (127.0.0.1) [open] 0.333 ms 0.244 ms 0.186 ms Okay, so it looks like --no-select should be the default on MacOS X. Based on the output of "gcc -E -dM - </dev/null" on your machine, it would seem that we can detect MacOS X systems by checking for the presence of __APPLE__ and __MACH__. I just patched the configure.ac file so that autoconf should now do just that, and make --no-select the compile-time default for MacOS X. Can you please confirm that it's no longer necessary to specify the --no-select command line argument by hand with tcptraceroute-1.5beta2? <http://michael.toren.net/code/tcptraceroute/tcptraceroute-1.5beta2.tar.gz> > Here's the non-local case too w/ and w/o --no-select: [..] > $ 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 Hmm. Earlier you included a traceroute to 24.163.210.43, which was one hop away. Is that the address of your local machine, or the address of a NAT device external to your MacOS X system? If it's an external NAT device, I wonder if it could be interfering with tcptraceroute. Can you please try executing the following commands, and sending back the output from each? tcptraceroute -q1 -d 127.0.0.1 tcptraceroute -q1 -d 24.163.210.43 tcptraceroute -q3 -f30 -d toren.net traceroute toren.net telnet toren.net 4242 Thanks, -mct _______________________________________________ tcptraceroute-dev mailing list tcptraceroute-dev@netisland.net https://lists.netisland.net/mailman/listinfo/tcptraceroute-dev
|
|