Thanks kaayman. Finally found a simpel solution for my so much wanted wol feature. Works great!

I couldn't help notice however that your last line of code isn't completely correct...


should be:

echo "/usr/local/etc/busybox2 ether-wake <MAC ADDRESS OF SERVER TO BE STARTED>" >> /usr/local/etc/rcS

A simple copy and paste wil do.
Like kaayman, i hope this wil help others.

Does anyone know if this works the same in the new SDK 3.X. It appears that this is not the case on my POHD. It worked for 4018 but not for 3582. Should I add something or change one of the command lines?

kaayman was also using Squashfs firmware, so it should work for you straight away.

If not, please write more information, because It worked for 4018 but not for 3582 doesn't really say anything useful, so we could help you.

@Christian_Ku

My POHD also has firmware version 3582 (waiting for the new GUI )
It should work

Hmm, then I do not understand, I downloaded today the new BB but still get no response on the server. Nothing changed there so I assume that it is the fw of the POHD which is strange aswell as you say it works on your POHD. Verified the string in rcS and is correct. BTW, I tried to launch it manually using "busybox2 ether-wake MACADRESS" but didn't work, it says busybox not found, while I was in the correct dir. I tried busybox ether-wake etc. but then the ether-wake applet is not found. I do not understand.

Hello Christian_Ku

It works, my PlayonHD is running the last firmware 4824 and it wake-up my NAS without problem.
I just followed the instructions below and it works.
Thanks to kaayman and mikka.

Marty068

Well, I think it is safe to conclude that this problem currently is only for my particular situation. Is there any way I can try to do it manually (i.e. not via startup but via a command in the putty line). I tried this as explained above but this did not work.

I've noticed you are trying to run

"busybox2 ether-wake MACADRESS"

which is not going to work (/usr/local/etc is not within $PATH). Try "/usr/local/etc/busybox2 ether-wake MACADRESS" or "cd /usr/local/etc" + "./busybox2 ether-wake MACADRESS" instead.

Well, at the time I was in the correct directory, with ls I could see busybox2 in the directory. However it still didn't work. System says that busybox2 is not a valid command.

EDIT: ah wait, I now see that I should use "./" in front of my busybox2 command...will try that!

Now I am at a loss. Via putty I've tried the ./busybox2 etc. command and that does turn on the server. But WHY does the POHD not do this out of its own?

This is at the bottom of my rcS file:

/usr/local/etc/busybox2 ether-wake MACADDRESS

That should be enough right?! And no, the MAC Address is not wrong, I copied it straight out of the rcS file when issuing the busybox2 command manually.

I do not get it.