FreeBSD 6.1 Tor issues (Once More, with Feeling)

[Fabian Keil]

Robert Watson <rwatson at FreeBSD.org> wrote:

> On Tue, 27 Jun 2006, Fabian Keil wrote:
> 
> > There was a "request" for Tor related problem reports a while ago,
> > I couldn't find the message again, but I believe it was posted here.
> 
> I'm very interested in tracking down this problem, but have had a lot
> of trouble getting reliable reports of problems -- i.e., ones where I
> could get any debugging information.  I had a similar conversation on
> these lines yeterday with Roger (Tor author) here at the WEIS
> conference.  If this is easily reproduceable, I would like you to do
> the following:
> 
> - Compile in options DDB, options KDB, options BREAK_TO_DEBUGGER,
> options WITNESS, options WITNESS_SKIPSPIN, options INVARIANTS, options
>    INVARIANT_SUPPORT.
> 
> - Make sure to have a kernel with debugging symbols for the kernel.
> 
> - Turn on core dumps.

Done. I expect to get a chance to test the settings in the next 24 hours.
 
> The above debugging options will have a significant performance
> impact, and may or may not affect the probability of the race or
> deadlock being exercised. The first question is:
> 
> - Are there any warnings on the console from WITNESS or other
> debugging options?  If so, please copy/paste them into an e-mail for
> me.

So far the logs show nothing unusual, but I
noticed that the ssh connection gets unresponsive
from time to time.

I did a few pings with "interesting" results:

[fk at tor ~]$ ping 10.0.0.1 | grep 'time=[^0]'
64 bytes from 10.0.0.1: icmp_seq=25 ttl=64 time=1.104 ms
64 bytes from 10.0.0.1: icmp_seq=61 ttl=64 time=2.983 ms
64 bytes from 10.0.0.1: icmp_seq=167 ttl=64 time=1.112 ms
64 bytes from 10.0.0.1: icmp_seq=189 ttl=64 time=1.653 ms
64 bytes from 10.0.0.1: icmp_seq=222 ttl=64 time=1.748 ms
64 bytes from 10.0.0.1: icmp_seq=291 ttl=64 time=1.058 ms
64 bytes from 10.0.0.1: icmp_seq=334 ttl=64 time=1.020 ms
64 bytes from 10.0.0.1: icmp_seq=337 ttl=64 time=1.967 ms
64 bytes from 10.0.0.1: icmp_seq=562 ttl=64 time=1.027 ms
64 bytes from 10.0.0.1: icmp_seq=586 ttl=64 time=1.230 ms
^C[fk at tor ~]$ ping tor.fabiankeil.de | grep 'time=[^0]'
64 bytes from 81.169.155.246: icmp_seq=70 ttl=64 time=1.920 ms
64 bytes from 81.169.155.246: icmp_seq=79 ttl=64 time=1.587 ms
64 bytes from 81.169.155.246: icmp_seq=402 ttl=64 time=1.062 ms
^C[fk at tor ~]$ ping localhost | grep 'time=[^0]'
64 bytes from 127.0.0.1: icmp_seq=142 ttl=64 time=1.142 ms
64 bytes from 127.0.0.1: icmp_seq=497 ttl=64 time=1.227 ms
64 bytes from 127.0.0.1: icmp_seq=627 ttl=64 time=1.181 ms

10.0.0.1 is on lo1, 81.169.155.246 is on fxp0, both
are filtered with pf. lo0 is skipped. The pings were run
locally while tor was running, the usual ping response times
are below 0.2 ms.

I get even more obscene ping times if I ping
from home, but my net connection isn't the best.
I'd appreciate if someone with a reliable net
connection could confirm the weirdness.

Thanks for your time, Robert, I hope to have real
information by tomorrow.

Fabian
-- 
http://www.fabiankeil.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060628/2b3720b7/signature.pgp