Posted under Library
Permalink
The information on this is firmware version dependent and not all correct.
However, This post appears to have the correct update for the telnet wol command which is needed to make it work.
The correct options for wol to enable wol from the wan are
wol fromWan any
wol fromWan off
wol fromWan on
In my case the correct one is the any option, wol fromWan any. My surmisal is that this is doing a similar thing to setting up a static ARP entry as I did on the Netscreen, as normally arp translation would require the target machine to be awake to reply to the arp request, which of course it is not.
Note that this post appears to have incorrect information in my case that did not work.
This post is mostly correct, but the above wol command was definitely needed as well or it would not work – I checked this by using wol fromWan off and it stopped working again. In my version, I defined a MAC binding of 10.0.0.253 to ff-ff-ff-ff-ff-ff, i.e. used a spare unused address near the top of the subnet.
In the post, he defined an open port, whereas I used a port redirection as initially I tried a different public port (2007), but changed back to port 7 when I discovered that the port number was not an issue. The key thing here in my case was to map the WAN address in use to the above IP address just bound, using the desired port, and making sure it is a UDP mapping or it will not work.
This finally allowed it to work via the WAN, but noting that initially Panther would not wake due to another reason but Meerkat did successfully, which misled me for a while!