Hello!

KTorrent does not work at all for me.
All torrents I add have the status "Stalled" and do not start downloading.

The tracker is OK, and the status widget shows ~30 leechers and ~15 seeders (this is for a SuSE ISO CD download).
I am not connected to any peer, but from time to time to 1, but it still does not download anything.
I have 0 DHT nodes.

I am using KTorrent 2.0.3 (KDE 3.5.5) on Kubuntu 6.10.

The same torrent works fine with Azureus.

I am behind a router, but I forwarded the following ports:
6880-6999 UDP, TCP
4444 UDP, TCP
59861 UDP

The port settings in KTorrent are:
Port: 6881
UDP tacker port: 4444
UDP port for DHT communication: 6881

UPnP is disabled in KTorrent and on the router.

The firewall in Ubuntu is disabled. However, I don't think the ports are the problem.

I have tried older versions of KTorrent in the past, but they did not work either (even on a SuSE install).

Any idea what is going on and how I can resolve the problem?

Can you try using a port other than 6881? Some ISP's firewall it. Azureus typically doesn't use 6881 nowadays, either.

jdong wrote:Can you try using a port other than 6881? Some ISP's firewall it. Azureus typically doesn't use 6881 nowadays, either.

I set up Azureus to use port 6881, it works perfectly (Also the NAT/Firewall test in Azureus says "OK" for port 6881).
So this seems not to be an ISP problem.

Anyway, I tried with port 10000, same results.
Azureus works fine, KTorrent does not work at all.


I get a lot of log entries about parsing errors, timeouts and authentication failures, like this:

Error happened during parsing : Illegal token: ô
Error happened during parsing : Illegal token: Ô
Error happened during parsing : Illegal token:
Timeout occurred
Authentication to 194.146.250.12 : failure
Timeout occurred
Authentication to 60.212.71.63 : failure

I get about 1 parsing error per second. The authentication failures and timeouts then all happen at once.

You are getting some weird stuff back from the tracker, can you send me that torrent for testing ?

George wrote:You are getting some weird stuff back from the tracker, can you send me that torrent for testing ?

I've sent you the torrent by e-mail.

I also tested a bit more (several torrents) and noticed the following:

- I get very few parse errors (illegal token) now
- I now get a few of the following errors: Cannot find PeerManager for hash : [..]
- The only peers I have been ever able to connect to were BitComet peers. This however might be pure coincidence, as I was only connected to a peer 2 or 3 times (as I mentioned, I was not able to download anything from those peers).
- For every "Initiating connection to [..]", there is a matching "Authentication to [..] : failure", most of the time with a timeout, sometimes without.

As I said, it does not matter which torrent I try, the problems and symptoms are all the same.

tmg wrote:

George wrote:You are getting some weird stuff back from the tracker, can you send me that torrent for testing ?

I've sent you the torrent by e-mail.

Torrent seems to work fine in the current SVN version, it starts downloading at around 90 to 100 KB/s

I also tested a bit more (several torrents) and noticed the following:

- I get very few parse errors (illegal token) now

Don't see any of these in my log file. Bug is probably allready fixed in the SVN version.

- I now get a few of the following errors: Cannot find PeerManager for hash : [..]

Normal, a couple of peer connecting to you for a torrent you are no longer downloading.

- The only peers I have been ever able to connect to were BitComet peers. This however might be pure coincidence, as I was only connected to a peer 2 or 3 times (as I mentioned, I was not able to download anything from those peers).
- For every "Initiating connection to [..]", there is a matching "Authentication to [..] : failure", most of the time with a timeout, sometimes without.

As I said, it does not matter which torrent I try, the problems and symptoms are all the same.

So basically 99 % of your authentications fail for some reason. Seeing that there is practically no difference in the authentication code between 2.0.3 and the current SVN version, maybe this is a firewall issue ?

George wrote:So basically 99 % of your authentications fail for some reason. Seeing that there is practically no difference in the authentication code between 2.0.3 and the current SVN version, maybe this is a firewall issue ?

Yeah, but what could be the problem?
The ports are forwarded (see above), the firewall is off, Azureus works with the same ports.
This seems to be a KTorrent problem for me.

Is it somehow possibly to identify the causes of the authentication failures?