Really impressed by the new features, especially dht, the client is steadily becoming a tough competitor with utorrent as far as features are concerned.
I was wondering, though, is it normal that ktorrent shows so few dht nodes? The most I saw was 2 nodes. In utorrent I usually get around 250.
Do the numbers compare at all?

Thanks again for delivering this awesome client!

md wrote:Really impressed by the new features, especially dht, the client is steadily becoming a tough competitor with utorrent as far as features are concerned.
I was wondering, though, is it normal that ktorrent shows so few dht nodes? The most I saw was 2 nodes. In utorrent I usually get around 250.
Do the numbers compare at all?

Thanks again for delivering this awesome client!

We save the nodes at exit and reload them. µTorrent probably doesn't do this. This is part of the draft DHT spec, which was released a couple of weeks before we released 2.0beta1. We made sure KT followed this spec, my guess is that the next version of µTorrent will probably do this to.

We save the nodes at exit and reload them. µTorrent probably doesn't do this.

I'm wondering how exactly does that explain the lack of nodes? Wouldn't that mean ktorrent should have MORE than utorrent, not less?

I have around 90 nodes at the moment, probably just a matter of get onto a torrent with lots of DHT clients.

I have 113 nodes This DHT is actually working fine.

BTW, I posted a thread on uTorrent forums regarding DHT implementation. So far I got an answer saying that 'we have to reverse engineer Mainline DHT protocol since there's no official documentation'. I guess they didn't understand my question right. Anyway, I'm waiting for their next reply.

Ivan - can you link to the uTorrent post?

__EDIT__

Never mind
http://forum.utorrent.com/viewtopic.php?id=10655

Yeah, that's the post. Apparently they reverse engineered BitComets DHT which *should* be compatible with Mainline...

It seems like they never use the flags and only use router.bittorrent.com for getting nodes

doesn't that go totally against the entire idea behind DHT? once the server goes, so does the DHT, how silly is that?

Well, this router.bittorrent.com was the mainline standard some time ago. They have changed it from two seperate networks into one network with the normal tracker protocol as the main source for other peers(and some local dht file).
I am not sure if mainline supports "both" networks at the moment. Would be nice to know i think.

Hi there,
I have a certain question. Is there something special that has to be done for ktorrent to start collecting DHT nodes. In my ktorrent they stay on zero all the time. The check is set for enabling dht network and the nodes still stay zero.
On uTorrent there is no such thing. There alsways stay about 250 nodes in the uTorrent client.
Thanks in advance

The specification says that you shouldn't ask router.bittorrent.com automatically [1], but utorrent does that. [2] When you add a dht-only-torrent to your client, the client should ask the default peers entered in the torrent. KTorrent seems not to do it [3], but it asks the known clients (you are downloading from) which have set the dht flag set or informed you over dht stuff. utorrent doesn't do that really. [2]

So both clients seems to do something wrong
utorrent developers doesnt seem to react really to our complains [2], but George knows about it [3] and will hopefully fix it some time in the future.
The only problem I see is that I never got near to the 250 clients which utorrent gets by default...even after running ktorrent a long long long...long time. Even not when It got peers from another client (bittorrent 4.4.0) on my machine....and the bittorrent routing table is getting really big (but the bt routing_table isnt binary compatible with ktorrent dht_table, so I cannot really exchange it for test stuff....maybe I will write some stuff when I got time again in ~1 month)

[1] http://www.bittorrent.org/Draft_DHT_protocol.html
[2] http://forum.utorrent.com/viewtopic.php?id=10655
[3] http://ktorrent.pwsp.net/forum/viewtopic.php?t=603

EDIT: I wrote a little script to test what bittorrent has nearly directly after adding a dht-only-torrent. I noticed that only ~140 clients where listed...

EDIT: I sniffed the utorrent startup phase and must say that I was wrong. utorrent doesnt use router.bittorrent.com. Instead it uses router.utorrent.com. After getting some (~30) nodes it will use them to find some more peers and ends with ~220 nodes. So if you have a dht-only-torrent with router.utorrent.com as default node, you should end with the same amount of nodes when ktorrent has the fix for [3].

uuencoded test.txt.torrent:

Code: Select all

begin 644 test.txt.torrent
M9#$S.F-R96%T:6]N(&1A=&5I,3$U,3@V-S0R-64T.FEN9F]D-CIL96YG=&AI
M,35E-#IN86UE.#IT97-T+G1X=#$R.G!I96-E(&QE;F=T:&DS,C<V.&4V.G!I
M96-E<S(P.K17X&%2JD+<4"YA[/.FK%NX#1C4934Z;F]D97-L;#$Y.G)O=71E
7<BYU=&]R<F5N="YC;VUI-C@X,65E964`
`
end


Number[3] is under development, only need to test it at the moment.