Unless you have a critical reason or use case for this, it's really not necessary to reboot every day. Mine only reboots if a major change is made that requires a reboot, or a new firmware update was applied.I'll report back tomorrow after it does scheduled reboot overnight.
There should be some messages in the system log to hint at what happened. Either it couldn’t find the USB in time, your DNS wasn’t working, or something is corrupt on your /jffs or USB. You need to look for the clues instead of uninstalling and reinstalling.After reboot, Skynet was still not running.
Sorry if I was not clear: I truly believe this is on my side, not blaming Skynet.There should be some messages in the system log to hint at what happened. Either it couldn’t find the USB in time, your DNS wasn’t working, or something is corrupt on your /jffs or USB. You need to look for the clues instead of uninstalling and reinstalling.
Skynet hasn’t changed in any significant way in several months.
I agree. I only have a scheduled daily reboot because I have a few network clients that just do not behave properly without atleast a once every other day reboot, but that is not related to the behavior of the router. I just choose to reboot instead of writing my own FIXITMON. I think that is a new idea you could terminally market on. Have wifi stability issues, restart the wifi. Have an issue with clients and their rouge behaviors with DHCP, restart the dhcp service. You could set it to where task can be scheduled using the crontab.Unless you have a critical reason or use case for this, it's really not necessary to reboot every day. Mine only reboots if a major change is made that requires a reboot, or a new firmware update was applied.
scMerlin does allow you to restart services as you have alluded to.I agree. I only have a scheduled daily reboot because I have a few network clients that just do not behave properly without atleast a once every other day reboot, but that is not related to the behavior of the router. I just choose to reboot instead of writing my own FIXITMON. I think that is a new idea you could terminally market on. Have wifi stability issues, restart the wifi. Have an issue with clients and their rouge behaviors with DHCP, restart the dhcp service. You could set it to where task can be scheduled using the crontab.
I actually have something like this on my to-do list. Like if the WAN isn't responsive after so many minutes/attempts, force a reboot. I like that idea about DHCP, WiFi, etc. too.I agree. I only have a scheduled daily reboot because I have a few network clients that just do not behave properly without atleast a once every other day reboot, but that is not related to the behavior of the router. I just choose to reboot instead of writing my own FIXITMON. I think that is a new idea you could terminally market on. Have wifi stability issues, restart the wifi. Have an issue with clients and their rouge behaviors with DHCP, restart the dhcp service. You could set it to where task can be scheduled using the crontab.
That particular one has been done before.Like if the WAN isn't responsive after so many minutes/attempts, force a reboot
Thought I remember seeing that somewhere before.That particular one has been done before.
![]()
GitHub - MartineauUK/Chk-WAN: ASUS Router Check WAN status
ASUS Router Check WAN status. Contribute to MartineauUK/Chk-WAN development by creating an account on GitHub.github.com
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!