I was thinking of another possible workaround. And why so many of us choose to use third party firmware. For anyone familiar w/ WOW, this is old news, and well understood. But I can guarantee you that this issue w/ ARP *is* and will remain an issue for WOW. So I'm not claiming you might not have other issues. Usually you don't have this kind of low-level access, so you can't fix that particular problem. When it comes to OEM firmware, that's another matter. My own WOW configuration works perfectly, and has for many years, but I'm always using a third party firmware on my router (dd-wrt, tomato, etc.) that makes adding a static ARP entry trivial. And when it does, the router will have no way of determining the MAC address of the target device based on its IP address unless there's a static/fixed entry in its ARP table. Sooner or later the ARP entry for the target device is going to drop from the router's ARP cache. This is a loooooong standing and well known problem when dealing w/ WOW. And before WOW is ever going to work, WOL has to be configured and working reliably from the LAN.Īll that said, whatever issues you may be having that might explain why WOL/WOW doesn't work even a few seconds after a clean shutdown, doesn't negate the issue of ARP. The reason I'm explaining all this is just to make it clear how it actually works, and why it can be tricky to set up properly. That's why it's recommended that if you're going to use WOL, that you also configure the BIOS to automatically boot the machine when recovering from a loss of power (the name of this BIOS option varies from system to system). WOL is a process of the normal shutdown process. IOW, it has to be powered down cleanly! If, for example, you literally just pull the power from the machine, or power is suddenly lost for any other reason, WOL will NOT be set. When you configure your PC and BIOS for WOL, that tells Windows and the BIOS to place the network adapter into a special WOL state as the system is being shutdown. closing the PC while listening to the port. I don't understand the distinction you're making between closing the PC vs. I'm not 100% sure that the ARP cache doesn't get reset, but if this was my only problem, then shouldn't wake on wan work say 10 seconds after I close my PC regardless of what it was doing? Because that isn't the case, WOW only works 10 seconds after I close my PC if the PC was actively listening to the port, which is why I asked about disabling auto closing/opening of ports. Using third-party firmware like dd-wrt, tomato, etc., makes this a trivial exercise. Or perhaps they do buried somewhere in the GUI, but that would vary from router to router. Of course, not all routers provide this kind of low level access. So now the ARP table always has this information available, even if the target device is sleeping. where you replace 00:01:02:03:04:05 and 192.168.1.100 w/ the target device's actual MAC address and IP on the LAN. If you have access to the CLI, the command would be: The solution is to add a static/permanent ARP entry for that device to the router. But of course it's sleeping, so the ARP request fails, and you can't wake the device. And since the device is sleeping, when you try to use that port forward to wake the device, the first thing the router has to do is determine its MAC address based on its IP address, so it can then update its ARP table and initiate communications w/ it over ethernet. In order for WOL to work, the ARP entry for the target device (which maps the target device's MAC address to its IP address) must be available, but it's only cached in the router for a very short period (5-10 mins in most cases). Now my question is, is there any way to disable this kind of closing/smart opening or whatever, as my router seems to close port when the PC is turned off, defeating the whole purpose of WOL over WAN or whatever it's called.Ĭould a broadcast address, instead of the direct static address of my PC work? How would I use said address? What else can I do?Īny help is appreciated and sorry if this is a stupid question.Įlisa (finnish ISP) version of ZyXEL VMG3925-B10B My PC even wakes up after the monitor has been active, but only for about 5 minutes, I assume this is due to some clever port opening and closing going on. The green light of my PC's ethernet cable even keeps blinking when the PC is off.īut I seem to have run into a problem with the port required for WOL not staying open I have the port forwarding rule set up in my router (see below) and it works when I open up say Depicus Wake On Lan Monitor. ethernet adapter allowed to wake the device I have enabled all of the necessary things in windows and BIOS: I am trying to use Wake On Lan, but from a remote IP, over the internet, to turn my PC on.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |