WAKE addon problem

super-poussin wrote:
if I have time , but no guarantee

Thank you so much for even considering it! It would be a great benefit to the community!

Cheers

Matt

+1 for the English idea too please! :oops:

Babel translate doesn't work too well when passing php through it. I'm slowly getting an idea of the translation but fear I could really make a mistake relying on something like that. D

Could do with a bit of help please!

I've set up Wake 1.1, and added the MAC addresses for the other PC's on my network.

I've configured the PC's ethernet cards to allow/accept magic packets, but the PCs are not waking up. What could I have done wrong or missed, should I be adding an ip address somewhere?

I get no error message via Wake, it seems to say all went well. (I ran the page through Google translate to understand what the message said.)

The PC with the MAC address XX:XX:XX:XX:XX:XX was awake! If you want to use the remote control, thank you wait a moment while your machine starts. You can close this window.

Got this sorted, t'was a PEBCAK issue. ;)

Thanks for this addon SP, should save me a few quid over the year, so there will be a donation coming your way in return. :thumbs up:

Thanks for the Wake add-on, this is working great (internally).. I am a advanced user and knows what port routing/forwarding/firewall does. When i forward port 80 to my computer, its working great. My web server is broadcast to the Internet. But when i forward 443 to my ReadyNas Duo i cannot connect to the admin portal or to the /wake website.

What can this be? i can connect to the internal address but it seems like the readynas duo does talk to my router. It also seems my router does no routing to my readynas but it does route to my pc when i check a default 443 or 80 port to my pc.

Sounds this familiar to someone, though it is an old thread..

Can someone help?

and fixed :)

when i setup my readynas to a DHCP address the problem was solved. The static address had a problem (i think) i could not configure the gateway address, that was the problem i suppose..

can anyone confirm this? or have a similar problem or solution for static addresses?