May 6, 2012
I'm hoping to get this router to allow WOL (actually wake on WAN) but it seems to be blocking the necessary broadcast magic packet even though the settings appear correct. It's not critical, but the reason is this: I'd like to shut down the home PC, but when necessary be able to start it up and use a VPN to access any info I need remotely.
View 5 Replies
From within the LAN, I can verity that WOL works. I have NIC and PCI WOL enabled in the BIOS. The NIC (a Marvel Yukon Gigabit) has WOL enabled as well as "allow this device to wake.." using magic packets under power management. The target machine's local IP is reserved through the EA4500 DHCP Reservation table. Just for troubleshooting, I opened port 9 in windows firewall. More importantly, I have ports 7-9 forwarded to my target LAN address. Single port forwarding... it just has been less reliable (?). I'm using a mask of 255.255.255.128 in order to enable broadcasting on .127 at some point as it seems it must be necessary. Broadcasting on .255 is not possible, despite some workarounds I found on the web. EA4500 firmware is the latest, 2.0.37. I have turned off the multicast filter and the anonymous internet filters under the security tab.
So, with these settings, I can WOL from inside the network no problem either targeting the LAN address, or by using a dyndns address. So far so good.With these same settings, I can go to WAN using Depicus or the Cloud Connect Pro app over 4G on an iPad. With all these same settings, WOLsniffer confirms the magic packet still getting through over WAN (obviously using the dyndns address). Even better, I can shutdown the target PC and STILL wake it up within a few minutes from WAN. Let me restate that! Wake up over WAN works, but only for the first few minutes after a shutdown.
However, if I wait 20 minutes or so, WOL stops working. If I change the port forwarding to .127, not only does it not work, but WOLsniffer will fail to see the magic packet. My conclusion is that the ARP table is getting purged, which is undertandable, and so the target LAN address isn't in memory. However, frustratingly the EA4500 will not broadcast no matter what settings you use. This limitation is undocumented, and counterintuitive since the software allows you to disable multicast filtering and does not notify you of an error when forwarding to xxx.xxx.xxx.127 with a 255.255.255.128 mask.