Michael C. Toren on Mon, 26 May 2003 04:58:05 -0400

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

Re: [tcptra-dev] tcptraceroute-1.5beta1

> I used --no-select and found better results for and
> Side-by-side results follow:
>     $ sudo ./tcptraceroute --no-select
>     Selected device lo0, address, port 49518 for outgoing packets
>     Tracing the path to on TCP port 80 (http), 30 hops max
>      1  localhost ( [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?


> Here's the non-local case too w/ and w/o --no-select:
>     $ 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

Hmm.  Earlier you included a traceroute to, 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
	tcptraceroute -q1 -d
	tcptraceroute -q3 -f30 -d toren.net
	traceroute toren.net
	telnet toren.net 4242

tcptraceroute-dev mailing list