Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
This should evolve into a simple step by step tutorial how to install fun_plug 0.7 and how to work with it.
If you cant understand any of these instructions, know that some information is missing or inappropriate just write me and I will update this guide.
I'm currently doing this on DNS 343, but it should work also for many other devices.
Special thanks to fonz, who created ffp, to Mijzelf for his abi script and to uli for his great tutorials.
In following I quoted Ulis tutorial from here: http://nas-tweaks.net/40/installation-o … many-more/ wherever the procedure is the same.
I also used a lot of this German tutorial as base:
http://wolf-u.li/4523/hdd-installation- … -geraeten/
Thanks to uli for providing this to us.
I dont take any responsibility for anything that happens to your hardware due to this guide.
What you do always contains low risks of data loss or if executed wrong of unit damage.
You have to take this risk for yourself.
Step 1: Figuring out which ABI to use
The older devices like DNS 323 does not support the new Application Binary Interface. So of fun_plug 0.7 there are 2 versions, one called oarm and one called earm.
o stands for old and e for embedded, so earm (often also just called arm) is the one to prefer if it is available.
In this step we want to figure out which Versions are supported by your NAS.
Download the following Skript: http://pizzard.de/testabi.tar.gz
Afterwards unpack it directly to the first hard drive of your NAS. Make sure that the files are not opened in windows (that will destroy newlines) or at any time placed on a windows disk drive in unpacked state (this will destroy the executable bit).
Afterwards you placed the 3 files fun_plug, testeabi and testoabi in the right position,
reboot the NAS by holding down the power button 5 seconds or via the web interface (”Tools” -> ”System” -> ”Reboot”). This causes the NAS to go and find the file fun_plug on Volume_1 and execute it.
On my NAS it was Maintenance -> System -> Restart.
Afterwards you will find a file called supported_abis.log on your first volume.
Open it and look inside.
If your NAS is one of the newer generation, you'll find the following inside:
That means both abis are supported and you can use earm / arm, if there is only the 2. line inside,
you have to use oarm.
If the file does not exist, something has gone wrong and you have to check the file permissions of the fun_plug script. Is it really executable?
If the file exists and is empty, none of the abis is supported by your NAS. This should not happen, in case it does report this here.
Now delete all 3 files from your NAS, so you can start with the real installation of ffp.
NOTE: In the following instructions there is for technical reasons again a script called fun_plug, but do not mix the two up!
Delete the script for abi test now, you will never need it again!
2. Step: Downloading the right package
Depending on the arm you figured out before, download the appropriate fun_plug package:
arm is here:
and oarm is here:
Download the following files:
- fun_plug (this is a text file, you probably have to right-click to save it to disk)
NOTE: This does not work for: D-Link DNS-320/DNS-325/DNS-345, for these you need a different script here.
- fun_plug.tgz (this is a 10 MByte “tarball” file, roughly the Linux counterpart of a Zip file)
Place a copy of both files in the topmost directory of Volume_1 of your NAS using Windows Explorer (see screen shot of what shared network drives looks like in Explorer, or alternatively use Samba or FTP).
Then reboot your NAS (like above).
Now all preconditions are fulfilled and you can start with the installation and configuration itself.
3. Step: Verifiying fun_plug Installation
After rebooting your NAS there should appear the following:
WARNING: This may take some time. If both (the folder ffp and the .tgz archive) are present, your NAS is still working! Just wait for the *.tgz folder to vanish. When it doesn't vanish after some minutes, then sth. went wrong.
If these things appear like that, your installation was successful so far.
Otherwise don't continue, just look into the ffp.log what went wrong and get some help in #irc or here.
Perhaps you have to put the File on Volume2? Perhaps you mixed up abi and oabi?
4. Step: Connect via telnet
Now we want to connect to the NAS via telnet.
Under Windows there is a Tool called putty for this, which can be found here: http://www.chiark.greenend.org.uk/~sgta … nload.html
Download putty.exe and simply execute it.
Afterwards type in the IP-address of your NAS and choose telnet as connection method and click on Open.
Now your NAS should welcome you with at least the following prompt:
Congratulations, we are on it!
But now we want to replace this very unsafe telnet connection with a safe, password-encrypted ssh connection.
Therefore we need an appropriately configured user root, what we we do with the following commands:
usermod -s /ffp/bin/sh root mkdir -p /ffp/home/root/ sed -ie 's#:/home/root:#:/ffp/home/root:#g' /etc/passwd pwconv
Afterwards we'll set a new secure root password and then test it by logging in as root.
This may look like this:
sh-4.1# passwd Changing password for root Enter the new password (minimum of 5 characters) Please use a combination of upper and lower case letters and numbers. New password: Re-enter new password: passwd: password changed. sh-4.1# login dlink-9FF13F login: root Password: No mail. root@dlink-9FF13F:~#
As login type root and as password your newly set password. There isn't anything shown while typing your password, this is correct.
If you were able to login, we'll now store this configuration, otherwise set a new password with passwd.
wget http://wolf-u.li/u/172/ -O /ffp/sbin/store-passwd.sh store-passwd.sh
The first command will download this script, the second executes it.
If you get “wget:bad address `wolf-u.li` while executing the first command, the network settings of your NAS are wrong.
Verify a working internet connection for your NAS and try again.
The Result should look similar like this:
root@dlink-9FF13F:~# wget http://wolf-u.li/u/172/ -O /ffp/sbin/store-passwd.sh --2012-02-26 19:28:06-- http://wolf-u.li/u/172/ Resolving wolf-u.li... 2a01:488:66:1000:53a9:2a6a:0:1, 220.127.116.11 Connecting to wolf-u.li|2a01:488:66:1000:53a9:2a6a:0:1|:80... failed: Address family not supported by protocol. Connecting to wolf-u.li|18.104.22.168|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://wolf-u.li/downloads/3779-d2ee273e64e3c3166139f56fbb100067/store-passwd.sh [following] --2012-02-26 19:28:06-- http://wolf-u.li/downloads/3779-d2ee273e64e3c3166139f56fbb100067/store-passwd.sh Connecting to wolf-u.li|22.214.171.124|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 875 [application/octet-stream] Saving to: `/ffp/sbin/store-passwd.sh' 100%[=======================================================================>] 875 --.-K/s in 0s 2012-02-26 19:28:06 (9.87 MB/s) - `/ffp/sbin/store-passwd.sh' saved [875/875] root@dlink-9FF13F:~# store-passwd.sh Saving Userdata to flash storage Mounting flash ... Updating files ... /sys/mtd1/passwd /sys/mtd1/group /sys/mtd1/shadow /sys/mtd1/smbpasswd /sys/mtd2/passwd /sys/mtd2/group /sys/mtd2/shadow /sys/mtd2/smbpasswd /mnt/HD_a4/.systemfile/AccountFile/passwd /mnt/HD_a4/.systemfile/AccountFile/group /mnt/HD_a4/.systemfile/AccountFile/shadow /mnt/HD_a4/.systemfile/AccountFile/smbpasswd Unmounting flash ... root@dlink-9FF13F:~#
Now your settings for root are saved and we can switch to ssh in the next step.
Step 5: Deactivating telnet, activating ssh
Now activate the ssh daemon on your NAS with this commands:
chmod a+x /ffp/start/sshd.sh sh /ffp/start/sshd.sh start
The first command makes sshd executable by setting the executable bit, the second command start the daemon.
This may take a while, because on first run it generates key pairs. Therefore some funny looking images are printed.
At last, is responds
Now DO not close the telnet session to prevent from locking yourself accidentally out of the machine, open a second instance of putty.
Now type again the IP-address of your NAS and select SSH as connection mode.
next it prompts you for your login, this is root and the password is your password from above.
At first connect, the following will also appear in between:
The authenticity of host '126.96.36.199 (188.8.131.52)' can't be established.
ECDSA key fingerprint is f9:ff:83:00:5f:7b:72:c4:9c:72:ef:72:e7:b1:58:23.
Are you sure you want to continue connecting (yes/no)?
This is normal, because you ssh client has never seen this device before, so just type yes.
If everything worked well we can now disable telnet (we have ssh now) with this command:
chmod -x /ffp/start/telnetd.sh
Afterwards, close both connections by just typing exit (for the first connection you have to do this twice) and reboot your NAS once more.
Step 6: Congratulations
You are done!
fun_plug 0.7 is now successfully installed on your system.
Now you can start installing packages via slacker, compiling your won packages or do a couple of things with your NAS.
Just look around in this forum, visit http://dns323.kood.org/howto:ffp or in irc #funplug on FreeNode
Last edited by pizzard (2012-02-26 21:52:37)
Is there a list somewhere (on the Wiki maybe?) which shows which NAS supports EABI, and which only supports OABI?
If not, maybe we should create one?
It can also be firmware dependent. All ZyXEL nasses are OABI. But the firmware 4.40 beta for the NSA310 supports EABI.
I don't believe pwconv is supposed to give me this error is it?
"pwconv: failed to change the mode of /etc/passwd- to 0600"
Ideas? On a DNS-320
<edit> Issue solved, see edit below: </edit>
Having some trouble with the install. I was using fun_plug 0.5 until over the weekend I had some issues (detailed here: http://forum.dsmg600.info/viewtopic.php?id=7114). So I decided to try to install 0.7. I ran the supported abi's checker and it told me that my 321 supports both oabi and eabi. I downloaded the fun_plug file and fun_plug.tgz file from the abi link and put them both in my Volume_1 directory. On reboot, nothing happened, the tgz file is still present and the ffp.log and ffp directory were not created. So far it's been about 10 minutes since the reboot, so I would think it should have finished by now.
EDIT: Looks like windows added a .txt to the fun_plug file. I removed the extension and the install seems to have worked.
Last edited by turkvu (2012-05-22 02:32:38)
Thanks pizzard for the tutorial. I'm quite nubbie for linux but it worked perfect!
Now I have just a question: according to some suggestions, one should install cleanboot first thing, to avoid disk/data problems. But I can not find a version that works with ffp07. Does it exist? Is it recommended to work ffp07 without it? Or it would be better to remove it and install ffp05 that works with cleanboot?
[** EDIT on Jan 17th **]
I have installed cleanboot in ffp07. See this thread -> http://forum.dsmg600.info/viewtopic.php?id=7118
Last edited by beto6971 (2013-01-18 06:13:29)