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

KTorrent cannot read bittorrent dht torrents

Tags: None
(comma "," separated)
Moshroum
Registered Member
Posts
63
Karma
0
As I read before, DHT support was added to ktorrent (I saw the button and the icon in the peer list), but when I create a dht (only) torrent in bittorrent 4.4.0 (btw. it is not possible with ktorrent->new) and then try to open it in ktorrent, I get "An error occurred while loading the torrent. The torrent is probably corrupt or is not a torrent file.".

Here is a small test torrent (use "uudecode FILENAME.uu" - from sharutils - to decode file)

Code: Select all
begin 644 tescht.torrent
M9#$S.F-R96%T:6]N(&1A=&5I,3$T.#$S,C,U.&4T.FEN9F]D-CIL96YG=&AI
M-64T.FYA;64V.G1E<V-H=#$R.G!I96-E(&QE;F=T:&DR-C(Q-#1E-CIP:65C
M97,R,#H`+9>IT&8H#]!]"51RZ:@<,D'-YF4U.FYO9&5S;&PR,3IR;W5T97(N
78FET=&]R<F5N="YC;VUI-C@X,65E964`
`
end

Code: Select all
begin 644 tescht
%0FQU8@H`
`
end


PS: Using Version from SVN Trunk (542839)
George
Moderator
Posts
5421
Karma
1

Sun May 21, 2006 8:44 am
You are right, I was comparing the wrong type fields when this torrent got loaded.

It is fixed now in SVN.
Moshroum
Registered Member
Posts
63
Karma
0

Sun May 21, 2006 9:36 am
Ok, import seems to work, but I had some different problems. I started a DHT session with bitcomet 0.66 and nothing happened for a while. After checking the logs I noticed the long list of "Cannot find RPC call" (something like that). But after I restarted ktorrent, I looked like peers where find and Information where send between the two nodes.
Some times later I looked at the peers page and noticed that the DHT info icon was the red cross......ehrm, I am sending data over a trackerless session and the other peer has no dht support (which bitcomet 0.66 has of course)....?
George
Moderator
Posts
5421
Karma
1

Sun May 21, 2006 12:09 pm
Moshroum wrote:Ok, import seems to work, but I had some different problems. I started a DHT session with bitcomet 0.66 and nothing happened for a while. After checking the logs I noticed the long list of "Cannot find RPC call" (something like that). But after I restarted ktorrent, I looked like peers where find and Information where send between the two nodes.


Cannot find RPC call is when RPC calls timeout, this happens regularly, it's just the other peer not responding in time.

Some times later I looked at the peers page and noticed that the DHT info icon was the red cross......ehrm, I am sending data over a trackerless session and the other peer has no dht support (which bitcomet 0.66 has of course)....?


The other peer has to indicate that it supports DHT in the handshake. Maybe BC doesn't do that and just sends a PORT packet ?


Bookmarks



Who is online

Registered users: Bing [Bot], blue_bullet, Google [Bot], rockscient, Yahoo [Bot]