|Курилка||Версия на русском|
This text was made from instruction mentioned in the 1st post of conference Обсуждение NAS D-Link DNS-325 (thanks Panchenko for his work). This instruction edited for NAS D-Link DNS-315 that different from DNS-325 in central processing unit (CPU). Familiarity with Panchenko's instruction also will be good because something themes described more detailed in it and something—differently.
Because of mount point of Volume_1 (directory which seen from LAN) in DNS-315 is different from DNS-323, it's need to change all paths in fun_plug from /mnt/HD_a2/ to /mnt/HD/HD_a2/. For example, change FFP_PATH=/mnt/HD_a2/ffp to FFP_PATH=/mnt/HD/HD_a2/ffp.
Also, it may be useful to add commands to make link /mnt/HD_a2 to /mnt/HD/HD_a2/ and adding permissions to read file /dev/urandom for “all” users into fun_plug.
#!/ffp/bin/sh PATH=/ffp/sbin:/ffp/bin:/usr/sbin:/sbin:/usr/bin:/bin # Create symbolic link /mnt/HD_a2 to point to /mnt/HD/HD_a2 ln -snf /mnt/HD/HD_a2 /mnt/HD_a2
Command “ln -snf /mnt/HD/HD_a2 /mnt/HD_a2” can be added into fun_plug and words about installing fun_plug.local may be skipped. For example:
# create /ffp link echo "ln -snf $FFP_PATH /ffp" ln -snf $FFP_PATH /ffp # *** Create /mnt/HD/HD_a2 link echo "ln -snf /mnt/HD/HD_a2 /mnt/HD_a2" ln -snf /mnt/HD/HD_a2 /mnt/HD_a2
2014/09/02: Note: Perl programming language that depend on uClibc-0.9.33_git-arm-1.txz already installed with fun_plug.tgz. May be, it is no need to install it at all. Not checked.
To work with command line on NAS you'll need some program that works with telnet or SSH protocols. You can use PuTTY or standard Windows utility telnet.
mv fun_plug.local /ffp/etc
chmod a+x /ffp/etc/fun_plug.local
funpkg -i uClibc-0.9.33_git-arm-1.txz
funpkg -i curl-7.21.4-arm-1.txz
funpkg -i Transmission-2.83-arm-1.txz
chmod a+x /ffp/start/transmission.sh
chmod a+r /dev/urandom
tr_crypto error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not seeded (crypto.c:113):
It's possible that the file /dev/urandom created on each boot. So it is good idea to add nobody's permissions adding into fun_plug that runs every NAS boot. For example:
# create /ffp link echo "ln -snf $FFP_PATH /ffp" ln -snf $FFP_PATH /ffp # *** Add rights for others to urandom device echo "chmod a+r /dev/urandom" chmod a+r /dev/urandom
Wait for a while so Transmission can shutdown cleanly.
Configuration file can be found on Volume_1 and has name .transmission-daemon\settings.json. Directory .transmission-daemon has attribute “hidden” set.
Some parameters (see also Transmission Support and Development):
|Parameter||Default value||Description (may be some inaccuracy)|
|message-level||2||Verbosity of transmission messages. 0 = None, 1 = Error, 2 = Info, 3 = Debug|
|preallocation||1||Set disk preallocation method. 0 = Off, 1 = Fast, 2 = Full (slower but reduces disk fragmentation)|
|rpc-enabled||true||Permit access from LAN (true) or deny (false)|
|rpc-port||9091||Port number for access to Transmission WEB interface or control daemon by third-party program. For example, if NAS resides at address 192.168.1.196 and value of port equals 9091, you need type http://192.168.1.196:9091 in your browser address bar|
|rpc-authentication-required||false||Use login/password pair (true) or no (false) for remote access|
|rpc-username||empty string||User name (login) for remote access|
|rpc-password||password hash||Password for remote access. You enter it as plain text. After start Transmission will change it to hash sum|
|rpc-whitelist-enabled||true||Use (true) on do not use (false) “whitelist”|
|rpc-whitelist||127.0.0.1||Comma-separated list of IP addresses that permitted remote access when rpc-whitelist-enabled = true. To permit access from computers that address starts with 192.168.1. add this as “127.0.0.1,192.168.1.*”|
|umask||18||Sets transmission’s file mode creation mask. See the umask(2) manpage for more information. Users who want their saved torrents to be world-writable may want to set this value to 0. Bear in mind that the json markup language only accepts numbers in base 10, so the standard umask(2) octal notation “022” is written in settings.json as 18.|
You can control Transmission daemon using WEB interface at URL: http://<IP_address_NAS>:<port> or you can use third-party tool. For example, Transmission Remote GUI.
Partially quoted text found at DSM-G600, DNS-3xx and NSA-220 Hack Forum. Original updated by KyleK (2013-09-24 21:32:34).
Latest version: 2.83.
can't load library 'libevent-2.0.so.5'
Download library from http://downloads.zyxel.nas-central.org/.../0.7/arm/libevent-2.0.16-arm-0.txz and install it with command
funpkg -i libevent-2.0.16-arm-0.txz
WARNING: It was observed that Transmission 2.83 hangs up when adding new torrent for downloading. (now observed on rutracker.org only). It is recommended to not install this version or downgrade to 2.82 using same procedure as below.
(wait for a while so Transmission can shutdown cleanly—you can admire by work of top command)
funpkg -u Transmission-2.83-arm-1.txz