I'm using Ubuntu 10.10, and have a question about the network activity of Transmission 2.22. Even though I set the global upload limit to 1kbs/s or even 0kb/s, my System Monitor/Conky shows a steady 20-25 kb/s upload rate. I'm just curious, what's with this upload rate and is there any chance to reduce it?
Ubuntu – Why doesn’t Transmission respect the 1 KB/sec upload limit
bandwidthtransmission
Related Solutions
Limiting single interface is easy, but global rate limits need more complex rules as do application based rules. I'm not saying that it can't be done, but it requires quite a bit digging in to the internals of the networking.
Here is a quick How to on setting up a per interface limit
If you really want to set up application based rules, you should look in to some firewall framework, like shorewall, which have helper features to configure shaping. Even with these tools, it requires quite bit of forethought and testing to get it in to place. Doing something like this ad-hoc is not yet quite that easy.
First, add the PPA and update if you haven't already (Close transmission first):
Command line way:
sudo add-apt-repository ppa:transmissionbt/ppa
sudo apt-get update
sudo apt-get install transmission-gtk transmission-common
Or:
- Open Update Manager.
- Click "Settings".
- Click "Other Sources".
- Click "Add".
Enter (change oneiric to your version if different):
deb http://ppa.launchpad.net/transmissionbt/ppa/ubuntu oneiric main
deb-src http://ppa.launchpad.net/transmissionbt/ppa/ubuntu oneiric mainClose Settings Window.
- Click "Check".
- Once complete, click "Install Updates".
Second, Edit the Preferences in Transmission: 1. Open Transmission. 2. Open "Edit" ➜ "Prefernces". 3. Under the "Downloading" Tab, Under "Queue", set "Maximum Active Downloads" to the limit you desire.
Best Answer
The upload speed limit of Transmission limits the data itself, not the BitTorrent protocol data. It will have a steady consumption above the limit, the amount of consumption relates to the number of torrents, peers, DHT being on and other. The only way to limit it altogether is to limit with outer resources, like creating a slowed down bridge connection or connecting through proxy on localhost.