@sleibo I am not having success either.  On my Netgear R7000, this worked just fine.  I think part of the problem is this.  On the R7000, when I VPN in, the router assigned my remote pc/laptop an IP address within the same range as the home computer I want to turn on using WOL. For example, the home PC's IP is 192.168.1.125 and the remote pc/laptop's IP is 192.168.1.155

However, with TP-Link, I see that the IP address assigned my remote pc/laptop is NOT in the same range as the home comuputer I want to turn on.  For example, the home PC's IP is 192.168.1.125 and the remote pc/laptop's IP is 175.145.0.121 

@Winger13   I eventually gave up on this.  I don't think the magic packet will pass through the VPN.  So the alternative is to wake the PC without the VPN.  You can of course use the VPN for all subsequent contact.

@sleibo Thanks for the response.  As I stated, WOL worked over OpenVPN on my Netgear R7000 router for many years before I had to replace the Netgear, so this points to a setting(s) in the TP-Link router.

 Old thread but I wanted to chime in because it is still the top rated search result for "wol over vpn". Yes the WOL magic packet is definedOld thread but I wanted to chime in because it is still the top rated search result for "wol   over vpn". Yes the WOL magic packet is defined

Yes the WOL magic packet is defined within the constrains of layer 2 but this does not mean it cannot be contained inside a network and transport protocol entity which can then be used to route it across the VPN.