Transmission Setup on the ReadyNAS NV+/Duo:

[VMColonel]

Preface:
I wasn't able to find this all in one place, and I ran into a few snags here and there (Nothing a quick google wouldn't cure)

I assume the x86 installer would be similar, but I don't have a unit to test with, so if someone does have one and wants to add comments, I can correct.

What you will need:
Transmission binary (I'm using a DUO, so Sparc for me, version 2.04)
Get it from here: http://www.readynas.com/forum/viewtopic.php?f=47&t=24271

SSH Root Access (Both Sparc and x86):
http://www.readynas.com/?p=4203

Instructions:
1) Login to FrontView:
a) Open a browser to https://<IP_OF_NAS>
b) Accept SSL warning
c) Enter your credentials (Login: Admin Password: <admin pass>)

2) Install the SSH addon:
a) Login to FrontView
b) Click on System -> Update -> Local tab (at the top) -> Choose File
c) Select "EnableRootSSH_1.0.bin"
d) Click on "Upload and verify image.."
e) Accept warning (OK) and WAIT
f) Click on "Perform System Update"
g) Shutdown and reboot the device. (This may take a few minutes to come back online)

When the power light on the NAS stops blinking:

3) Install the Transmission addon:
a) Login to FrontView
a) Click on System -> Update -> Local tab (at the top) -> Choose File
b) Select "Transmission_2.04.bin"
c) Click on "Upload and verify image.."
d) Accept warning (OK) and WAIT
e) Click on "Perform System Update"

4) Disable the Transmission Daemon:
a) Login to FrontView
b) Click on System -> Installed Add-ons -> Transmission
c) Take the check out of the box
d) Click "Save" and WAIT.
e) Click "OK" after it has successfully stopped.

5) Use PuTTY (Or your SSH terminal of choice) to remote into the box.
a) Download putty here: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

6) Edit the settings.json file for the Transmission Daemon (or Service)
a) SSH into the NAS
b) Backup the config file
# cp /addons-config/Transmission/transmission-daemon/settings.json /addons-config/Transmission/transmission-daemon/settings.json.default
c) Use your favourite editor to make changes to the config file:
# vi /addons-config/Transmission/transmission-daemon/settings.json

To bypass throttling, I changed the port, disabled DHT, and forced protocol encryption. So far, I'm downloading at about 60kb/s, so it seems to be working. For more information please see: http://www.pervices.com/docs/throttling_tech_brief.pdf
Old Config:
"peer-port": 51413,
"dht-enabled": true,
"encryption": 1,
"rpc-password": "{d15b146a3063b3ade7d0fecaa9602218a327a8c8gOoal64v",

New Config:
"peer-port": 1723,
"dht-enabled": false,
"encryption": 2,
"rpc-password": "test123",

Directories, Bandwidth, Scheduling, Peer Management, Ports, Proxy, Remote Control and Advanced settings can all be tuned from this file, for more information see this page: http://www.readynas.com/contributed/super-poussin/Transmission-Parameters.htm

NOTE:
Changing the web password (rpc-password) may also require changes to /addons-config/Transmission/transtop.sh and /addons-config/Transmission/transtart.sh
Old Config:
TRANSOPT=" localhost:8181 -n admin:password1"
New Config:
TRANSOPT=" localhost:8181 -n admin:test123"

7) Re-enable the Tranmission client:
a) Login to FrontView
b) Click on System -> Installed Add-ons -> Transmission
c) Put the check back in the box
d) Click "Save" and WAIT
e) Click "OK" after it has successfully started

8 ) Ensure that external port is open remotely:
a) Open a browser and go to http://www.t1shopper.com/tools/port-scan/
b) Beside "Scan this list of port numbers" put in the value of "peer-port" from step 6 (In our example, enter 1723) and click "Scan"
c) The report should say "<Your IP> is responding on port 1723 (pptp)."
d) If it isn't check your router settings

9) Add torrents through the Web Interface:
a) Open a browser and go to http://<IP_OF_NAS>:8181/transmission/web/

GENERAL NOTES:
The Web Interface (http://<IP_OF_NAS>:8181/transmission/web/) has a default username of "admin" and a default password of "password1" unless changed in step 6.

Create a new torrent using: https://<IP_OF_NAS>/ctransmission/

[mdgm]

Good guide. However you don't need to use SSH (feel free to use SSH though if you are comfortable with using it). super-poussin has deliberately placed the config files so that using SSH shouldn't be necessary. It's still handy to have SSH access just in case.

You can login to CIFS/SMB (windows file sharing) as admin and access the addons-config share (it may require a reboot to create this) or open the C volume, open the addons-config folder and edit the relevant files using Notepad++ (don't use ordinary Notepad as it'll stuff up the formatting) on a Windows Machine or you can use TextEdit to edit the file on a Mac.

By CIFS/SMB, On a Windows machine, I mean browsing to the NAS via My Network Places or typing \\ip.address.of.nas in Windows Explorer.

On a Mac, In the Finder Click Go > Connect to server (or type Command-K) and type smb://ip.address.of.nas and then click Connect.

[VMColonel]

You can login to CIFS/SMB (windows file sharing) as admin and access the addons-config share (it may require a reboot to create this) or open the C volume, open the addons-config folder and edit the relevant files using Notepad++ (don't use ordinary Notepad as it'll stuff up the formatting) on a Windows Machine or you can use TextEdit to edit the file on a Mac.

Thanks, good to know, perhaps I should have just made a general "installing any plug-in" post and forked from there. Is this how most plug-ins work, or do the majority force you to SSH in, or have a web interface?

In all seriousness I had no idea the ReadyNAS was this robust (Impulse buy), but now seeing it in action, I'm thinking I should have picked up an Ultra or something x86 based, I would love to run a VM in there with my vent server, that would pretty much free up this quad-core Phenom that the ReadyNAS has almost replaced. (Except maybe the transcoding)

[mdgm]

Most add-ons work this way. If not, you can ask the add-on developer if they'll make the necessary changes. It's not hard to take a look at super-poussin's code for the "addons-config" share and do likewise.

Though the Ultra is not on the HCL for VMWare it should work fine. It runs the same OS as compatible devices and has both NFS and iSCSI.

Performance wise, ReadyNAS Pro > ReadyNAS Ultra 6 > ReadyNAS Ultra 4 > ReadyNAS NVX. The NVX Pioneer and Pro Pioneer lack some features of the business units, but still have NFS and iSCSI (iSCSI is available via an add-on for the Pioneer on 4.2.13 or greater).

Some adventurous types have even run VMs directly on a Pro (this definitely requires a fair bit of SSH work) and is unsupported.

[kimme]

Thanks for this quick setup guide for installing Transmission.

[mcarora]

Hi

Quick question from a noob when it comes to readynas systems: I have a duo and a much older version of transmission (have not used it in a while), what is the best way for me to update my version? As I mentioned I am a noob, so I am guessing that I would nee to uninstall the old version from my FrontView and then install the latest version? Can someone confirm if that is right?

Thanks

[mdgm]

Would've been better to start a new thread for this issue. What version of RAIDiator and what version of the Transmission add-on (you can check the version under Services > Installed Add-ons)? You might wish to contact super-poussin e.g. via PM as he can best advise you on what to do.

[MTW]

Thanks for the guide, it's what I used to install it. Thought i'd just post up exactly what I did in a mini-guide as it seems a bit simpler not using the SSH route.

This is how I installed Transmission 2.11, using CIFS/SMB. I am on a ReadyNAS NV+ (x86) on the RAIDiator 4.1.6 firmware.

Download the latest Transmission from: http://www.readynas.com/forum/viewtopic.php?f=47&t=24271

How to install Transmission
Open a browser:
1. Log in to FrontView ("https://IP-address-of-nas")
2. It will ask for your username & password, enter them.
3. Navigate to System -> Update -> Local tab - Choose File
4. Select the "Transmission_x.xx.bin" file you just downloaded
5. Click "Upload & verify image"
6. It will take a moment, then click "Perform System Update"
7. Navigate to Services -> Installed Add-ons then scroll down to the new "Transmission" entry and un-tick the box
8. Click Save

Open Windows Explorer (Or whatever you use to browse folders on your computer):
9. Go to the root directory of your NAS (If you havn't done this before/don't know how to - read the section "To access the root directory of your NAS:" further down)
8. Navigate to /addons-config/Transmission/transmission-daemon/
9. Create a copy of settings.json (I called mine settingsBACKUP.json)
10. Edit settings.json (I use Notepad++ for this) and edit the settings as necessary
11. If you changed the rpc-password you must also change it in /addons-config/Transmission/transtop.sh & transtart.sh

Open a browser:
12. Log in to FrontView again
13. Navigate to Services -> Installed Add-ons then scroll down to Transmission and tick the box

An explanation of all the options in settings.json can be found at: http://www.readynas.com/contributed/super-poussin/Transmission-Parameters.htm

To access the root directory of your NAS:
Open a browser
1. Log in to FrontView
2. Navigate to Security -> Security Mode
3. Select "User" and wait a minute or so, then close the browser.
4. Open a cmd prompt (Windows Key + R, then type cmd and hit Enter)
5. type "net use t: \\ip.address.of.nas\c /user:admin"
It should say "The command completed successfully."

Now you will have the root of your NAS accessible from My Computer.

If you are looking to access Transmission from outside of your network, you will need to take note/change the rcp-port in settings.json and make sure that port is open/redirects traffic to your NAS via your router.

[Gandhionaharley]

Just wanted to say thanks to all posters for the step by step guides.

Being a total noob I used bits from few posts here and I can now log in.

All I have to do is start a torrent now!

Cheers.

[poddster]

Hi - I've read through this thread and followed the instructions, but I'm not able to copy or alter the settings.json file. Each time I try, I'm told I don't have permission. This occurs from my Mac and from a Linux VM. This seems to be the only file affected, and Properties/Get Info tells me that I have full admin rights over the file. I made sure to stop the Transmission add-on. Does anyone have any ideas what I need to try next?? Thanks

[poddster]

For anyone with the same problem that I had... the solution was the change the Security Mode in Frontview from Share to User, update the settings.json file, then change the Security Mode back to Share.

[TheKoKo]

Hi everyone.

Great post on the setup instructions. I seem to be running into two issues regardless of what I do. My setup is as follows. ReadyNas Ultra 4, RAIDiator 4.2.15 and Transmission 2.14(b) (x86)


I followed the instructions up until I needed to SSH into the NAS, then I hit issue #1:
#1. When I use putty to SSH into the ReadyNAS, it asks for my username. I type admin, then hit enter. Afterwards, it asks for my password. I enter my password and hit enter. At this point, Putty just quits as if it was closed. Retried a few times with the same outcome. So I modified the files using the CIFS access method. Is SSH not enabled? Why does it keep quitting?

Once the config files were modified. I tried to launch transmission and hit issue #2.
#2. trying to restart the Transmission add-on, i check the box and hit save, the NAS pops up a window saying that "Transmission Failed To Start". However, the green "led" on the right hand of the add-on pane is on and the check mark stays. If I refresh the screen (using the refresh button at the top of the FrontView), the box is now unchecked, but the green "led" is still on. If I restart the NAS, its off again.

I would greatly appreciate any input/ideas/solutions.

Thank you...



----- UPDATE -----

Solution to ISSUE #1.
I was doing a little bit of research and came up with the solution to why putty would suddenly quit when trying to access the NAS using SSH.

When logging in to the NAS, do not use admin/password, instead, use root/password. This will grant you access to the ROOT of your NAS.

[dhodgin]

I have a similar problem as above i can install and startup the addon just fine and it works perfectly.

As soon as i shut it down once and change the settings.json file and the startup and shutdown files to modify the default password i can no longer start the service. it says it starts it and then after 3-5 seconds the light turns off on the installed addons page of frontview and launching the transmission web interface just gives a server not found error. the services wont restart once i change those 3 files.

I am editing them in visual studio so maybe its a encoding issue on the text files after resaving?

------------- update
i was editing my files in visual studio and it was resaving the files in a different codepage.
using notepad++ to edit the files preserved ANSI encoding and i can start and stop the service repeatedly now
it must cause it to crash on boot if the files arent encoded as ANSI


-

[mechael]

Hi,

I've followed the first post and installed "Enable Root SSH Access" then realized it wasn't needed. Is there any way to remove it? I don't want to jeopardize the warranty of my NV+.

Thanks.

Michael

[No1Joker]

I've just completed this setup.

Anyone getting the "Service failed to start" message at the end of the setup. Make sure your blocklist.sh has the correct password too, if you changed it in step 6.

T