Howdy,

I've been running Ktorrent 1.2 on Ubuntu DapperDrake for a while, all has been fine - except that traffic shaping does not work.

Currently I have KDE 3.5.2 installed and the KDE desktop environment dual booting with Gnome.

Under KDE and Gnome (just using both to check because whilst I normally use Gnome this is a KDE app and I thought Gnome could possibly be breaking it) the bandwidth limiter does not limit bandwidth at all.


I decided to try 2.0b1, used dpkg to force it to install (it had to rewrite a file handler if I remember rightly), and now I still have the lack of bandwidth limiting with the addition of Ktorrent incorrectly reporting its bandwidth usage.

It will say it is currently using say 40-70kB/s downstream and 0kB/s upstream, whilst network monitor shows my downstream is maxed out and choking (at 160kB/s) and upstream is hovering at about 6-8kB/s (of 25kB/s). Killing Ktorrent causes network usage on both down and upstream to drop to 0kB/s, and trying to run other applications whilst Ktorrent is running is very slow, indicating that Network Monitor is not lying.


Ktorrent 1.2 wasn't quite so much of a bandwidth hog even with scheduling off - I could still browse webpages and such nicely even with it going flat out. With 2.0b1 reporting 40-70kB/s I have to wait for webpages and such to load.


Is there anything that you can suggest I do to find the problem? Is there anything I can do to fix the problem if it is known about? I am quite happy to go back to 1.2 for the mean time but it would be handy if I could get the bandwidth limiter working in at least one of the two versions.

FYI I installed 1.2 via apt-get and 2.0b1 from the .deb


Any help you can give on this would be appreciated!

Cheers
-Maelstrm

Do you have DHT enabled? That seems to be causing quite a few of the issues around.

We only show the actual data going up and down.

We haven't really measured DHT overhead yet, but at the moment there is quite a bit of overhead from connection attempts, I still need to deal with this.

DHT was disabled in both cases.

Thanks for the quick replies though!

Just FYI this is still an issue. Is there anything I can do to help provide information on what is causing it?

Maelstrm wrote:Just FYI this is still an issue. Is there anything I can do to help provide information on what is causing it?

Not much I am examining it here.