Since the Tailscale segfault issues that were fixed in 7.11.1, each time RutOS has upgraded on my RUTX11 I have needed to go into the web UI via RMS to log Tailscale back in. The method I am authenticating with is the Tailscale login URL. When I re-authenticate the router appears as a new machine in the Tailscale list and I have to approve routes again.
Is this authentication supposed to be stored somewhere and persist through RutOS upgrades? I did install the manually fixed package provided to me before 7.11.1 was released, but have removed that, deleted associated configuration and added the package again from Package Manager, but that didn’t help with the de-authing.
I am not in a position to reset the router to defaults but any suggestion that doesn’t involve that would be appreciated.
Could you please confirm whether this issue persists after updating to the latest 7.12 firmware? You can download the firmware here: RUTX11 Firmware Downloads.
The issue occurred most recently as part of the upgrade to 7.12, if 7.12 is meant to fix it then I’ll have to let you know after the release of the next firmware version.
Our developers are aware of this issue and are actively working on a resolution. I’ll keep you updated as soon as I have news about when the fix will be available.
Thank you for your patience. The current Tailscale issue, which requires logging in after each RutOS update, will be fixed with the upcoming 7.13 firmware release this month. However, I don’t have a precise release date now.
I have just applied 7.13 and needed to log into Tailscale again.
Are the fixes in 7.13 so that future updates won’t need Tailscale to be re-authenticated, or was the 7.13 update meant to retain the Tailscale authentication?
Unfortunately, the 7.13 firmware was removed due to an issue with Auto Reboot. Once the fixed firmware becomes available, I will test Tailscale again and check if the issue persists.
I had an auto reboot issue with the ping monitor (it would always act as if the pings had failed) and resolved it by deleting the monitor and creating it again.
Could you please confirm if you experienced this issue and managed to resolve it with the 7.13 firmware version? If so, could you kindly provide the detailed steps you followed (what you configured, deleted, etc.), and, if possible, include any relevant screenshots?
I upgraded to 7.13 and was getting ping watchdog reboots listed in the system logs. I fixed it by deleting the reboot action and recreating it. Editing the timing wasn’t enough to prevent the reboots.
The 14:15 reboot is exactly 20 minutes after the firmware update which aligns with two ping timeouts 10 minutes apart. I then changed some reboot interval settings and the 14:45 reboot was 25 minutes after the device booted. I turned the ping reboot feature off after this but then revisited it in the evening, deleted the old configuration and created it again. My device with 7.13 has been up for 23 hours now with the ping reboot feature enabled.
