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

dhub wrote:

I have no idea, the only difference between what you are doing and how I install is that I tell zip to extract directly to \\nasname\Volume_1 via smb.

The only thing I can think of is that ftp is setting the permissions differently than SMB does.

What are the permissions of the files in the funplug.d/bin directory?  They all need to be executable (especially webselect which is the webserver)

I really need to make the thing a self extracting archive...

Boy I'm still struggling here...
I feel that I must be missing something glaringly obvious here!!

I've tried extracting directly to the Nas via mapped drive in windows.... and still nothing.
I've wiped the drive, tried different firmwares (I'm on 1.09 at the moment).
I've installed with fonz's funplug installed, then without.
All permissions in funplug.d/bin are executable (0777).

I can see the point at which the nas reads the fun_plug (I timed it with ffp and gaining a telnet session).
Fonz's fun_plug blinks the led just once, yours 2or 3 times, but nothing comes up...

I'm at a loss...

dhub wrote:

Can you log in with fonz funplug and run my funplug script.  I'm curious if there is any error output and if /mnt/HD_a2/fun_plug.d/bin/webselect is getting started.

As far as I can tell you're using the exact same steps I'm using successfully...

Hi dhub,

Thanks for getting back to me,
I have run the script as asked, here is the output from telnet session.
Note the funplug manager script is fun_plug.m

/ # cd /

/ # cd mnt

/mnt # ls
HD_a2     HD_a4     web_page

/mnt # cd HD_a2

/mnt/HD_a2 # ls
README.funplug_manager  ffp.log                 fun_plug.d
ffp                     fun_plug                fun_plug.m

/mnt/HD_a2 # sh fun_plug.m
fun_plug.m: /mnt/HD_a2/fun_plug.d/bin/fun_plug.common: line 15: current_default_
gateway: not found
rm: cannot remove '/mnt/HD_a2/fun_plug.d/funplugs/install/default': No such file
or directory
sh: you need to specify whom to kill
Can't bind
chmod: /mnt/HD_a2/fun_plug.d/funplugs/default: No such file or directory
fun_plug.m: line 128: /mnt/HD_a2/fun_plug.d/funplugs/default: not found

dhub wrote:

That sounds like you don't have a default gateway defined, which is rather odd and will certainly prevent the debian-reloaded install from working.  Does the command "/sbin/route -n|/bin/grep ^0.0.0.0" return anything?.

Lol, Nice catch...!!!

Because I had been having some trouble setting this up, I had wiped the drive, and reset the box's flash settings,
and in order to mess as little as possible with any settings, the only setting I altered was to enable the ftp.
I had left the box on DHCP. (I mostly have things on static, but I leave my router's DHCP server on for other visiting people's stuff, like iPhones and Psps.)

Just to test, I set the box to a static IP, Gateway, + DNS.
And your fun_plug manager booted first time!!!

So to check that I was'nt going mad, I did a reset of the box's flash, and left the LAN settings on its defaults.
I left the drive in exactly the state that had previously been working, and guess what...
Your fun_plug manager would'nt boot again, - I tested it at least 3 times, rebooting and shutting off as well, It just would'nt run.

Next, I left it on DHCP, but just set the DNS settings manually (which had been automatically set to my routers DNS (which has DNS-Relay), and it rebooted straight into your fun_plug manager again.

So I tested this a couple of more times, and the behaviour is entirely reproducable, as each time I reset the flash, your fun_plug manager would'nt work, until I manually set the DNS!!

So there we have it...

Some weird bug in the firmware's default DNS settings..., untill manually set..

Thanks for your help, and of course fun_plug manager, of which I going to play around with the debian installer..

By the way, your link the latest fun_plug manager link is to an internal IP on your network..

Last edited by tinybilbo (2011-04-13 01:29:54)

Oh, in the most recent version of funplug_manager if you put a hostname or IP address of a syslog server in /mnt/HD_a2/funplug.d/conf/syslog.server funplugs that use the log function will log their output to the syslog server (which is really handy for troubleshooting)

Ok, I got the mdadm install issue in the debian-reloaded installs firstboot script.  The debian firstboot start script now completes without hanging and results in a bootable disk image (big cheer). 

I'm going to make a copy of the funplug_manager I'm testing and put it in a release directory so future changes on my part don't cause this to break (murphy's law says I'll fat finger something when I move it and break it...)

dhub wrote:

New version, since this is the first real release with all the features I'd intended working I'll list the features instead of a change log. 

It's available at: http://ipkg.dhub.me/funplugs/release/fu … -0_147.zip

Thanks,
Will test it tomorrow...

That's actually two documentation errors.

1. The funplug_manager funplug is now called fun_plug in the archive.
2. It no longer runs on port 8000 it replaces the dlink web interface instead.

Waouh, very nice !
I try it with only one disk and get a nice debian squeeze install without headache.

About the funplug_manager webapp :
- the message says "Booting into DLink Flash Firmware Unknown in 90 seconds if no selection is made" : in fact it should be something like "Booting into 'you precedent choice' or 'DLink Flash Firmware Unknown' in 90 seconds if no selection is made", isn't it ?
- the 90 seconds is good for first time config but I'd appreciate I could change this duration for simple reboots

The debian answer time is really good : it's a lot faster than with my different chroot tests (with lenny, not squeeze).
I'm going to try it with 2 disks in RAID1...

Oh, if you want to use LVM tell it to build a small raid1 (I normally select 50GB).  It will make a second raid0 using partition 3 that can be blown away and turned into LVM physical volumes without having the dlink firmware prompting to reformat the disk on every reboot. 

I have mine configured with debian on /dev/md0 raid and one LVM logical volume formatted ext4 that's mirrored via LVM and one that's not mirrored and formatted with btrfs.  Very nice

With raid the install takes longer, it downloads the raid management tools and triggers a rebuild of the boot image as well as all the kernel modules.  Which with the DNS-323's slow processor and the amount of data takes some time.

Yeah, it shouldn't take that long.  I wonder where it failed.  The reloaded script writes a log to /mnt/HD_a2 but it generally doesn't show much. 

I'd be curious if there's a /mnt/Hd_a2/var/log/messages file since that would be the main debian log.

Hello Dhub,
Your "grub" for NAS is really interesting.
Do you know if it works on the DNS-320 ?
The main difference I see with the 323 is the Hard Drive path (/mnt/HD/HD_a2 instead of /mnt/HD_a2)...
I have not tried yet since I am careful not to brick my NAS

Also another question, it seems to run on top of the firmware, but can you make it run before ?
Meaning I want to try other builds (like native debian) without having the firmware running in background. Especially the 2.02 of the DNS-320 that makes the SMB transfers so slow and no way to roll back