bugmldonkey, a multi-networks file-sharing client - Bugs: bug #503, Upload limitation does not work

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #503: Upload limitation does not work

Submitter:  None
Submitted:  Wed 29 May 2002 08:45:48 PM UTC
   
 
Category:  Core Severity:  3,5
Item Group:  None Status:  Remind
Assigned to:  mldonkey Open/Closed:  Closed
Release:  None Release: 
Operating System:  None Binaries Origin:  None
CPU type:  None

Jump to the original submission

Tue 02 Dec 2003 05:50:12 PM UTC, comment #20: 

This patch report is very old. If the bug still exists in current
versions please post a new bug report - spiralvoice

spiralvoice <spiralvoice>
Group administrator
Tue 29 Oct 2002 12:27:30 PM UTC, comment #19: 

I was just evaluating mldonkey. It has been running > 15hrs now and just NOW I am experiencing the same problem with upload larger than it should be

The problem is, upload limiting does work for transfers but I just took an "out-time" with "nu 60" and still I am exceeding 14+KBytes / sec. Then I went to look with a network sniffer on the linux server and I saw that mldonkey is NOT uploading a single file. However, it IS asking many many peers for files. All packets are around size 15, 30 and 60 bytes, so very small. But there are SO MANY of them that it saturates my upstream !

In short: mldonkey (version 2.0 release linux shared binary) seems to cap uploads but not meta-data/search upstream

I have an ethereal packet dump of a few seconds where mldonkey shows this behaviour. If the developers want it, just email me at -email is unavailable-

Anonymous
Mon 21 Oct 2002 09:06:36 PM UTC, comment #18: 

poelzi meant, that you can create a single account only for mldonkey, and shape the traffic for this account (eg. "leech"). Well , it works for me :)

greetz tech

Anonymous
Sat 19 Oct 2002 06:21:56 PM UTC, comment #17: 

well, just set it the uprate value to 5 as i did.
iptraf says outgoing rate is about 9-10kbyte/s, which
doesn't actually fit in the limitation, but my remaining 8kbyte/s bandwith is enough to manage other tcp/ip stuff

Anonymous
Thu 17 Oct 2002 05:27:14 PM UTC, comment #16: 

Darn, Even with the 'new' 2.0 so called 'stable' release this bug has not been fixed!
I set the cap to 10KB, but the §$%§! thing just ignores it and pumps out at 20KB at this point my provider disconnects me.

And please do not tell me to limit my overall-output like poelzi tried as I have more than one process on my box that needs some bandwitdh

Thanks

Anonymous
Wed 09 Oct 2002 06:13:42 PM UTC, comment #15: 

I use
http://fiaif.fugmann.dhs.org/ firewall and patched them for adding own rules. The patch is padded for adding into the distrbution but can get it from
http://files.poelzi.org/patches/fiaif/addbands.tar.gz

good look :)

Anonymous
Wed 09 Oct 2002 12:29:03 PM UTC, comment #14: 

i didnt know that. can you mail me your tbf script ?
Im using cbq atm.
-email is unavailable-

Invalid User ID <#11303>
Tue 08 Oct 2002 07:02:54 PM UTC, comment #13: 

When you use Linux you can use for example:
iptables -I INPUT -i ppp0 -t mangle  -m owner --uid-owner leech -j MARK --set-mark 67

Then run every P2P program as user leech. Every outgoing packet is marked and can be shaped by a tc rule to one limit.
Don't forget to use a qos qdisc and not only a class or mostly the wrong packages get droppend an transfer is realy bad. I have good experiences with tbf as qdisc.


Invalid User ID <#11315>
Tue 08 Oct 2002 03:05:18 PM UTC, comment #12: 

I live in Germany too. I experienced a few problems while testing mldonkey. The first one was , that mldonkey uses too many connections if you want to share the line with a few workstations. 5 PCs online at home here. If mldonkey runs a while nobody can even surf anymore. limit the connections to 200 or 300. QoS is a way to limit upload bw, BUT it limits (and if to fast drops) the p2p communication packets too (because they use the same port) and thats not what we want. I think it is the 900+ connections too, that is causing the uploadbw "override". To hold the connections a few kb/s are needed and to establish new ones even more bw is needed. Im not sure if mldonkey calculates this. So reduce the maxconnections value. Further i noticed a random disconnect. The first thing i thought its my ISP disconnecting me, because i cant do to many nmap scans without beeing disconnected. But this wasnt the case. I looked in the debugmessages of my clientsoftware ( rp-pppoe ) and saw a message like "net send error ... no buffer space availabe ... modem hangup". Its a bug in the UDP packet handling of the pppoe software. Its easy to fix. You just have to edit a line in the sourcecode and recomile it.
Sorry, I dont have the link anymore but I found the solution at the debian BTS. www.debian.org . The error appears if sending many UDP packets. (eg extended search).
Sorry for my bad english.

Invalid User ID <#11303>
Mon 07 Oct 2002 06:05:27 AM UTC, comment #11: 

max_hard_upload_rate = 15 works fine with me...
a workaround for users that are deconnected by their own provider would be to use QoS to limit bandwith usage on donkey ports.

Anonymous
Sun 29 Sep 2002 07:26:52 AM UTC, comment #10: 

update (me again)
just read the releasenotes of mldwatch 1.7 and found a bug report on the up/down speed shown in the statusbar.

unfortunateley this does not have anything to do with the problem of too high up/down rates i experienced

Anonymous
Sun 29 Sep 2002 07:05:07 AM UTC, comment #9: 

update concerning my post from 2002-Sep-16 02:39 (the huge one) : it's not only the downstream bw that's completely sucked up by mld, even the upstream is at 128kbit/s.
-
sure @ mldonkey, now i updated to mld1.99b8 and mldwatch 1.7.
the gui pretends to upload about 3-4kbytes/s with a given limit of value "10". [kilobytes per second, aight? ;) ]
but iptraf shows me an output bandwith of about 135 kbit/s.
(yes i checked iptraf even when mld was offline, and it was about 8kbit/s).
maybe it's not a transfer sucking up my bandwith, because mld found about 2600 sources for one file, but i limited the value to 1000. could this be the reason why i have no bandwith left?
ppp0 receives 45000 packets per minute, almost 98% for mld.
hand
mux

Anonymous
Mon 16 Sep 2002 07:30:37 PM UTC, comment #8: 

Don't forget these options are in kB/s and not kb/s

Next CVS snapshot will indicate in the GUI the uploaded/downloaded bytes.

mldonkey admin <mldonkey>
Group administrator
Mon 16 Sep 2002 06:39:12 AM UTC, comment #7: 

Hi
I use the same provider, and limitated my bandwith in mld 1.16 to 80/10 k/s, and it works pretty fine.
However, from time to time, my mld seems not to update his serverlist after restart (although 4 .met's are in the downloads.ini), and starts starving around with about 40 servers.
So i used the mld 1.99 beta5 core (just because of the nice windows-gui that's around),and now it seems to me that mld 1.99 has severe problems with bandwith limitation.
mld1.99 always seems to suck up the whole downstream bandwith, no matter which limit is set.As my linuxserver is used as a router to, it comes extremely unhandy that there's almost no downstream bandbwith available (even smallhonkclients like irc or icq can't connect to their servers - same applies to the browsers.)

have a nice day
mux

Anonymous
Thu 05 Sep 2002 12:29:33 PM UTC, comment #6: 

I have it too, it´s fucked up, because my hole house is on a router, and when mldonkey is running, the other computers can´t surf in the Internet!!!!

Alex

Anonymous
Mon 22 Jul 2002 08:46:20 AM UTC, comment #5: 

I have the same problem!

Invalid User ID <#9089>
Fri 14 Jun 2002 01:47:25 AM UTC, comment #4: 

Got the same problem. I temporarily fixed this with a smart router (Basically, I drop incoming frames when the bandwidth limit is reached). This is not the right/intelligent way of doing it. I would really like to get this one fixed.
Joel

Invalid User ID <#7483>
Sun 09 Jun 2002 12:01:56 AM UTC, comment #3: 

y0, got t-dsl too and have the same prob
got upload on 12K/Sec but its streaming more than 16K/Sec
:/ fix that plz

Invalid User ID <#7976>
Sun 09 Jun 2002 12:01:26 AM UTC, comment #2: 

y0, got t-dsl too and have the same prob
got upload on 12K/Sec but its streaming more than 16K/Sec
:/ fix that plz

Invalid User ID <#7976>
Sat 08 Jun 2002 11:56:26 PM UTC, comment #1: 

y0, got t-dsl too and have the same prob
got upload on 12K/Sec but its streaming more than 16K/Sec
:/ fix that plz

Invalid User ID <#7976>
Wed 29 May 2002 08:45:48 PM UTC, original submission:  

Hi,
I live in Germany and can only upstream with 16KB/s (capped by the German Telekom).
And if I set my mldonkey-upstream to 15 I am experiencing the problem, that mldonkey does not stick to its limitation, it always tries tries to send more than it can send and my Provider then allways disconnects me.

I am using mldonkey 1.16

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

 

Follow 5 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2003-12-02 spiralvoice Open/ClosedOpen Closed
2002-09-16 mldonkey CategoryNone None
    Severity3 - Normal None
    StatusNone None
    Assigned toNone None

Back to the top

Powered by Savane 3.13-4b48.
Corresponding source code