Hello. I have a GL.iNet MT3000 Beryl AX at my summer home running Tailscale. I have a QNAP NAS at my regular home running Tailscale as well. This setup allows my NAS security software at my regular home to continuously record video on the NAS from cameras that are located at the summer home. The setup has been working flawlessly for over three months, but about 5 days ago the recordings stopped because the Tailscale connection was lost. I can tell that the modem and router at the summer home are still working because I can access the cameras using the camera manufacturer’s app on my phone which does not require Tailscale to be operational. I cannot access the Beryl AX using the Tailscale IP address, and the Tailscale Admin Console shows the Beryl AX is not connected. The console shows it was “Last Seen” 1 day ago even though the issue started 5 days ago. If I look at the video logs for the summer home cameras there are a couple short recordings since the problem began. The “Last Seen” date and the small number of short recordings tell me that it does periodically connect for a short time, unfortunately I can never catch it when it’s connected to log into the Beryl AX to reboot it. The Tailscale Admin Console says that the OpenWrt is 8 versions out of date. I prefer to update the Beryl AX while at the summer home rather than remotely in case an issue occurs that needs attention on-site. What I’m speculating is that the Beryl AX is bogged down possibly due to a shortage of memory and that a reboot might fix the problem. Next time there I’ll test this and if a reboot corrects it I’ll put a programmable timer on the Beryl AX to power it down and back up perhaps once a week. My question is whether anyone has experienced a similar problem, and if users find it necessary to periodically reboot their GI.iNet routers?
I set my Beryl AX to reboot every night at 0400. There is an admin panel option to set up the reboot. See screenshot.
The reason I set up the nightly reboot is because of repeated experiences similar to what you describe. Beryl AX seems to simply give up after a while - regular reboots are the only reliable solution I have found.
Hi,
It has nothing to do with the software version of Tailscale. The current firmware version of Tailscale can be connected and run stably.
-
Please check whether there are any issues with Internet access?
-
When there is an issue with Tailscale, if there is any way to export the issue syslog on the router, to check if there is any problem with the network?
-
If possible, enter SSH and execute the following command to check the tailscale process status:
tailscale status
ps |grep tailscale
Currently the router can enable the schedule reboot.
Thank you both for your advice. After checking the Tailscale Admin Console often, I finally caught the Beryl AX online, logged into it remotely, and rebooted it. I also setup a scheduled reboot while I was at it. All seems to be back to normal at this point as cameras are streaming to my NAS. Great tip for the scheduled reboot!
In my experience, Beryl AX (or any device with constrained RAM and no swap) seems to benefit from regular reboots, especially in unattended setups.
Unattended/Remote deployments on constrained devices need watchdog scripts, uptime limits, or reboot schedules. At least that’s my thinking.