Alexander W. Janssen
alexander.janssen at gmail.com
Wed Jan 2 13:23:49 UTC 2008
-----BEGIN PGP SIGNED MESSAGE-----
Hans Schnehl wrote:
> Jan 02 12:46:06.204 [debug] TLS error: <syscall error while reading>
> (errno=54: Connection reset by peer) Jan 02 12:46:06.204 [info]
> connection_read_to_buf(): tls error [connection reset]. breaking
> (nickname NoNickNode, address 22.214.171.124).
It looks like one of the nodes you have a connection too just kicked you
out for some reason ("connection reset by peer"). This is pretty normal.
Could be the remote node shutting down the software, rebooting and such.
> Jan 02 12:46:14.711 [debug] crypto error while performing RSA
> decryption: oaep decoding error (in rsa
Not sure about those, but it could be consecutive errors resulting from
the encrypted connection (TLS) being shut down.
> Tor is running, but appears to be using only fractions of the
> bandwidth it is supposed to. Can someone please give a short
No idea about that though. But it usually takes some time until everyone
learned about your node - from my experience it takes up to 24 hours
until the bandwidth is fully utilized.
I'm just guessing from my generic experience :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
-----END PGP SIGNATURE-----
More information about the tor-talk