First of all, I want to say that I love the ktorrent project. The current release seems to be stable on my machine with the webui working great. I get good speed, and the plugins work. Thanks for your hard work

I do have a few questions/concerns

Ktorrent seems to take an awful long time to complete torrents after the 99% mark. The torrents I am downloading are well seeded and for example at 99.8% ktorrent client downloads @ 100k+ for 20 mins and its still not complete.

I know that I dont want to get corrupt data, but I have never had a client that refused the end of the torrents. Is there a setting in the configs that I am missing?

The other thing I want to mention is that I never had a client's bandwidth stream fluctuates so quickly between refreshes. Example: I am downloading at 30K/sec hit refresh 1-2sec then its 100K. It goes up and down rapidly. Like I said I dont have a problem with Ktorrent speed, I actually think that Ktorrent is one of the fastest clients I have used. So I dont know if its the Ktorrent code, or if the incoming tcp connections do cause those spikes. It may be worth looking into.

If anyone can help with the unfinishing torrents I would appreciate it.

Thanks

Mike

After further investigating it is a few data "chunks" that do not want to receive. I have 2 chunks less then 1meg that will not pass the check. They keep restarting over and over. This has happened to me on more than 2 other torrents.

Is there any fix for this? I tried under options check data after every (changed to) "1" fail, but it still just keeps retrying. Forcing a re-check states that there is 2 chunks that failed, when I go in the chunks tab they just restart over and over.

Mike

Sorry about responding to my own thread...

The torrent did eventually finish at 100% just took awhile with bad chunks. I guess there is no way to avoid this huh?

Thanks

Mike

Hi!

What version of KTorrent do you use?

Sorry, should have posted that...

Its Ktorrent 2.1.3 on Slax 6 rc2

*update*

If I leave downloads over night they seem to complete ok. I just wanted to mention that chunk situation. Maybe its the coding, maybe we cant do anything about "bad" chunks.

I have a new problem, like many users posted before I sometimes get a crash handler when I upload torrents through webui. I was not able to get a backtrace. I will review the logs and see if I can find something.

Thanks

Mike

Probably some peers sending bad data intentionally, you could try using the IP filter plugin, the blocklist from bluetack should protect you against most of these peers.

Hi George,

Thanks for the reply. I forgot to mention that I do have the ipfilter plugin on, it says the bocklist is loaded.

Ive been doing p2p for a long time now. I dont think there is much anyone can do about recieving bad data because as you pointed out, it could very well be intentional. I just wanted to point out that it "seemed" like Ktorrent was taking longer than other clients once it reached 99%+. The truth is that other clients do the same (just hard to ignore when its 100k+ for 1 meg and it takes 20 min)

There has been some discussion on a development implementing a rule that would state:

"If a peer [ip address] sends "x" amount of bad data (chunks), then blacklist"

If such a rule can/will be written, then the p2p will have won another battle.

Mike