Any way to limit upload bandwidth
 

Is there a way in Gnucleus to cap upload bandwidth?

There's an over-all cap, and a way to limit message bandwidth during transfers, but I find those downloading from me can use all of my upstream bandwidth. This slows down any downloads I may have going.

What I'm looking for is a way to place a cap on upload bandwidth as a whole. Lime and BS do this nicely (Gnote limits it per connection which is kinda useless).

Re: Any way to limit upload bandwidth
 

[Is there a way in Gnucleus to cap upload bandwidth?]

No, as far as I know (1.3.2.). Maybe later- go and suggest it at sourceforge.com.

Greetings....

How to limit
 

In the preferences, under bandwidth, there is an option to limit total bandwidth.

Actually this option will only limit upload bandwidth, this should work if you put a value in it. Please let me know if it doesnt.

Thanks!
 

Thanks That seems to work!

From the name I thought that would limit the total bandwith both up and down (which I can see for people who's ISPs force transfer limits).

...

Oops, I may have spoke too soon (I'm editing this post). If I set my upload limit to 30k it's actually dropping *way* below this. It looks as if it keep lowering the upload bandwidth until up + down = 30k. This can grind uploads to a virtual stop which isn't want I want. I just want to keep the upload bandwidth below 30k (since realistically that's all I can serve). Download should go as fast as the remote side will allow.

Well i have tested the speed limits in a LAN enviroment and they seem to work fine. There are 2 factors that might be responsible for your observations:

1. As you probably are on some kind of ADSL line your upload and download speed are "linked" together.
quote from a posting on some msg board

"
First, ADSL is 2 channel as much as SDSL is, except the channels are different sizes: upload is usually quite a low speed.
Second, its got nothing to do with the remote server having trouble doing two things at once.
The main reason upload slows download and vice versa is that downloading at full speed takes some of the upload channel for ack packets. Not a lot, but some. About one small ack packet for every 2 large data packets.. With really unbalanced ADSL speeds, like 1500/128, this small up traffic of acks is actually quite a chunk of your 128..

The bigger problem, that people have observed and emailed me about, is to do with TCP throttling down when there are delays in ack packets.. as would happen if you were hammering your upload channel.. the end result is that you cannot optimally use full speed in both directions, even on SDSL lines, for TCP protocol (used for FTP/http etc) although you can for UDP traffic (streaming video)..
"

2. the people downloading from you might only be on modem or ISDN

This is my whole point for wanting to limit upstream bandwidth!

On any network connection downloading requires some upstream bandwidth for ACK's. If the person uploading from me is taking *all* my bandwidth, there will be nothing left for this. The problem well understood - LimeWire, BearShare, and Gnotella allow you to specifically cap upload bandwidth to prevent this (Although Gnotella's method isn't great).

Gnucleus bandwidth limits work fine, it's just that it doesn't seem to have the limit I need. It will cap the total bandwidth by lowering the upload until up + down <= cap (as least this is what seems to happen), but as far as I can't see you can limit the upload bandwidth alone.

With my ADSL I have a bit over 150k down and 30k up. To preserve my download speed I only need to reserve a small bit of that upload bandwidth for myself, but if I place the total cap to 30k the upload bandwidth allowed will shrink to zero (since downloads often exceed 30k). This completely shuts people download from me out which is not what I want to do.