[AC66U_B1] WakeOnLan/Wan Doesn't work after a while.

[kbone123]

Router: Asus RT-AC66U_B1
Firmware: 3.0.0.4.384_21045
Hardware Version: B1
PC OS: Windows 10 Home 64-bit (Build 17134)
NIC: Onboard NIC Realtek PCIe GBE Family Controller
NIC driver: MSI provided driver. Date: 1/19/2018 Version: 10.25.119.2018
Motherboard: MSI Z77a-G43

Wake on Lan/Wan (through port forwarding) works when:
PC has been shut off recently (haven't found exact time limit)
Command is issued through web interface feature for the router.

As far as I can tell, the router being capable of turning the machine on regardless of how long it has been means that the PC and my chosen method of sending the wake packet are configured properly in every way. If it were not, the router wouldn't be able to turn it on either.

This tells me that the router is disabling the connection to the machine after seeing that it is offline for a certain period of time. I currently have the machine set to a static IP in the DHCP settings for the router.

Is there something I can do to deal with this? ASUS support isn't being very supporting.

 

[kbone123]

Update:
I saw last night that the NIC lights are off within seconds of the PC being turned off and not after a few minutes. I also noticed that forwarding the port to the broadcast IP of .255 seemed to work a bit better. This morning after having the PC off all night, I managed to get it to boot, but saw I was still on the network on my phone and used the local wake instead of the WAN. I will be able to test it again to see if it works that way through WAN tomorrow.

However, I consider that to be a temporary solution as I would rather not send anything to the broadcast IP if I don't need to.

Interestingly enough, using ether-wake in the router after using SSH does not get caught by my software on ports 7, 9, or 4343 on the target PC. What port does it use then?

 

[kbone123]

Update 2:
I was able to test it today and keep my PC powered off for ~30-60 minutes. It was not able to turn on from broadcast from outside the network (as expected). So I still do not have a working option for WakeOnWAN.

Does anyone know what the router is changing after a while that makes it no longer be willing to forward the packet to the specified IP?