I’ve been with a RUT50X for some years in my camper. I’m powering the unit with the original 12v cable, and the power in the camper is rock solid.
It’s usually connected online with a Starlink, but now while in Europe I have it running a SIM card. Speeds are great and all that but.. clients are getting disconnected like every 20-30 mins for 15-20 secs.
In most cases the logs just show
WiFi client disconnected: 72:68:XX..
WiFi client connected: 72:68:XX..
And in a few instances I get
DNS resolution started to fail
IPv4 connectivity restored
DNS resolution restored
Any suggestions on how to debug the disconnect/connect issues?
These specific logs tell me that the issue could be mobile-related, what are your signals? (Status → network → mobile) blur out everything besides the colorful signal values
In that case, could you try following this process? This will reset your device completely, but will help us rule out any other factors that may be causing this: Bootloader menu - Teltonika Networks Wiki
Prerequisites:
Direct access to the device (physical)
Ethernet cable (LAN of device connected to a PC)
Firmware file downloaded (can be any, just use the stable FW file)
A needle or something pointy to press the reset button
As the user suggested, the resolution errors are usually mobile-related, so we would need the requested information to investigate further regarding that.
As for the bootloader process, if you are not in any way able to do it, you can opt for a simple factory reset if that hasn’t been tried already. You can also try upgrading from 7.18.3 to 7.19.4 to see if that helps with your issues. The firmware download page can be found here: https://wiki.teltonika-networks.com/view/RUTX50_Firmware_Downloads
Thanks. Later today I will have full 5G on my cellphone. From there I will keep an eye on the logs. Is there any simple way to determine, if the issue is due to local devices in my network or the cell reception in general or?
You can view the logs in the System.log that is located within the troubleshoot file of your device. You’d have to reproduce the issue, and then download the file from System → Maintenance → Troubleshoot → Download. It’ll be a .tar.gz file so you’ll need WinRar or 7ZIP to open it.