Hi, I just noticed that every time that I set up a configuration of the device it doesn’t stick with it, I think every time reboots it loses that configuration, please a I need help checking the device I have the troubleshoot. I don’t know the anomaly of what could’ve been happening.
I went through the troubleshoot-RUT240-2026-08-11.tar.gz file — a few things stand out.
The overlay partition (JFFS2) isn’t full (3.8 MB free out of 4.3 MB), so this doesn’t look like a “no space to save config” issue.
The most suspicious thing is the reboot pattern in the event database (log.db). You have ping_reboot enabled (pinging 8.8.8.8 every 5s, rebooting after 3 failed attempts) — the history shows 29 such forced reboots. More importantly: the last logged reboot (July 31) has a cause marked as “Other” — a rare, unusual code that only appears 3 times in the entire history. And the device’s current uptime session has no corresponding “Reboot” entry in the database at all — even though every other type of reboot (WebUI, button, scheduler, FW upgrade) is always logged there.
This may (though I can’t confirm it remotely) point to unplanned/unclean restarts — e.g. a brief power loss or a system hang — rather than a normal reboot. On the small flash storage these devices use, an abrupt restart while the config is being written can, in rare cases, result in a fallback to default settings on next boot.
What I’d check first:
Power supply — check the adapter, cable, and outlet (a loose connector can cause exactly this symptom).
ping_reboot — if it’s not essential, consider disabling it or relaxing it (higher retry/time_out) to reduce the number of forced reboots.
Firmware update — you’re on RUT2_R_00.07.06.21; worth checking whether a newer version includes overlay-write related fixes.
After reconfiguring, immediately take a Device Backup (not Configuration backup) — if this happens again, you can restore in a minute instead of reconfiguring everything by hand.
Let me know whether, after these steps, reboots in the log start showing a proper logged cause — that’ll be a good sign the issue is actually resolved.