This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Giving up on KTorrent

Tags: None
(comma "," separated)
imported4-microchip
Registered Member
Posts
15
Karma
0

Giving up on KTorrent

Sat Sep 16, 2006 7:59 pm
Sorry guys but i'm giving up on KTorrent. Its DHT functionality is terribly broken that it never goes on on my SUSE 10.1 with KDE 3.5.4. I'm going back to Azureus, sorry George/Ivan
lucke
Registered Member
Posts
205
Karma
0

Sat Sep 16, 2006 8:34 pm
As one could read in some other topic, its DHT functionality is "terribly broken" on SUSE because it's disabled by SUSE devs.
imported4-microchip
Registered Member
Posts
15
Karma
0

Sat Sep 16, 2006 11:10 pm
lucke wrote:As one could read in some other topic, its DHT functionality is "terribly broken" on SUSE because it's disabled by SUSE devs.


I've compiled the latest release of KT and DHT still doesn't work
George
Moderator
Posts
5421
Karma
1

Sun Sep 17, 2006 8:36 am
Can you post the log file, of a session with DHT enabled (make sure you have the DHT port forwarded if you are behind a router) :

~/.kde/share/apps:ktorrent/log
imported4-microchip
Registered Member
Posts
15
Karma
0

Sun Sep 17, 2006 3:25 pm
Bound to port 6881
Loading /home/microchip/.kde/share/apps/ktorrent/tor0/
OutputPath = /home/microchip/Upload/Nemesis.avi
Loading plugin searchplugin
Loading plugin infowidgetplugin
Showing KT
Starting download
Doing tracker request to url : http://tracker2.bt-chat.com/announce?pe ... cb%besJ%df
IP 0.0.0.0 banned.
Initiating connection to 86.61.67.152
Initiating connection to 196.205.179.159
Initiating connection to 82.79.52.163
Initiating connection to 213.93.78.190
Initiating connection to 87.194.60.196
Initiating connection to 217.44.218.205
Initiating connection to 85.197.244.221
Initiating connection to 83.248.64.229
Initiating connection to 69.197.187.239
Initiating connection to 199.126.247.33
Initiating connection to 88.113.195.47
Initiating connection to 88.9.244.49
Initiating connection to 203.59.252.51
Initiating connection to 88.73.207.58
Initiating connection to 213.67.194.100
Initiating connection to 85.197.219.121
Authentication to 213.67.194.100 : failure
Initiating connection to 213.67.194.100
Authentication to 213.67.194.100 : failure
Authentication to 82.79.52.163 : failure
Initiating connection to 82.79.52.163
Authentication to 82.79.52.163 : failure
Authentication to 217.44.218.205 : failure
Initiating connection to 217.44.218.205
Authentication to 217.44.218.205 : failure
Authentication to 85.197.244.221 : ok
Starting socketmonitor thread
Peer supports Fast Extensions
Authentication to 203.59.252.51 : ok
Timeout occurred
Authentication to 86.61.67.152 : failure
Initiating connection to 86.61.67.152
Timeout occurred
Authentication to 196.205.179.159 : failure
Initiating connection to 196.205.179.159
Timeout occurred
Authentication to 213.93.78.190 : failure
Initiating connection to 213.93.78.190
Timeout occurred
Authentication to 87.194.60.196 : failure
Initiating connection to 87.194.60.196
Timeout occurred
Authentication to 83.248.64.229 : failure
Initiating connection to 83.248.64.229
Timeout occurred
Authentication to 69.197.187.239 : failure
Initiating connection to 69.197.187.239
Timeout occurred
Authentication to 199.126.247.33 : failure
Initiating connection to 199.126.247.33
Timeout occurred
Authentication to 88.113.195.47 : failure
Initiating connection to 88.113.195.47
Timeout occurred
Authentication to 88.9.244.49 : failure
Initiating connection to 88.9.244.49
Timeout occurred
Authentication to 88.73.207.58 : failure
Initiating connection to 88.73.207.58
Timeout occurred
Authentication to 85.197.219.121 : failure
Initiating connection to 85.197.219.121
Authentication to 88.9.244.49 : ok
Authentication to 88.73.207.58 : ok
Authentication to 199.126.247.33 : ok
len err BITFIELD
Timeout occurred
Authentication to 86.61.67.152 : failure
Timeout occurred
Authentication to 196.205.179.159 : failure
Timeout occurred
Authentication to 213.93.78.190 : failure
Timeout occurred
Authentication to 87.194.60.196 : failure
Timeout occurred
Authentication to 83.248.64.229 : failure
Timeout occurred
Authentication to 69.197.187.239 : failure
Timeout occurred
Authentication to 88.113.195.47 : failure
Timeout occurred
Authentication to 85.197.219.121 : failure
Going the normal ServerAuthenticate routte
Authentication(S) to 69.197.187.239 : failure
Going the normal ServerAuthenticate routte
Authentication(S) to 85.197.219.121 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 85.197.219.121 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 85.197.219.121 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 196.205.179.159 : ok
Going the normal ServerAuthenticate routte
Authentication(S) to 83.248.64.229 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 83.248.64.229 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 213.67.194.100 : ok
Connection closed
Going the normal ServerAuthenticate routte
Already connected to -BC0070-výƒK›oº•Zœ4p
Authentication(S) to 196.205.179.159 : failure
Going the normal ServerAuthenticate routte
Authentication(S) to 85.197.219.121 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 213.67.194.100 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 83.248.64.229 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 82.79.52.163 : ok
Connection closed
Authentication(S) to 196.205.179.159 : failure
Going the normal ServerAuthenticate routte
Authentication(S) to 82.79.52.163 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 213.67.194.100 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 82.79.52.163 : ok
Connection closed
Going the normal ServerAuthenticate routte
Already connected to -BC0070-výƒK›oº•Zœ4p
Authentication(S) to 196.205.179.159 : failure
Going the normal ServerAuthenticate routte
Authentication(S) to 85.197.219.121 : ok
Connection closed
Going the normal ServerAuthenticate routte
Authentication(S) to 86.61.67.152 : ok
Connection closed
imported4-microchip
Registered Member
Posts
15
Karma
0

Mon Sep 18, 2006 2:45 pm
OK, i've recompiled KT again and now DHT works, but the problem now is that it always stays on 0 nodes/tasks
George
Moderator
Posts
5421
Karma
1

Mon Sep 18, 2006 4:42 pm
You have to connect to a peer which supports DHT to get DHT nodes.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot]