Quote:
Originally Posted by qasdfdsaq
^^ Dark FIber is right.
Though as an addendum, there's a reason "Wake on LAN" is called "Wake on LAN". It's only really designed to work on a LAN. Otherwise it'd be called Wake on WAN or Wake on N. Making it work on anything other than the LAN requires non-standard hacks and tomfoolery in any case so it's not surprising to get different success rates between different equipment
|
Thanks,
qasdfdsaq 
Although I found waking from WAN straightforward for me before the "security" fix became common.
Believe it or not, I'm trying to help
teg. I sympathise with his anger and frustration when something that was working well suddenly stops for no apparent reason- that is exactly how I felt when I upgraded from my old Belkin and found that WoL no longer worked although I'd set the same port forwarding rules in the new router.
My Googling at that time showed three distinct sorts of workaround:
1) Alter the subnet mask so that the broadcast address is no longer what the router designer expected ( this can work with some cheap-and-cheerful routers)
2) Flash the router with non-standard firmware to allow Wake from WAN (
qasdfdsaq, from your sig you might help there
)
3) Set up a WOLF- a small computer like an Arduino or Raspberry Pi that is left on all the time to send magic packets within the LAN.
teg should Google "Wake on LAN Forwarder" as I think it's the best solution for him.