Re: [tcptra-dev] tcptraceroute test suite

["Michael C. Toren" <mct@toren.net>]

> >Oops, you're right.  This one-line fix should correct the problem:
> 
> That worked fine.. weird thing that it worked under Linux. I could not
> find the perldocs for sockaddr_in, I guess you did. :-)

The perl function is provided by the Socket.pm module, which is why
something like "perldoc -f" isn't very helpful in this case.

> This result is the same with 1.4 and 1.5beta3. Everythings looks ok 
> except for the last line. As far as I know Solaris does not have a 
> device in /dev for loopback (and if it did, it would be called /dev/lo 
> not /dev/lo0).
> 
> > It might also be interesting to see if the error is also present with
> > libnet-1.1.x.
> 
> Now with libnet 1.1.1 (1.1.0 does not work on Solaris):
>
[..]
>
> I don't see how this is a libnet problem. tcptraceroute does:

I had a (perhaps irrational) hope that libnet-1.1.x might solve the
problem, only because I happened to notice that the changelog entry for
libnet-1.1.1 mentions improved loopback support.  Oh, well; thanks for
trying.

> device here is /dev/lo0 ... I am not sure if this is a pcap issue or 
> that we need to be smarter about which device to use for localhost on 
> Solaris.

That very well could be, and should be easy enough to determine.  The
debugging output you pasted earlier revealed that three interfaces were
found in addition to the loopback:

> debug: Discovered interface lo0 with address 127.0.0.1
> debug: Discovered interface eri0 with address 192.168.0.2
> debug: Discovered interface hme0 with address 0.0.0.0
> debug: Discovered interface sppp0 with address 62.234.101.241

Are you able to successfully traceroute to either 127.0.0.1 or
62.234.101.241 if you specify the device to use by hand?

	tcptraceroute -d --no-filter -i eri0 62.234.101.241
	tcptraceroute -d --no-filter -i hme0 62.234.101.241
	tcptraceroute -d --no-filter -i sppp0 62.234.101.241

	tcptraceroute -d --no-filter -i eri0 127.0.0.1
	tcptraceroute -d --no-filter -i hme0 127.0.0.1
	tcptraceroute -d --no-filter -i sppp0 127.0.0.1

Another test to help determine if it's a libpcap problem might be to
see if tcpdump can attach to the loopback interface.  Something like:

	tcpdump -n -i lo0

Thanks,
-mct
_______________________________________________
tcptraceroute-dev mailing list
tcptraceroute-dev@netisland.net
https://lists.netisland.net/mailman/listinfo/tcptraceroute-dev