bittorrent on networkspace

[athar]

i was wondering whether its possible 2 install bittorent on the networkspace. ne1 tried it?

[Daan]

I've tried installing some of the bittorrent packages available through ipkg, but errors when running the programs, due to incompatible versions of C libraries.

What have you tried?

[SpecialeW]

got transmission working
transmission is a torrent client

install transmission using ipkg:

Code: Select all

ipkg install transmission

then edit the config file which is settings.json
this can be either located in:
/.config/transmission/
or in my case:
/home/.config/transmission/

you can set the download directory here
as well as the rpc whitelist, which you need to edit to use the web UI.
set it to

Code: Select all

"rpc-whitelist": "192.168.*.*,127.0.0.1",

the next step is to set the system variable TRANSMISSION_WEB_HOME
I haven't made a startup script yet so I need to manually set it using:

Code: Select all

export TRANSMISSION_WEB_HOME=/opt/share/transmission/web

after this you can start the transmission deamon which is located in /opt/bin
so /opt/bin/transmission-deamon

now it is fully functional
go to the web interface by:
http://networkspace:9091/transmission/web

have fun

[CUnknown]

In my case the procedure was like this (Speciale W and me worked together on this project):

// Transmission is working now with the webinterface and startup on device startup

Install transmission using ipkg:

Code: Select all

ipkg install transmission

note: to install ipkg see: http://www.nslu2-linux.org/wiki/MSSII/HomePage

Then edit the config file which is "settings.json".
This file was located in: "/root/.config/transmission-daemon/"

You can set the download directory here (and a torrent watch dir, to download all torrents that are pasted in this dir automatically)
as well as the rpc whitelist, which you need to edit to use the web UI.
Set it to

Code: Select all

"rpc-whitelist": "192.168.*.*, 127.0.0.1",

(The loopback adres is needed to use the transmission-remote in the SSH or Telnet commandline.)

note: This assumes your internal network is on address 192.168.*.*, if not, modify accordingly.

after this you can start the transmission daemon which is located in /opt/bin
so

Code: Select all

/opt/bin/transmission-daemon

and you can control the daemon using the remote

Code: Select all

/opt/bin/transmission-remote

use the argument -h for the instructions how to use this.

now we are going to make the transmission-daemon start on device startup (also needed for the webinterface).
The device wil start transmission and start the pending downloads.

When the system starts, it has no rights to read or execute the files in /root/.
The transmission config files are in "/root/.config/transmission-daemon/" so we have to move these config files.
We have choosen the dir "/opt/share/transmission/" to move the config file directory to and we renamed the config dir to "transmission-config":

Code: Select all

cd /root/.config/
cp -a transmission-daemon /opt/share/transmission/
cd /opt/share/transmission/
mv transmission-daemon transmission-config

cleanup of the root dir:

Code: Select all

cd /root/
rm -rf .config

create a script in /etc/init.d/, we use the filename "transmission" here:
if you have installed nano (ipkg install nano !):

Code: Select all

cd /etc/init.d/
nano transmission

else

Code: Select all

cd /etc/init.d/
vi transmission

put this in the script:

Code: Select all

#!/bin/sh
# Begin $rc_base/init.d/

# export EVENT_NOEPOLL=1
# export TRANSMISSION_WEB_HOME='/opt/share/transmission/web/'

/opt/bin/transmission-daemon -g /opt/share/transmission/transmission-config/

# End $rc_base/init.d/

(save and close the file with Ctrl-o, Ctrl-x for nano. For vi: Escape-:-w-q-Enter (without the dashes))

for some reason, the export commands didn't work, so i commented them out in this file (you can omit these lines).
note: the argument -g <dir> ("-g /opt/share/transmission/transmission-config/") points to the directory with the config files.

to start the script on device startup, we have to make a symmetric link with the name "S97transm" (for example) in "/etc/rc.d/rc3.d/" to the "transmission" script in /etc/init.d/:

Code: Select all

cd /etc/rc.d/rc3.d/
ln -s ../../init.d/transmission S97transm

The next step is to let the system set the system variable TRANSMISSION_WEB_HOME on startup!
It didn't work if we put the export commands in the startup script, but it worked when we put the commands in "/etc/profile"
so open the file and add between the lines "if" and "PATH=/opt/bin:/opt/sbin:$PATH":

Code: Select all

export EVENT_NOEPOLL=1
export TRANSMISSION_WEB_HOME=/opt/share/transmission/web

note: this is not a very decent fix, so if someone knows a better place to put these system variable declarations, i would like to hear it.

If you reboot the device, transmission should be working and listed in the processtable (you can check that by using the command "ps")

now it is fully functional
go to the web interface by:
http://networkspace:9091
note: "networkspace" is the Device Name or the ip adress of your device.

have lots of fun

What makes me wonder: Are we the first to have transmission on our NetworkSpace?

[VinceDucat]

I have install transmission 1.83 with ipkg, all is good but, it seem that transmission-daemon use too many resources.


So the web-gui become unreacheable and all the Networkspace is very slow ... smb etc ...

Is other user have this problem ??

[CUnknown]

Yes, I'm having this problem too lately. When i try to download big files (approximately 9 GB) with the NAS, the transmission web daemon hangs at a certain moment. In my experience, the download continues though. With cd's (approx 700 MB) it works like a charm.

Someone here has told me that it has something to do with the old-skool OOM killer that comes with the networkspace OS. This service kills the tasks with the most badness (http://linux-mm.org/OOM_Killer quote) when the resources are out. This is a really primitive method but in most cases it wil suffice for this device.

In my opinion the OOM killer in combination with the Firefly Media Server (mt-daapd, port tcp 3689) and the twonkey media services (tcp port 9000) are the blame for the slow transfer speeds when you are transferring big files (with a non-tweaked stock device). These services are using a lot of (CPU and) RAM and when you are transferring a big file, the evil OOM killer will kill the file transfer because it scores the highest baddness rate. The details: http://linux-mm.org/OOM_Killer.

A long story short: The transmission setup (daemon and remotes) are using to much resources when downloading big files. And then... they will die.
You can change the manner of badness assigning of the OOM killer but I read that its risky and I haven't tried it myself yet.

According to this thread: viewtopic.php?f=221&t=1822 increasing the swap space might solve something, but that's still on my schedule so I can't tell you if that works. (i'm now working on a robot powered by a thin-client pc (what are the chances? ), so it can take a while for me to continue with tweaking the NAS )

And if that doesn't work, maybe nothing will work. The device isn't build for this purpose so every software addition will pushes the limits of the device and, like with all other systems, overkill causes instability. The Networkspace 1 runs with a 385 MHz CPU and 16MB RAM so it's not very powerfull.

I hope this will help you solving you problem and I hope you will share you findings.

[VinceDucat]

You're right, using twonky et transmission seems too much for this device

but uses are ~30% cpu for transmission and 10% cpu for twonky

is it a good think to use the same space /home/openshare for transmission and for the other service smb .... ???



thanks

[CUnknown]

I don't think that using the same directory (or the same partition) for transmission and sharingservices would be a problem. There will not be a sharing violation very often (they don't seize all the files at the same time). Like you found out, the transmission-daemon and the twonkey media server make up 30% of the cpu usage. That implies that the bottleneck lies with the amount of swap space. See above for the instructions for increasing this amount.

[fotonic]

Thank you CUnknown and Special W for this guide.
I followed your instructions and I got transmission working, but not very well.
I'm not familiar with linux. Sorry for the long post...

Somtimes my interet connection (ADSL) doesn't work when I download with transmission. When I paused transmission via web interface, internet was working again.
After that, I installed Transmission Remote on Mac and tried to set a limit to the upload speed, I set it to 75.
Then it worked for a while 1 or 2 days and my internet connection too.
But now Transmission Web Interface does not work again..

How did you configure transmission on yuor network for a stable use of it?
Shall I open some ports on my router?

Now I can telnet to my Lacie Internet Space;
but at login i become this:

Code: Select all

BusyBox v1.1.0 (2006.11.03-14:53+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

After login, runngin ps 
I get the line 
[code]1039 root       3952 S   /opt/bin/transmission-daemon -g /opt/share/transmissi

And now Transmission Web Interface is working again, but it don't know how long it will run fine...



-sh: Syntax error: "else" unexpected (expecting "then")
~ #
[/code]

I think I messed up my /etc/profile, which now is

Code: Select all

if
#export EVENT_NOEPOLL=1
#export TRANSMISSION_WEB_HOME=/opt/share/transmission/web
        # Do not set PS1 for dumb terminals
        if [ "$TERM" != 'dumb'  ]; then
                export PS1='\[\033[01;31m\]\h \[\033[01;34m\]\W \$ \[\033[00m\]'
        fi
else
        # Do not set PS1 for dumb terminals
        if [ "$TERM" != 'dumb'  ]; then
                export PS1='\[\033[01;32m\]\u@\h \[\033[01;34m\]\W \$ \[\033[00m\]'
        fi
fi
#export EVENT_NOEPOLL=1
#export TRANSMISSION_WEB_HOME=/opt/share/transmission/web
PATH=/opt/bin:/opt/sbin:$PATH
/etc # 
 

Are some lines at the beginning missing?
Can you post me your /etc/profile , please?

My settings.json file is:

Code: Select all

cat /opt/share/transmission/transmission-config/settings.json 
{
    "alt-speed-down": 50, 
    "alt-speed-enabled": false, 
    "alt-speed-time-begin": 540, 
    "alt-speed-time-day": 127, 
    "alt-speed-time-enabled": false, 
    "alt-speed-time-end": 1020, 
    "alt-speed-up": 50, 
    "bind-address-ipv4": "0.0.0.0", 
    "bind-address-ipv6": "::", 
    "blocklist-enabled": false, 
    "cache-size-mb": 2, 
    "dht-enabled": true, 
    "download-dir": "/home/openshare/Downloads", 
    "encryption": 0, 
    "idle-seeding-limit": 30, 
    "idle-seeding-limit-enabled": false, 
    "incomplete-dir": "/root/Downloads", 
    "incomplete-dir-enabled": false, 
    "lazy-bitfield-enabled": true, 
    "lpd-enabled": false, 
    "message-level": 2, 
    "open-file-limit": 32, 
    "peer-limit-global": 240, 
    "peer-limit-per-torrent": 60, 
    "peer-port": 51413, 
    "peer-port-random-high": 65535, 
    "peer-port-random-low": 49152, 
    "peer-port-random-on-start": false, 
    "peer-socket-tos": 0, 
    "pex-enabled": true, 
    "port-forwarding-enabled": true, 
    "preallocation": 1, 
    "proxy": "", 
    "proxy-auth-enabled": false, 
    "proxy-auth-password": "", 
    "proxy-auth-username": "", 
    "proxy-enabled": false, 
    "proxy-port": 80, 
    "proxy-type": 0, 
    "ratio-limit": 2, 
    "ratio-limit-enabled": false, 
    "rename-partial-files": true, 
    "rpc-authentication-required": false, 
    "rpc-bind-address": "0.0.0.0", 
    "rpc-enabled": true, 
    "rpc-password": "{af56542a570c6f78444ca2a3f77a1bc78db9cfc0geTu5Vp2", 
    "rpc-port": 9091, 
    "rpc-username": "", 
    "rpc-whitelist": "192.168.*.*,127.0.0.1", 
    "rpc-whitelist-enabled": true, 
    "script-torrent-done-enabled": false, 
    "script-torrent-done-filename": "", 
    "speed-limit-down": 75, 
    "speed-limit-down-enabled": false, 
    "speed-limit-up": 75, 
    "speed-limit-up-enabled": true, 
    "start-added-torrents": true, 
    "trash-original-torrent-files": false, 
    "umask": 18, 
    "upload-slots-per-torrent": 14
}
/big-disk/opt/share/transmission/transmission-config # 

Note, the ip adress of my lacie is 192.168.1.101
Of that file I think I modified the lines:

Code: Select all

"download-dir": "/home/openshare/Downloads", 
    "rpc-whitelist": "192.168.*.*,127.0.0.1", 
    "rpc-whitelist-enabled": true, 

And my transmission scritp looks like:

Code: Select all

cat /etc/init.d/transmission
/etc/init.d/transmission       /etc/init.d/transmission-old 
/etc/rc.d/init.d # cat /etc/init.d/transmission
#!/bin/sh
# Begin $rc_base/init.d/

 export EVENT_NOEPOLL=1
 export TRANSMISSION_WEB_HOME='/opt/share/transmission/web/'

/opt/bin/transmission-daemon -g /opt/share/transmission/transmission-config/

# End $rc_base/init.d/

I also had this problem:
to shutdown my Lacie I sometimes need to switch off the button at the back of the Lacie, but it doesn't switch off. In order to switch off I have to disconnect the power cable. Then when i connect the power cable again, I have to switch on the button and the Lacie turns on...


Can anyone help me???

fotonic