Hi there!

Recently I noticed that whenever there were only 2 peers including myself, and the other one was non-clever (can't accept incoming connections), the torrent NEVER moved. This struck me as odd as I've verified through various methods that I CAN accept incoming connections, meaning the other peer should be able to at least connect to me. Then I noticed the following pattern in the log:

Authentication(S) to xxx.xxx.xxx.xxx : ok
Connection closed

There were no exceptions to ths pattern. Every incoming connection was closed immediately after being opened (I checked hundreds of examples). Turning off encryption fixed the problem right away. It seems that every client doesn't recognise the encrypted header and immediately closes the connection.

version 2.0.3


PS: Most web tools I tried to test NAT setups did not test past making a connection. This one is an exception: http://btfaq.com/natcheck.pl . It did not recognise the encrypted header, but I couldn't be sure if it just lacks an implementation.

... It would be handy to have a simple CLI debugging client which I could use to connect to my ktorrent client from a remote host to test whether it's sending appropriate headers. Does anyone know of such a tool?

PPS: I did have the 'Allow unencrypted connections' option CHECKED! :)

When encryption is enabled, we try encrypted first and if that fails we try again unencrypted. But I better do some tests on this. Maybe there is a bug in there.