Wake On LAN - Stop Working After Around An Hour Sleeping?

Pizz

Reputable
Oct 10, 2014
13
0
4,510
Hi All,

I have a DD-WRT configured router, acting as a client bridge on my home network.
After a day or two messing around, I managed to get Wake On LAN (Although, I'm using it to wake the system externally) working.

I woke the system twice and it worked great. Though i've noticed that if I leave the PC sleeping for 30 mins - an hour... It will no longer wake.

Any ideas on what could be causing this?

Thanks,

Pete
 
Solution
You are using the wake on lan feature incorrectly. You are assuming that a sleeping PC has a IP which it does not. It only know about IP once a OS is loaded. You are also getting lucky that the PC will take a packet that is sent directly to its mac address rather than the broadcast address as defined in the wake on lan standard. When the arp entry times out there is no longer a mapping from ip to mac. This is why the wake on lan standard says you must send the packet to the broadcast mac address rather than the actual mac of the pc.

This is the problem when manufactures support things that do not follow the standard, if a pc would ONLY accept a packet with the destination mac of a broadcast when it was in sleep mode people would...
You are using the wake on lan feature incorrectly. You are assuming that a sleeping PC has a IP which it does not. It only know about IP once a OS is loaded. You are also getting lucky that the PC will take a packet that is sent directly to its mac address rather than the broadcast address as defined in the wake on lan standard. When the arp entry times out there is no longer a mapping from ip to mac. This is why the wake on lan standard says you must send the packet to the broadcast mac address rather than the actual mac of the pc.

This is the problem when manufactures support things that do not follow the standard, if a pc would ONLY accept a packet with the destination mac of a broadcast when it was in sleep mode people would learn you do not send WoL to a actual IP address because it would never work

The way to get this to work is to use directed broadcast. You must send the special packet to the broadcast ip...something like 192.168.0.255... and the router must allow this. Many times this feature is disabled because the ability to use it for denial of service attacks.

The way this is normally done safely is to have a machine that is active on the same segment that will accept requests to wake other machines.
 
Solution
Same problem I had.
Add this: arp -s 192.168.1.xxx 01-02-03-04-05-06 in a bat file. Add the file in Task Scheduler to run on Startup or Logon, check box "Run with highest privileges".
Now is solved.
 

Latest posts