WOL problem on NVX

Does your WoL problem only happen when you remove the power cable from the computer for a while? If so, the issue may be in the bios of the computer (not responding to the WoL request). If the computer is in a sleep state, then the bios actions are different than power off (requiring starting a boot sequence from the power off state).

If I understand your question correctly;
The problem occurs once I remove the powercable from the computer. As soon as I re-attach the powercable, my network-card lights up (as it started to do after I activated WOL support in the BIOS). If I simply shut it off (completly) it still starts up on WOL requests.

Slasky wrote:
The problem occurs once I remove the powercable from the computer. As soon as I re-attach the powercable, my network-card lights up (as it started to do after I activated WOL support in the BIOS). If I simply shut it off (completly) it still starts up on WOL requests.

That doesn't sound like an ARP cache problem to me. An ARP cache issue would happen whenever the PC is shut off, it would not be limited to the situation when you remove the cable.

It sounds more like the computer bios is somehow "forgetting" that it is supposed to react to WoL. If this becomes a big issue for you, you could try getting a small UPS, so that the PC won't ever lose power when it is "off". This assumes that the router will handle the WoL ok even if it is re-booted.

My issue is definitely ARP related as the link light remains on at all times and looking at Wireshark's output the router doesn't know where to send the packet.

I have tried a DHCP assigned address and a fixed address but it makes no difference,

Judging by other posts on other forums the Belkin router is my problem.

mike. wrote:
My issue is definitely ARP related as the link light remains on at all times and looking at Wireshark's output the router doesn't know where to send the packet. I have tried a DHCP assigned address and a fixed address but it makes no difference, Judging by other posts on other forums the Belkin router is my problem.

I agree that your issue sounds different from Slasky's. I've also seen other posts complaining about WoL with Belkin routers.

This doesnt sound that bad of a suggestion. I'll try to see if my BIOS has any upgrades out there. And if there is any complaints on those routers, then it's most likely that its a router firmware problem.

Although the post is old, I still write. Suddenly someone will need.
I have a TP-LINK TL-WR1043N (300M Wireless N Gigabit Router) and ReadyNAS NVX Business Edition (with RAIDiator 4.2.24). Both NVX network LAN adapters are setup in the automatic load-balancing mode. When the power of NVX is turned off, the LEDs of the LAN1 (upper) light up only. The MAC address of the LAN1 network adapter I used when setting up the router. I have a static external IP address. To turn the power on of NVX over Internet I have folowing setup of the router:
- enable the DHCP server on the router and set a static local IP address for the NVX (LAN1 MAC => IP)
- enable forwarding for UDP port 9 to the local IP address of the NVX
- enable ARP binding for the NVX (LAN1 MAC => local IP)
Next, I use www.wakeonlan.me. I type my external IP address (host name), MAC of LAN1 and click the button "Wake Up my PC".
That's all, NVX is turn on.

Hi Dimonira

Thx for sharing your method. Reading through it, it appears to be aimed at allowing you to use WoL over the internet, and shouldn't be needed if the web browser is connected to the local network.

Inside the local home network I use the same method :)
Internet access is required. But this is not a problem.

In my case I want to wake up multiple devices. Since my router won't forward port 9 to a broadcast LAN address, your method would not work for me.

Though since I am ok with leaving the main NAS up 24x7, what I do instead is use the Pro's WoL add-on. That uses http to tell the Pro to send the magic packet. I already forward http to the NAS (using a non-standard port), so nothing new needed to be done there. I have browser bookmarks for each device, so it is easy to wake them.

BTW, I am not sure why you needed to do the ARP binding for this???

StephenB wrote:
BTW, I am not sure why you needed to do the ARP binding for this???

http://www.wakeonlan.me/kb/net/tplink_wol.php
Without ARP binding Wake on LAN does not work In my case.