|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
Re: [tcptra-dev] tcptraceroute-1.5beta1
|
Michael,
I just received your message and have not tried v1.5 beta2. I will do so shortly.
I thought it would be prudent to forward a few comments from Jerry Talkington.
He has tcptraceroute v1.4 working on MacOS X. He used the -DHASSALEN as a
compilation option. If you would like me to try anything related to this then
just let me know.
--Joel
--- forwarded message ---
From: Jerry Talkington <jtalkington@users.sourceforge.net>
To: "Joel L. Breazeale" <jlb@visi.com>
Subject: Re: [tcptra-dev] tcptraceroute-1.5beta1
I haven't tried that version yet, but I just got the 1.4 version working
by specifying -DHASSALEN on the command line. I'm having the same
problem, though, even when I try to access machines inside my
firewall...
You may want to try asking the tcptraceroute development mailing list.
--- end forwarded message ---
> > 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
>
_______________________________________________
tcptraceroute-dev mailing list
tcptraceroute-dev@netisland.net
https://lists.netisland.net/mailman/listinfo/tcptraceroute-dev
|
|