DSM-G600, DNS-3xx and NSA-220 Hack Forum

ugh. I tried to compile from source, on the dns 323 and the currently available GCC version from fun_plug has a fatal arm related bug, it cant compile libtorrent.

Bobby, are you running wtorrent with rtorrent under chrooted debian?

Not strictly related to rtorrent but try dtach instead of screen. Much more lightweight and it worked perfectly out of the box for me.

Well kramed, I can't put my hand on the fire on it not doing it at all, but comparing it to Transmission, its much more effective and lighter.

I have rTorrent (old version in lenny repos) + wtorrent running on lighttp working. Give me a night to play with rTorrent and get my settings perfect and I can write up some quick instructions how to get it all working with all the dependencies if it will help you guys.

Last edited by kramed (2009-06-06 02:16:37)

Ok, I wrote most of this a couple weeks ago. I only ended up using rTorrent for a few days as I had some crashing problems with it. Since Transmission 1.71 was released, I feel Transmission is a much better client. The web interface has improved greatly and Transmission Remote.net is awesome. Anyways, here is a quick guide. It may have some errors, let me know.

Dlink NAS 323 + Debian chroot + rTorrent + wTorrent

This is a quick guide to getting rTorrent running on your 323 with the wTorrent web interface.

There are several ways that one could get this working in theory but this is the only method that worked properly. The fun_plug custom rtorrent package did not work properly at all nor did the ipkg one work with xmlrpc enabled (which is required for wTorrent).

To run rTorrent with wTorrent, you must install Debian Linux on your 323. This takes 5-10 minutes and there is a fun plug package that automates all of the work for you. Debian is installed in a chroot environment which means it is completely seperated and self contained from the rest of the 323 software.

If you (like I was) were running Fonz's Fun Plug you will first have to remove it. This is done by deleting the funplug directory in /mnt/HD_a2/fun_plug. It is possible it can be done via Windows Explorer (or whatever) if you changed its permissions/owner, otherwise do it from the command line.

(Please be careful using rm -rf, you can destroy a Linux system with one wrong delete)

rm -rf /mnt/HD_a2/fun_plug
chmod -R 777 /mnt/HD_a2/ffp
rm -rf /mnt/HD_a2/Nas_prog

Reboot the NAS and delete the /mnt/HD_a2/ffp directory.

You are now ready to install Debian. This is very simple using the Debnas fun plug package. You can find it at http://sourceforge.net/projects/debnas/. At the time of this writing 0.5 is the latest version.

Download and extract the package to Volume_1 of the 323 (tar -jxf in /mnt/HD_a2/). There should now be linux.tar and the fun_plug in the root of the drive now.

Reboot the 323 and Debian will install, this will take several minutes. SSH will be enabled when the device boots. SSH to the 323, the default root password is 12345678. Change the password immediately with the passwd command.

Now you have a full Linux environment on the 323 with all the repository packages at your disposal. The first step is to upgrade to Debian Lenny, a newer stable version of the operating system. Edit /etc/apt/sources.list.d/etch.list, replacing the word etch with lenny. I also changed the mirror url to a North American mirror rather than the German one by removing the de. in the url. You may also rename the filename from etch.list to lenny.list if you feel so inclined.

Now we need to update the repository packages listing and upgrade to lenny:

apt-get update
apt-get dist-upgrade

This will take a while to download and then upgrade. When it is done reboot Debian. I had to reboot using the command 'reboot -f'. When Debian comes back up, it will be running Lenny. When it comes back up, update to make sure everything is current.

apt-get update
apt-get upgrade

Now we have a reasonably current Linux system to play with. Time to install rTorrent, lighttpd, wTorrent and all the dependencies.

apt-get install <package name>

Apt-get should resolve and install all the package dependencies for you.

List of Packages:

rtorrent
lighttpd
screen
php5
php5-cgi
php5-cli
php5-sqlite
php5-xmlrpc
libxmlrpc-c3
subversion
// Packages I dont think are required but installed anyways
automake
build-essential
libapache2-mod-scgi
libapache2-mod-php5
libapache2-mod-fastcgi

Dont worry about lighttp complaining that it cant be started because port 80 is in use, we will change it.

First we will modify the rTorrent settings. One thing that I do that you may also like is that I store my rtorrent settings on the NAS volume 1 and link it to /home/<user>/.rtorrent.rc

Add the following line to your .rtorrent.rc

scgi_port = localhost:5000

usually this line is already in the config and just needs to be uncommented. For this option to work, rTorrent needs to have RPC support built into the program. The rTorrent available from apt does but it is an older version.

Now edit /etc/lighttpd/lighttpd.conf

Under the server.modules section, add the following lines at the end before the ).

"mod_fastcgi",
"mod_scgi"

Change where the server stores webpages:

server.document-root       = "/mnt/HD_a2/www/pages/"

You also need to change the port the webserver runs on. 80 is used by the dlink admin page:
server.port               = 8080

Add the following section to the config:

## php support
fastcgi.server = ( ".php" => ((
"bin-path"  => "/usr/bin/php-cgi",
"socket"    => "/tmp/php-cgi.socket",
"max-procs" => 2
)
)
)

## enable communication between lighttp and rtorrent
scgi.server = (
"/RPC2" => # RT_DIR
( "127.0.0.1" =>
(
"host" => "127.0.0.1", # Ip where rtorrent is listening
"port" => 5000, # Port specified in .rtorrent.rc
"check-local" => "disable"
)
)
)

NOTE: You can change the other settings to your hearts content. I changed the directories for my logs etc, I leave this up to you.

Now lighttp and php are configured properly. Lets make the web home on your 323 volume.

mkdir /mnt/HD_a2/www
mkdir /mnt/HD_a2/www/pages

echo "<html><body>TEST<?php phpinfo( ); ?></body></html>" > /mnt/HD_a2/www/pages/index.php

Start up the web server by:

/etc/inid.d/lighttpd start

Enter the URL including the correct IP for you 323 and you should see the PHP info version page
http://192.168.1.5:8080/

If everything works all you need to do is setup nstall wTorrent into a directory under your webserver home.

Download wTorrent from http://www.wtorrent-project.org/trac/ch … ormat=zip. Unzip the archive and move the /wtorrent/ directory to /mnt/HD_a2/www/pages/wtorrent. chmod -R 777 wtorrent.

Point your browser to http://<nas ip>:8080/wtorrent/install.php and follow the prompts. After installation is complete, start rTorrent and browse to http://<nas ip>:8080/wtorrent/.

Edit: Dont run rTorrent as root!

Last edited by kramed (2009-07-04 06:20:42)

when i do a apt-get update i get the following ..

W: GPG error: http://ftp.debian.org lenny Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9AA38DCD55BE302B NO_PUBKEY 4D270D06F42584E6
W: You may want to run apt-get update to correct these problems

how do i go about fixing that

Seems to be all up and running, with minimal hitches!
Excellent guide, thank you so much

nm!  I needed to put port 8080.. it's working now!

BUT, I am wondering what I should do to shut down my NAS.. do I have to SSH into it and stop rtorrent first?  Do I need to close debian?  Or can I just press the button for 5 seconds and then when I turn it on again everything will just work?  Also I inserted a rtorrent file (that someone else made) into my init.d folder and ran "update-rc.d rtorrent defaults".


Thanks

One of the reasons I stopped using rTorrent (aside from the crashing) was the insane length of time it took to rehash torrent files. I typically have 20-30 torrents going and if they need to rehash, it takes the better part of a day to do it on the slow hardware in the 323.

Anyways, you can use a script like the one found at http://codesnippets.joyent.com/posts/show/1947 to start / stop rTorrent. Put it in /etc/init.d and chmod +x it to have it start on boot ( I dont think I am forgetting a step).

To close it down from the command line gracefully: pidof rtorrent ; kill -2 <pid>

kramed wrote:

One of the reasons I stopped using rTorrent (aside from the crashing) was the insane length of time it took to rehash torrent files. I typically have 20-30 torrents going and if they need to rehash, it takes the better part of a day to do it on the slow hardware in the 323.

Anyways, you can use a script like the one found at http://codesnippets.joyent.com/posts/show/1947 to start / stop rTorrent. Put it in /etc/init.d and chmod +x it to have it start on boot ( I dont think I am forgetting a step).

To close it down from the command line gracefully: pidof rtorrent ; kill -2 <pid>

Haven't had it crash yet, but I'll keep my eyes open for it. Realised the hashing was taking a very long time especially on big torrents. Installed the new Transmission as you recommended and the hashing is definitely a lot quicker, but I didn't really like Transmission as a client last time I used it and the feeling remains.

TylerD004 wrote:

Waltons wrote:

I didn't really like Transmission as a client last time I used it and the feeling remains.

Why exactly?

Had problems on a few trackers with Transmission not properly registering amounts uploaded or downloaded. I also prefer the integrated bandwidth scheduling and watch directories in rtorrent, though I believe you can do the same with Transmission and some scripts. In terms of interface though, Transmission's web interface and GUI are much better than rtorrent. Minor issues, I guess.

I have to admit though, it's a hell of a lot easier to get running, and appears more stable, than rtorrent.