Hi everybody,

I recently changes my router, and after confguring it properly, everything seems to work normally except ktorrent.

I did set up port forwarding for ports 6881-6889 TCP+UDP, as well as port 4444 UDP. Everythig else seems to work OK (instant messenger, web server, etc.).

The strange thing is that I can download torrents using btdownloadcurses. Ktorrent is 2.2.2, kernel 2.6.22. I tried to delete the whole config (ktorrentrc) and start a download from scratch, but it did not change anything.

Seeders and leechers are detected but I get no connection with them (looks like: 0 (140) in the seeders row in the GUI). I can also successfully update or change trackers.

I have absolutely no idea where to look now, and what could cause this strange behaviour. Would somebody have a clue about this?

Thank you,

Eric

Edit: I noticed some other strange stuff:
- the btdownloadcurses download stopped after 16MB
- loading web pages is sometimes difficult (need to refresh 1 or 2 times before I get it completely, but when it's working they get loaded quite fast)

So it seems I could have a problem with my connection rather than with ktorrent. I need to check everything, if someone here has a clue I'd be glad to hear it, otherwise I'm going to look in a more appropriate place.

Also, here a part of the logs:

Initiating connection to xx.xx.xx.xx
Timeout occurred
Authentication to xxx.xxx.xx.xx : failure

[repeated lots of times]

Initiating connection to xx.xx.xxx.xx
DHT: Sending ping response
Timeout occurred
Authentication to xxx.xxx.xxx.xx : failure
Initiating connection to xx.xx.xx.xx1
Stalled for too long, time to get some fresh blood
DHT: Doing announce
Doing tracker request to url : http://tracker.xxxxxxxxxxxxxxxxxxxxx
DHT: Got 18 potential peers for torrent xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Doing scrape request to url : http://tracker.xxxxxxxxxxxxxxxxxxxxxxxx ... xxxxxxxxxx
Authentication(S) to xx.xxx.xx.xxx : ok
Starting socketmonitor threads
Stalled for too long, time to get some fresh blood
DHT: Doing announce

[repeated a few times]

DHT: Doing announce
Announce ongoing, queueing announce
DHT: Got 3 potential peers for torrent xxxxxxxxxxxxx
DHT: Got 16 potential peers for torrent xxxxxxxxxxxxx
DHT: Got 11 potential peers for torrent xxxxxxxxxxxx
DHT: Got 12 potential peers for torrent xxxxxxxxxxxxxxxxxxx
DHT: Got 7 potential peers for torrent xxxxxxxxxxxxxxxx
Doing scrape request to url : http://xxxxxxxxxxxx
Authentication(S) to xx.x.xxx.xx : ok
Initiating connection to xxx.xxx.xxx.xx

[lots of connections initiated]

DHT: Got 29 potential peers for torrent xxxxxxxxxxx
Doing scrape request to url : http://zzzzzzzzzzzzzzz
DHT: Sending ping response
DHT: Got 11 potential peers for torrent zzzzzzzzzzzz
Scrape : leechers = 19, seeders = 5
DHT: Got 15 potential peers for torrent xxxxxxxxxxxx
Scrape : leechers = 27, seeders = 37
DHT: Got 1 potential peers for torrent xxxxxxxxxxxxxxx

[...]

DHT: Got 11 potential peers for torrent xxxxxxxxx
DHT: Got 16 potential peers for torrent xxxxxxxxxx
DHT: AnnounceTask done
Authentication(S) to zz.zz.zzz.zz : ok
Sending ping request to zz.zz.zzz.zz:45004
Stalled for too long, time to get some fresh blood
DHT: Doing announce
Doing tracker request to url : http://zzzzzzzzzzz

DHT: Got 2 potential peers for xxxx
DHT: Got 22 potential peers for xxxx
[...]
Timeout occurred
Authentication to xx.xx.xx.xx : failure
Initiating connection to xx.xx.xx.xx
Scrape : leechers = 64, seeders = 15
Timeout occurred
Authentication to xx.xx.xxx.xx : failure
Authentication to xx.xx.xx.xx : failure
Timeout occurred
Authentication to xx.xxx.xxx.xx : failure
Timeout occurred
Authentication to xx.xx.xxx.xx : failure
Timeout occurred
Authentication to xx.xxx.xx.xx : failure

[repeated lots of times...]

OK, I fixed this. The router was a D-Link DSL-G664T with a very old firmware. I upgraded the FW and now everything is working perfect. I have no idea what was wrong with the old one.