Make your own seedbox

[puroi]

This guide is currently a work in progress. If you notice any errors, inaccuracies or know a better way of accomplishing what I am trying to explain please PM me or comment below.

Things to Fix

- Grammar
- ...

Index
01. Credits
02. Initial Configuration
03. libtorrent, rTorrent & xmlrpc-c
04. rutorrent
05. Updating & Patching
06. rutorrent Plugins
07. apache
08. vnStat & PHP Frontend
09. vsftpd
10. Security
11. Troubleshooting


I need to credit various sources on the internet for giving me the knowlegde I needed to write this. A few months ago I knew nothing about configuring a server and everything I have learned has been from these people/sources. Thanks go to naq, EmEyKeYwAy & scribe. I have also used Google and all of the software developers websites as well as lots of patient IRC dwellers' help.


Initial Configuration

This guide assumes you know a small amount about Linux and using the command line. Having said this nothing we will do is very hard and I will make every effort to explain each step.



I assume you will begin with a stock standard Debian server install but pretty much any version of Debian and its derivatives (Ubuntu etc...) will work just fine.

The principles of what I am doing will apply to any distribution of Linux although the commands and file locations will differ.

At the end of this guide you will have a server running the latest version of rTorrent with apache serving the latest version of rutorrent. I'll also provide instructions for compiling vsftpd, a light and secure FTP server. This guide will also cover some basic security measures you can take to harden your server against bots and hackers.

You will need root access to your server, be it at home or somewhere else. We will do most of what follows as root. Be careful as you can cause mayhem!

I will assume you are interfacing with your seedbox using PuTTY (above) or a similar SSH client. I have placed the commands you need to input in [ quote] [ /quote] tags. You can literally copy and paste these into PuTTY. Note that the '#' or '$' preceding each command are not part of the command. '#' denotes that the command is done as root and '$' means it is executed as a normal user. Don't include it when you copy and paste!

Each command has its own set of tags so you don't get confused and try to run two commands at once.

Handy Hint: The default 'paste' command in PuTTY is right click. Ctrl V will not work.

First off lets make sure we are up to date.

# apt-get update

# apt-get upgrade

Next up we'll install the required packages for our compiling and installing what we need.

apt-get install apache2.2-common apache2-utils autoconf automake autotools-dev binutils build-essential bzip2 ca-certificates comerr-dev cpp cpp-4.1 dpkg-dev file g g -4.1 gawk gcc gcc-4.1 libapache2-mod-php5 libapache2-mod-scgi libapr1 libaprutil1 libc6-dev libcurl3 libcurl4-openssl-dev libexpat1 libidn11 libidn11-dev libkadm55 libkrb5-dev libmagic1 libncurses5-dev libneon26 libpcre3 libpq5 libsigc -2.0-dev libsqlite0 libsqlite3-0 libssl-dev libssp0-dev libstdc 6-4.1-dev libsvn1 libtool libxml2 lynx m4 make mime-support ntp ntpdate openssl patch perl perl-modules php5 php5-cgi php5-common php5-sqlite pkg-config postfix postfix-mysql screen sqlite subversion sudo ucf zlib1g-dev

You will need to agree to any dependancies these packages may have and depending on the server's connection to the internet installation may take several minutes.

If you have no users on your system you will need to create a new one to run rTorrent. A note on rTorrent and rutorrent; they are both designed as single user systems which means that if you are setting up a box to resell or even just to share you will need to either run multiple instances or rTorrent and rutorrent (one per user) or simply have everyone use the same instance and make use of rutorrent's labelling system.

I believe the latter is better for conserving system resources but the downside is that each user will be able to see what the other is downloading and the WebUI can become quite cluttered depending on the number of users. I will provide a guide detailing how to configure a single user system which multiple users can use. If demand is high, I will add an example of how to setup a server running multiple instances of rTorrent and different versions of rutorrent for each user.

# adduser USERNAME

You will be asked for some random information about your user. You can add whatever information you'd like. Now we'll create the needed directories.

# mkdir /home/USERNAME/downloads

# mkdir /home/USERNAME/watch

# mkdir /home/USERNAME/.rtorrent

# mkdir /home/USERNAME/.rtorrent/session

Lets give the correct permissions to our user.

# chown USERNAME -R /home/USERNAME/

You're now ready to install rTorrent.


libtorrent, rTorrent & xmlrpc-c

Now we will compile the latest versions of libtorrent and rTorrent. rTorrent can also make use of xmlrpc-c as well so we'll compile it too. I usually compile software in /usr/local/src/ but where you compile source is up to you.

xmlrpc-c

# cd /usr/local/src/

# mkdir xmlrpc-c

# cd xmlrpc-c/

# svn co https://xmlrpc-c.svn.sourceforge.net...mlrpc-c/stable

# cd stable

# ./configure --disable-cplusplus

# make

# make install

# cd /usr/local/src/

libtorrent

# svn co svn://rakshasa.no/libtorrent/trunk/libtorrent

# cd libtorrent/

# ./autogen.sh

# ./configure

# make

# make install

# cd ..

rTorrent

# svn co svn://rakshasa.no/libtorrent/trunk/rtorrent

# cd rtorrent/

# ./autogen.sh

# ./configure --with-xmlrpc-c

# make

# make install

These programs can take some time to compile depending on your hardware.

After all that we should update some shared libraries:

# nano /etc/ld.so.conf

Add the text "include /usr/local/lib/" to the file (without the quotation marks) and save and exit. To save in nano is Ctrl O and to exit is Ctrl X.



Update the system libraries.

# ldconfig

Congratulations! Assuming all went well you now have a brand new rTorrent installation. Lets configure it.

# nano /home/USERNAME/.rtorrent.rc

There are several dozen options you can play with in rTorrent. Take a look over here for the full list.

Here is an example rTorrent configuration file. You can copy and paste it into nano if you'd like.

[quote]# SCGI Settings

scgi_port = 127.0.0.1:7001

[puroi]

# General Settings

bind = SERVER.IP.ADDRESS
ip = SERVER.IP.ADDRESS
port_range = 60450-60460
port_random = no
encoding_list = UTF-8
check_hash = no
directory = /home/USERNAME/downloads
session = /home/USERNAME/.rtorrent/session
encryption = allow_incoming,try_outgoing,enable_retry
peer_exchange = no
schedule = watch_directory,5,5,load_start=/home/USERNAME/watch/*.torrent
schedule = low_diskspace,5,60,close_low_diskspace=500M
schedule = untied_directory,5,5,stop_untied=

# Throttle Settings

upload_rate = 0
download_rate = 0
min_peers = 1
max_peers = 256
min_peers_seed = 1
max_peers_seed = 256
max_uploads = 64
max_uploads_global = 64
max_downloads_global = 64

# Tracker Related Settings

enable_trackers = yes
use_udp_trackers = yes
dht = disable

# Extra Settings

#schedule = tied_directory,5,5,start_tied=
#schedule = untied_directory,5,5,close_untied=
#on_start = link1,"create_link=tied,,.started"
#on_stop = link1,"delete_link=tied,,.started"
#on_finished = link1,"create_link=tied,,.finished"
#on_erase = link1,"delete_link=tied,,.finished"
#schedule = low_diskspace,5,60,close_low_diskspace=500M
#schedule = ratio,60,60,"stop_on_ratio=1020,9000M,9000"
#on_erase = rm_complete,"execute=rm,-rf,--,$d.get_base_path="[/quote]
There are several options you will need to configure. They are marked in red. The other options listed can also be configured as you like. The port range you use is up to you but keep in mind that the default bittorrent port range is not permitted to be used on most trackers. Generally somewhere in between 49152 - 65535 will do for most private sites.

The text in 'Extra Settings' is commented out but there are some powerful commands you can add to rTorrent to customise it. Read more over at the author's site.

The throttle settings are pretty much default and can be adjusted to suit your hardware and connection.


rutorrent

Now we will install rutorrent, a WebUI to rTorrent. There are several different web user interfaces available for rTorrent but I prefer rutorrent. You can check out wtorrent, rtgui and ntorrent but I won't offer support for them.

Navigate to the directory that apache can see (the default is /var/www/) and grab the latest build of rutorrent.

# cd /var/www/

# svn co rutorrent - Revision 519: /trunk/rtorrent

Lets edit the rutorrent configuration file.

# nano /var/www/rtorrent/config.php

Edit the line which includes RPC_TIME_OUT and change it to 15000. This simply cuts down on the number of messages which are logged to rutorrent about timeout requests (it can become annoying).

Next, edit the line starting with $scgi_host and change it to the same port as you set in the rTorrent configuration file. It is very important these numbers are the same and that you remember this number for later when we configure apache.


Updating & Patching

libtorrent & rTorrent

If a new release of rTorrent is released and you need/want to upgrade (make sure TehConnection has whitelisted it first!) all you need to do is navigate to the source directory and update:

# cd /usr/local/src/libtorrent/

# svn update

Then follow the same steps as above to recompile and reinstall rTorrent (./autogen.sh, ./configure, make, make install, make clean...) Your settings and session data will not be erased as it is all saved in a different location.

rutorrent

If you ever need to update rutorrent you can simply issue these commands from the directory rutorrent is installed in (/var/www/rtorrent/):

# svn update

Patching rutorrent

At times the developers and testers will find issues with rutorrent and issue a patch to correct it. These patches can often be useful and waiting for the next release takes a while. This page shows how to add patches to software in Linux.


rutorrent Plugins

There are many plugins available for the rutorrent frontend which offer enhanced functionality. You can view these here.

I'll update this guide as I experiment with them and recommend the better ones. If you have any experience with any of these plugins please PM me and I'll add extra info.


apache

Now we need to enable SCGI in apache. This is so rTorrent and rutorrent can communicate. There is a plugin for rutorrent which accomplishes this but I have not tested it and from what I have heard my method provides better performance for now. Copy over the SCGI mod to enable it in apache.

# cp /etc/apache2/mods-available/scgi.load /etc/apache2/mods-enabled/scgi.load

We need to edit the httpd.conf file and enable the SCGI communication port.

# nano /etc/apache2/httpd.conf

Add "SCGIMount /RPC2 127.0.0.1:Same port as rTorrent & rutorrent" without the quotation marks and save and exit the file.



Restart apache so the changes take effect:

# /etc/init.d/apache2 restart

Because we have been editing and creating files as root our file permissions will be slightly borked. Lets fix that.

# chown USERNAME:USERNAME -R /home/USERNAME/

# chmod 755 /var/www/rtorrent/

Open a new instance of PuTTY and login to your server as the user you created to run rTorrent. Once logged in start rTorrent with screen.

$ screen rtorrent

If you get an error "[screen is terminating]" there is most likely an error with the rTorrent configuration file or rTorrent itself. You can take a look at the file as your user by simply typing:

$ nano .rtorrent.rc

Lets take a look at that new rutorrent installation.

http://IP.ADDRESS.OF.YOUR.SERVER/rtorrent/ - If your host has given you a URL (some.server.net) then that will work as well.

If everything loads nicely then all has gone well.



Authentication

You might have noticed that we were able to browse directly to the rutorrent page without having to enter any kind of password. Unfortunately rutorrent does not have any kind of authentication system. To protect our WebUI we will need to make apache ask for a password.

On top of this I have also decided that I will explain how to use ssl for communicating with apache (https). This is because the username and password will be sent in clear text and anyone sniffing your packets will be able to grab the credentials otherwise.

First off, lets create ourselves a self-signed certificate. We need this to use encryption but unfortunately browsers will throw up exceptions to self-signed certificates. There is nothing wrong with them it is just that they cannot be verified by a third party Certificate Authority (CA). You would do well to not trust any self-signed certificates unless you trust the website owner. Since that owner is yourself we are going to be OK.

Generate a key for the Certificate Signing Request (CSR):

# openssl genrsa -des3 -out server.key 1024

You will need to enter a passphrase which cannot be shorter than four characters (ideally eight or more) that you must not forget. When we have finished every time you restart apache you will have to enter it.

Now we'll use our new key to create the CSR proper:

openssl req -new -key server.key -out server.csr

You will be asked a lot of information and you can put whatever you'd like in the fields that follow.

Now we'll create the certificate:

openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt

All we need to do now is to install the certificate and remove the other file.

# mv server.crt /etc/ssl/certs/

# mv server.key /etc/ssl/private/

# rm server.csr

Now we have a certificate we can enable mod_ssl in apache:

# cp /etc/apache2/mods-available/ssl.load /etc/apache2/mods-enabled/

All that is left now is to configure ssl, set a password for our rTorrent directory in apache and we'll be using rutorrent encrypted!

# nano /etc/apache2/sites-available/default

<VirtualHost *:443>
ServerAdmin webmaster@localhost

DocumentRoot /var/www/

SSLEngine on
SSLOptions StrictRequire
SSLCertificateFile /etc/ssl/certs/server.crt
SSLCertificateKeyFile /etc/ssl/private/server.key
<Directory />
Options FollowSymLinks
AllowOverride All
</Directory>
<Directory /var/www/>
Options FollowSymLinks
AllowOverride None
Order allow,deny
allow from all
</Directory>
<Directory /var/www/rtorrent/>
Options FollowSymLinksIfOwnerMatch
AllowOverride None
Order allow,deny
allow from all
AuthUserFile /etc/apache2/private/.htpasswd
AuthGroupFile /dev/null
AuthName "A Server Name"
AuthType Basic
<Limit GET POST>
require user USERNAME
</Limit>
</Directory>
...

The file contines after the dots but all you need to edit is what is highlighted in red. Where you see 'USERNAME' you may pick any username you'd like. If you'd like multiple username/password pairs to be able to login then replace your desired username with 'valid-user' (without the quotation marks).

Lets create the password file and then reboot apache and see if its all running smoothly.

# mkdir /etc/apache2/private

# cd /etc/apache2/private

# htpasswd -c .htpasswd USERNAME

htaccess will prompt you to enter and re-enter a password. If you want to add another user then enter the same command as before but don't type the "-c" part. That way you will simply add another user to the same file.

# /etc/init.d/apache2 restart

apache will ask you for your passkey which we created when we created the certificate. Now we'll browse to the new and improved encrypted version of your server.

https://IP.ADDRESS.OF.YOUR.SERVER/rtorrent/

vnStat

vnStat is a handly little program which keeps a record of your bandwidth usage by the server. It works by monitoring the network interface and can display the statistics via the commandline even in realtime.

This is useful to us but for those who can't be bothered firing up PuTTY for something like this there is a useful little frontend you can install so you can monitor bandwidth from your browser.

[puroi]

Lets grab the source for vnStat and get it running and configured:

# cd /usr/local/src/

# wget http://humdi.net/vnstat/vnstat-1.9.tar.gz

# tar -xzvf vnstat/vnstat-1.9.tar.gz

# cd vnstat-1.9/

# make

# make install

Now we'll test that vnStat is fine and then start the daemon. Lets select the interface we want to monitor and create the database entry for it.

# vnstat --iflist

My output for that command is: "Available interfaces: lo dummy0 eth0 tunl0 gre0" Pretty much everytime eth0 is the one you'd want to monitor.

# vnstat -u -i eth0

Now lets take a look at what our little friend can do:

# vnstat -l

Make sure it runs OK then exit and we'll create the init.d script.

# nano /etc/init.d/vnstat

Paste this into the file then save and exit. Make the file executable and update the rc.d.

# chmod x /etc/init.d/vnstat

# update-rc.d vnstat defaults

The daemon is now running so we can grab the frontend and install it.

# mkdir /var/www/vnstat/

# cd /var/www/vnstat/

# wget http://www.sqweek.com/sqweek/files/v...d-1.4.1.tar.gz

# tar -xzvf vnstat_php_frontend-1.4.1.tar.gz

# cd vnstat_php_frontend-1.4.1

# cp * /var/www/vnstat/

# rm vnstat_php_frontend-1.4.1.tar.gz

# rm -rmf vnstat_php_frontend-1.4.1

Now we have the files where they should be lets edit their config and test it out.

# nano config.php

Look for the line that says:

$vnstat_bin = ' ';

Change it to:

$vnstat_bin = '/usr/bin/vnstat';

Now lets test it out: https://SERVER.ADDRESS/vnstat/

If you see some data on the page then all is well! You can edit the other PHP files if you don't want to have the other interfaces appear or if you want a different colour scheme.


vsftpd

vsftpd is my favourite FTP daemon. It is light and secure and is able to provide encryption. Pretty much everything you could need. Remember that even during encrypted FTP sessions only the command channel is encrypted. The data channels remain unencrypted so anyone who is sniffing can see what is transferred. For the most secure possible session investigate rsync/sFTP over SSH. If you'd prefer another FTPd then you can also check out Pure-FTPd or ProFTPD.

Lets grab the vsftpd source.

# cd /usr/local/src/

# wget ftp://vsftpd.beasts.org/users/cevans...d-2.2.1.tar.gz

# tar -xzvf vsftpd-2.2.1.tar.gz

# cd vsftpd-2.2.1.tar.gz

# make

# make install

Remove the standard configuration file

# rm /etc/vsftpd.conf

Reopen the file and paste this configuration to get a more standard configuration.

# nano /etc/vsftpd.conf

listen_port=65497
listen=YES
#listen_ipv6=YES
anonymous_enable=NO
local_enable=YES
write_enable=YES
#local_umask=022
#anon_upload_enable=NO
#anon_mkdir_write_enable=NO
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
#chown_uploads=YES
#chown_username=whoever
#xferlog_file=/var/log/vsftpd.log
#xferlog_std_format=YES
#idle_session_timeout=600
#data_connection_timeout=120
nopriv_user=admin
#async_abor_enable=YES
#ascii_upload_enable=YES
#ascii_download_enable=YES
#ftpd_banner=Welcome to blah FTP service.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd.banned_emails
chroot_local_user=NO
chroot_list_enable=YES
# (default follows)
chroot_list_file=/etc/vsftpd.chroot_list
#ls_recurse_enable=YES
#
#
# Debian customization
secure_chroot_dir=/var/run/vsftpd
pam_service_name=vsftpd
pasv_min_port=65401
pasv_max_port=65410

You can change the port if you'd like but most definitely don't use the standard FTP communication port.


Security

Most of this information can be found in other places but as I have time I will add it here; probably in different tutorials as this one is long enough already.

To Add:

Changing the FTPd and SSHd port.
Authorized Keys.
Limit number of SSHd connection attempts.
Limit root login.
Configuring iptables.
PortSentry (listen on 21 & 22 to see who tries to connect).
rsync/sFTP over SSH (completely encrypted file transfer).


Troubleshooting

Common Problems

Coming soon...

[tripl3x]

Sunt noob total in linux adr nu inteleg ce faci prin tutorialu asta?
Iti transformi PC-ul itr-un seedbox? e deja ca un seedbox
De unde banda mare sau alt calculator ca la seedbox?

Nu va luati de mine prea urat, nu prea le am cu astea

[TheJudge]

Pai, cum spune si titlul threadului, iti faci propriul seedbox. De exemplu, daca ai un server dedicat cu banda buna si nu vrei sa iti iei un seedbox(care e si el un server dedicat dar care are aceste aplicatii deja instalate), urmezi tutorialul acesta si ai un seedbox.

E interesant tutorialul dar ce m-ar interesa pe mine, e partea care il face practic un seedbox; partea in care downloadeaza si uploadeaza automat, mai repede ca un client torrent cu rss-ul setat.

@puroi: poate ma iluminezi si pe mine cu aceasta treaba, continuand tutorialul cu ce am scris eu mai sus

[puroi]

Configuring a Debian Server As a Seedbox

Nu l-am facut eu. O sa va tin la curent cu ce modificari i se mai aduc tutorialului, desi daca cititi atent si va luati dupa acest tutorial, trebuie sa reusiti, de unde l-am luat are comentarii ca ar fi reusit cei care au incercat.

[TheJudge]

Nu contest faptul ca nu ar fi bun tutorialul, dar tot ce reusesti sa faci cu serverul dupa ce ai urmat tutorialul e sa iei torrent prin intermediul serverului, sa te conectezi remote la el, sa il controlezi remote si sa iei fisiere de pe el prin intermediul ftp-ului. Nicaieri in tutorial nu scrie despre upload si download automat folosind IRC-ul, ceea ce ma intereseaza pe mine si ceea ce nu stiu sau nu am cautat destul de mult...

[puroi]

To Add:

Changing the FTPd and SSHd port.
Authorized Keys.
Limit number of SSHd connection attempts.
Limit root login.
Configuring iptables.
PortSentry (listen on 21 & 22 to see who tries to connect).
rsync/sFTP over SSH (completely encrypted file transfer).

[Penemue]

Sau varianta prescurtata:

Plateste 15-20$ in plus pentru server cu Windows 2003 web sau Windows 2008
Sau fa-ti tu sistem acasa pe care instalezi Windows, orice versiune.

Instaleaza uTorrent pe el si logheaza-te pe sistem folosind Remote Desktop Connection.

Problem solved.

[ardei]

De acord cu Penemue. Am folosit varianta si merge de minune si e... simplu si util.

Eu am folosit vista.

[puroi]

Originally Posted by Penemue

Sau varianta prescurtata:

Plateste 15-20$ in plus pentru server cu Windows 2003 web sau Windows 2008
Sau fa-ti tu sistem acasa pe care instalezi Windows, orice versiune.

Instaleaza uTorrent pe el si logheaza-te pe sistem folosind Remote Desktop Connection.

Problem solved.

Of ce ne faceam daca nu erai tu, stateam sa invatam linux.

primu pe pagina:P

[nicholas]

E ceva de munca. Oricum foarte folositor tutorialul. Thx puroi

[Storm Winged]

Nu este ceva foarte complicat, e treaba de copy paste daca stati si va uitati.
Totul este ce sa faceti atunci cand intampinati vreo eroare.
Celor care au ca sistem de operare Ubuntu, exista un "installer", care instaleaza si WebUI nemaifiind necesar toti pasii din acest tutorial.

[Penemue]

Spuneti voi unui user sa scrie asta in linie de comanda:

apt-get install apache2.2-common apache2-utils autoconf automake autotools-dev binutils build-essential bzip2 ca-certificates comerr-dev cpp cpp-4.1 dpkg-dev file g g -4.1 gawk gcc gcc-4.1 libapache2-mod-php5 libapache2-mod-scgi libapr1 libaprutil1 libc6-dev libcurl3 libcurl4-openssl-dev libexpat1 libidn11 libidn11-dev libkadm55 libkrb5-dev libmagic1 libncurses5-dev libneon26 libpcre3 libpq5 libsigc -2.0-dev libsqlite0 libsqlite3-0 libssl-dev libssp0-dev libstdc 6-4.1-dev libsvn1 libtool libxml2 lynx m4 make mime-support ntp ntpdate openssl patch perl perl-modules php5 php5-cgi php5-common php5-sqlite pkg-config postfix postfix-mysql screen sqlite subversion sudo ucf zlib1g-dev

De-asta nu o sa aiba nici un Linux succes in randul userilor normali, pentru ca de cate ori incearca devin frustrati din cauza comenzilor criptice care variaza de la varianta de linux la varianta de linux , de la ubuntu 5 la ubuntu 6 samd.

De exemplu stau si ma uit si ma mir de ce ar avea nevoie rTorrent de libcurl3 SI libcurl4 care fac acelasi lucru, libsqlite SI libmysql SI sqlite (pai ori una ori alta), postfix (mail server pt rTorrent? ), ntp si ntpdate (la ce trebuie time server?), perl, perl-modules si php5 (pai folosesti perl sau php5, sunt doua limbaje de scripting diferite)...


Si daca totul ar merge brici ar fi minunat dar din pacate in realitate nu se intampla asa, ci o sa vezi cum downloadeaza jumatate din programe, le compileaza si le copiaza in directoarele care trebuie si apoi la jumatatea procesului incearca sa descarce de pe un ftp un pachet si da timeout ftp-ul sau daca nu da timeout iti raporteaza scriptul o eroare de genul "ai descarcat libpcre3 care are nevoie de apache 2.0.x dar tu ai instalat automat cu apt-get apache2.2-common dar daca dezinstalezi apache2.2 si pui apache2.0 nu o sa mai mearga libapache2-mod-php5 pentru ca apache2.0-common se pupa numai cu libapache20-mod-php5" si turbezi langa calculator.

Da, nu spun ca nu e extrem de eficient si ca poti face minuni in linie de comanda dar e ridicol cat de mult trebuie un om normal sa butoneze si sa bage comenzi si se presupune ca trebuie sa stie anumite lucruri.

Esenta la tot tutorialul ala este asta:

Ai nevoie sa
* instalezi un server Apache care e serverul prin care te vei putea conecta la interfata web a lui rTorrent
* instalezi un pachet SSL si configurezi certificat SSL ca sa mearga cu Apache ca accesul la interfata rTorrent sa fie criptat
* adaugi un user pentru ca nu e bine sa rulezi rTorrent ca root
* instalezi rTorrent
* instalezi un server FTP ca sa poti transfera fisierele pe calculator.

Asta e tot ce e de facut dar e ingrozitor cat de multi pasi sunt pt asta.

FreeBSD e mult mai smecher cu pachete gata compilate dar tot iti mai prinzi urechile din cand in cand.

[TheJudge]

@Penemue: Sunt de acord cu tine in tot ceea ce ai spus mai sus, dar un utilizator care e obisnuit cu linia de comanda nu va considera toate acestea decat o jucarie care are mai mult sau mai putin pana a fi finalizata

FreeBSD e mult mai smecher cu pachete gata compilate dar tot iti mai prinzi urechile din cand in cand.

De aceea folosesc de ani buni de zile FreeBSD in schimbul unei distributii de Linux...

[semeketh]

rtorrentul nu se instaleaza pe debian fara putin ajutor. am uitat exact care fisier era cu probleme.
iar rtorrent pe debian x64 e si mai complicat.

[Fynnon]

Asta cu rtorrent e cam complicat...

Cel mai simplu si mai usor e sa instalezi Torrentflux-b4rt

Torrentflux-b4rt - A BitTorrent and Internet Transfer Web Control Application

Si pt ca intreaba unii unde sa-l folosesti, eu de exemplu am un VPS pe care imi tin site-urile dar si un seedbox

Oricum e un tutorial foarte bun si folositor !