Hi everyone, I am a new TP-Link user (I am in the process of learning how TP-Link Hardware and Software works), and I am not a networking engineer so please excuse me if I'm posting this in the wrong place. I am simply a user upgrading my home network to Omada.

I have the ER605 and TL-SG2218 so far, no APs yet (I will buy some in the future), but this isn't about APs. So essentially, I have my VPN set up so I can log in from two other locations. Everything works, Remote Desktop, encryption, DDNS and all that nice stuff, so far so good. But there is a problem, I can't wake up my Server from WAN, which kind of defeats the purpose of all this. Well, I can, but only for a couple of minutes after I send it to sleep or hibernate, oh, and the Omada controller also lives on said Server. I know this has to do with the ARP cache removing the server's IP to MAC automatic matching entry from the table, so when the ER605 unicasts the WoL messages from WAN to the Server IP, the Server wakes up as long as the Router knows which IP that MAC is bound to. I also know that in standalone mode, both the Router and Switch have ARP tables and you can easily bind IPs to MACs, you can also update ARP tables via Telnet or SSH, I've seen people do it. But if I adopt the Router&Switch into the controller, the standalone interfaces are not accessible anymore. I also can't SSH or Telnet into them as long as the Omada controller has them, and I can't for the life of me figure out how to access the ARP table from the controller. If I forget the devices so I can access the standalone interface, they're getting reset for some reason and that's a painful experience. They are not holding onto the settings that the controller has provided for them, which doesn't make sense to me as long as I know for a fact that I do have the features I need, and if I can't find them in the controller, but I have them in the standalone interface, I should be able to log out of the controller and into the interface so I can use the features I need and have, right?

Everything else works just fine, but it's important for me to be able to wake computers up from the WAN side, especially this server, and again, I -can- do that, it works, but only for a few minutes after the Server has stopped being active.

I'm hoping for some guidance on how to do this, any of the following variants will work for me:

Access the ARP table through SSH.

Access the ARP table through the controller (ideally).

Access the ARP table through the standalone interface by forgetting the device, updating ARP, re-adopting device.

Access the ARP table without forgetting the device, if there is a way.

Access the ARP table through Telnet without being forced out of the device because "it's been adopted before".

Forward the WoL messages from WAN to the Server LAN's broadcast address. 

Some other Wake on Lan procedure I'm not aware of. 

Thanks, Sergiu.