I have an AX88U router and two AC68U mesh nodes all running their latest merlin. I have the system scheduled to reboot once a week but 50% of the time the reboot fails to reconnect to the Internet. When this happens I need to reboot the mesh from the web interface... which always works. Seems like a bug somewhere?
I have an AX88U router and two AC68U mesh nodes all running their latest merlin. I have the system scheduled to reboot once a week but 50% of the time the reboot fails to reconnect to the Internet. When this happens I need to reboot the mesh from the web interface... which always works. Seems like a bug somewhere?
Most likely. The only way to find out where the issue is coming from is to compare the behavior of official Asuswrt and Asuswrt-Merlin on your RT-AX88U. If it's the same - you have to wait for Asuswrt base update, then Asuswrt-Merlin on updated base. The old RT-AC68U routers are EoL and no fixes are expected. Most folks recommend running official Asuswrt on nodes. Not clear what your firmware choice is. Seem like your temporary fix is to disable the scheduled reboot. It's a band-aid solution to underlying issue anyway.
Just a quick question? Why are you rebooting? Is there something so catastrophically wrong with your router that it needs a fresh reset like that? I don't reboot unless I am loading a new firmware update, typically.
Just a quick question? Why are you rebooting? Is there something so catastrophically wrong with your router that it needs a fresh reset like that? I don't reboot unless I am loading a new firmware update, typically.
Maybe about once a month I need to reboot due to network instability issues. I thought that rebooting maybe once a week would keep things healthy, especially when I'm out of town for extended periods. Instead I lost access to my home network when the scheduled reboot happened.
You may want to investigate the root cause of network stability issues. If this setup has issues on official Asuswrt firmware and in vanilla configuration - plan replacement with something more reliable. Out of town plus intermittent issues hurts your family members' user experience.
You could try changing the setting of "DHCP query frequency" in the WAN section. I had a similar issue a while back but newer firmware versions eventually fixed it. If that doesn't work (and it didn't for me), you can try forcing a recycle the WAN connection at startup with the following commands put into an executable script called from services-start:
Bash:
#!/bin/sh
logger -t 'restart_wan' 'Restarting WAN...'
killall -USR1 udhcpc
sleep 10
service restart_wan
logger -t 'restart_wan' '... WAN restarted'
