Wake on Lan not working when logging into Asus Router interface remotely

[MortenxDKx]

Greetings,

I've been speculating for a while about how to wake up my PC when not being home, and while I'd prefer a jumphost so my router isn't public I've decided to test out the build-in Wake on Lan tool that my Asus RT-N66U provides.

I've set up DDNS / remote access so that I can log into the router from afar and expected the Wake on Lan feature to work, since I expected it to send the packet just as if I was connected on LAN.

In this example, it works great from my phone while it is connected to my Wireless network, but if I disable wifi and run on 4G, log into the router interface via my ddns address or IP and then click Wake on Lan it doesn't do anything.

Is it just not supposed to work when connecting outside the LAN, or am I missing something? Is there a way to troubleshoot or test what's going on?

I've tried setting up VPN and connecting to that as well but with no luck.

Any help will be greatly appreciated.

Thank you in advance

 

[nigelivey]

Wake on WAN, isn't really a thing, some vendors cobble together a solution but it isn't standardised. I believe its due to NAT.

 

[bill001g]

It could be the PC, microsoft unfortunately got involved in this issue and has a bunch of proprietary "sleep" conditions that some bios manufacture partially adopted. These feature some times cause WoL to not function correctly. Check the bios setting in the machine.

What you can do is load wireshark onto your machine and see if you are getting the packet. Your machine will still receive the packet even though it is actually active. You can also see the packet on other machines on the lan since it is sent to all machines not just the one that is off. So you could load wireshark on different machine than the target machine.

Wireshark should actually decode the packet so you can see the mac address of the machine to wake

If you get the packet you know at least the router is functioning correctly, you need to verify the mac address.

If the packet has the proper mac address then it has to be some stupid setting in the bios messing it up.