Hello,

Poisoning of BitTorrent network is becoming relatively common, thus a feature of blocking peers who send bad data continuously will be really great.

On Linux platform only Azureus supports this feature while in Windows utorrent is another client that can perform this function. If ktorrent adds such a feature then it will be a major benefit for users. So is it possible?

Regards,
Abhay

I never knew such a feature existed but now that I do, I'd like to join you in requesting this feature.

It is possible since v1.2 if I remember right. KT instantly bans peers who send bad data.

So, this feature exists for quite some time now

Ivan wrote:It is possible since v1.2 if I remember right. KT instantly bans peers who send bad data.

Wow! Never knew it. Shouldn't it be a more advertised feature cos it is quite a great thing to have imho.

Anyways, after reading your reply I did some googling and got to this thread here
http://ktorrent.pwsp.net/forum/viewtopic.php?t=242

It talks about banning peers instantly i.e. they send bad data once...and zap...you are banned! The discussion happened in Jan and a user objected about this policy but the discussion did not go anywhere. Is the policy still the same i.e. one bad occurrence and you are gone? Also, how do I know how many peers I am blocking? In Azureus you can see the number in status bar but you don't know in ktorrent. Any method on how I can check?

Is the policy still the same i.e. one bad occurrence and you are gone?

Yep. Peers are banned for current session only, so it's better to prevent unnecessary junk download by banning them.

Also, how do I know how many peers I am blocking? In Azureus you can see the number in status bar but you don't know in ktorrent. Any method on how I can check?

Latest SVN version has ipfilter GUI where you can see all banned peers. These changes will be included in the next minor release (v2.1), so try SVN version or wait for the next release.

Ivan wrote:Latest SVN version has ipfilter GUI where you can see all banned peers. These changes will be included in the next minor release (v2.1), so try SVN version or wait for the next release.

Oh that is a great a feature. Will grab the SVN ebuild then