I think I don’t have to explain the advantages of torrents because you are already looking for a bittorrent server setup guide.
The setup isn’t really difficult, just the documentation could be better.
So when you have a computer that’s permanently running and has also internet access, it’s a nice idea to give something back to the community.
I personally run a transmissionbt on my Raspberry Pi. So don’t be scared that your computer/server has not enough power.
Note that I use aptitude. Under Ubuntu it isn’t installed by default. So either you install it via apt-get install aptitude or you use the apt-get and apt-cache command. The result will be the same. You also need root access. So either you have access to the root account or you are allowed to use sudo for that.
Install the server daemon. To find the proper name type
aptitude search transmisson .
That will give you a list with all transmission related packages. Choose the name of the daemon (under debian transmission-daemon) and install it:
aptitude install transmission-daemon
So the server is installed and running. Wasn’t so difficult, was it?
We have to configure the server to fit your needs. Therefore will have to stop the running daemon first:
service transmission-daemon stop
Now we can change the configuration file called settings.json. To do so, choose your favourite editor and edit the file /etc/transmission-daemon/settings.json (note you need root privileges):
I know, there are a tons of options. But don’t worry, the most defaults fit your needs perfectly. I will just mention the essential configurations (for me). If you want a complete description for all of them, visit https://trac.transmissionbt.com/wiki/EditConfigFiles.
I love the simple ways. So I use the web interface to add new torrents. To activate it for your local network you have to do the following changes:
„rpc-whitelist“: „127.0.0.1,192.168.*.*“ 127.0.0.1 is the machine. Add your ip-address behind it. * is a wildcard, so it’s everything.
„rpc-authentication-required“: true That means password login. so only allowed persons can add or remove torrents.
„rpc-username“: „transmission“ The default user name. A change will improve the securitiy.
„rpc-password“: „blablub“ The password is encrypted. So it’ll look different. Enter yours there. It gets encrypted.
„rpc-port“: 9091 The default port for the interface. Change it if you like.
So fare about the web user interface. Now you can access the server via your browser. If it is your local machine, enter http://localhost:9091/ to access it. Else enter the ip-address of the machine. When you want access from the internet, so that you can add torrents from elsewhere, change the rpc-whitelist to the ip of your router or enter only wildcards (*.*.*.*). You also have to open the port in your router (9091).
To allow your torrent server to talk with other clients on the internet, you have to give him the possibility to do so. That for, set the option
This will open the default port in your router configuration. If you don’t like the default port for any reason, you can modify it or set it to random. Here are all options for that:
So that’s it. This is all you need to run a bittorrent server. But by now, it will use your complete bandwidth for the uploads. So in practice, you can’t visit the web anymore (in an acceptable speed).
To limit the bandwidth for the server, you can set a permanently maximum it can use or a time based limit. I prefer the time based limit. So during the day, the server is limited to 150 KB/s so that I have about 150-200 to browse the web. At night, it gets the full speed.
To set these limits in any way you want, you have to modify these options(this i my config):
„alt-speed-down“: 3000, Download-Limit in KB
„alt-speed-enabled“: false, The alt-speed is the permant variant
„alt-speed-time-begin“: 330, Gets limited at 330 in minutes from midnight
„alt-speed-time-day“: 127, Means everyday, see the link EditConfigFile above
„alt-speed-time-end“: 1320, The limit ends at 1320 minutes after midnight
„alt-speed-up“: 200, Upload limit in KB
So, after all this changes, your server should fit your needs in the most cases. Now restart it:
service transmission-daemon start
To proof it is running visit the webui http://localhost:9091/
That’s it. Have fun, and share what you can (legal).
In the case that your server runs on something as powerful as a Raspberry Pi and it has many torrents on it and also much traffic, so it starts lagging, you can change the allowed peers (clients) that can connect at the same time. I just wanted to mention it. You have now all information sources to figure it out by yourself.
Greetings from Berlin, Germany