Transmission installed and running on 1.7.1
Posted: Mon Mar 09, 2015 4:19 pm
Hey folks, wanted to give something back to this amazing community so I thought I could show you how I got Transmission Torrent Client working on my WDR3600 running 1.7.1 latest ispy build.
1. I followed this guide http://wiki.openwrt.org/doc/uci/transmission but I omitted the installation of transmission-cli and transmission-remote due to storage constraints. I decided to install it straight to the router's internal memory and use an external USB as the download destination.
2. Once I managed to succesfully install it, the very useful plugin Services Manager shows the newly installed Transmission service ready to be autostarted if you so desire. I don't, simply because this amazing plugin gives me the freedom to start and stop it whenever i desire, without using unnecessary router resources. If you also have the Services plugin, it should look like so:

3. Now here's the kicker. I knew if I used OpenVPN to connect, I could access the Transmission Web Service without issues. Thing is, I wanted to be able to access it through the DDNS host assigned to my Dynamic IP, and no matter how many rules I tried, I'd always get ERR_CONNECTION_REFUSED. So, I decided to edit the /etc/config/firewall and add the following rule:
I restarted the firewall and voilá, I could access my Transmission using the DDNS hostname associated with my Dynamic IP.
Bear in mind, if you plan on doing this, it is essential that you enable the following option either in the transmission or settings.json file:
This enables basic authentication that you can also set up within the same file in the fields and
Hopes this helps anyone interested in setting up their own torrent client without having to turn on a computer.
Cheers!!
UPDATE: In my case it worked with the rules I added, but if you get no peers, you can always add the following to the firewall script:
1. I followed this guide http://wiki.openwrt.org/doc/uci/transmission but I omitted the installation of transmission-cli and transmission-remote due to storage constraints. I decided to install it straight to the router's internal memory and use an external USB as the download destination.
2. Once I managed to succesfully install it, the very useful plugin Services Manager shows the newly installed Transmission service ready to be autostarted if you so desire. I don't, simply because this amazing plugin gives me the freedom to start and stop it whenever i desire, without using unnecessary router resources. If you also have the Services plugin, it should look like so:
3. Now here's the kicker. I knew if I used OpenVPN to connect, I could access the Transmission Web Service without issues. Thing is, I wanted to be able to access it through the DDNS host assigned to my Dynamic IP, and no matter how many rules I tried, I'd always get ERR_CONNECTION_REFUSED. So, I decided to edit the /etc/config/firewall and add the following rule:
Code: Select all
config remote_accept 'transmission'
option proto 'tcp'
option zone 'wan'
option local_port '9091'
option remote_port '9091'
Bear in mind, if you plan on doing this, it is essential that you enable the following option either in the transmission or settings.json file:
Code: Select all
"rpc-authentication-required": true,
Code: Select all
"rpc-password": "password",
Code: Select all
"rpc-username": "username",
Cheers!!
UPDATE: In my case it worked with the rules I added, but if you get no peers, you can always add the following to the firewall script:
Code: Select all
config remote_accept 'transmission_2'
option proto 'tcpudp'
option zone 'wan'
option local_port '51413'
option remote_port '51413'