lindend
Occasional Visitor
Roughly about once a week, WOL fails to work for me (Wifi WOL packets or directly from the Merlin admin page). I noticed that if I power up the machine to the Windows login, then power it down in the fail WOL state, I can subsequently send the WOL packet to the machine and it wakes up. When in this state, I tried briefly powering up the machine to get to the BIOS settings, then powering down to see if this was a power issue and that didn't help (i.e. WOL packets wouldn't wake up the machine).
Would this indicate an ARP issue or is it more indicative of something the windows NIC driver does to permit WOL to work after the machine is shutdown? If it is ARP-related, is there a way I can prevent the entry from being flushed from the ARP cache?
The reason I lean towards the ARP explanation (as suggested in this post http://forums.smallnetbuilder.com/showpost.php?p=84189&postcount=19) is this problem never happened when I was using a DIR-655 but showed up when I switched to the N66U.
Would this indicate an ARP issue or is it more indicative of something the windows NIC driver does to permit WOL to work after the machine is shutdown? If it is ARP-related, is there a way I can prevent the entry from being flushed from the ARP cache?
The reason I lean towards the ARP explanation (as suggested in this post http://forums.smallnetbuilder.com/showpost.php?p=84189&postcount=19) is this problem never happened when I was using a DIR-655 but showed up when I switched to the N66U.
