Hi TeltonikaTeam,
I have the RUTx11 and since a few updates I experience a strange behavior. After a reboot my WLAN works and after one or some days then I cannot connect with my mobile phone anymore. The network is shown and my device tries to connect, but then it stays as saved and not as connected (in Android). And it is really annoying to reboot everytime, it takes much time.
I don’t want to reset everything because I configured it really well for my needs. And by the way: I did not change anything for a long time. Then I experienced strange behavior in the mobile network, it was disconnecting during work. It happened with the version RUTX_R_00.07.14.3.
Then I installed the new stable RUTX_R_00.07.25.3. And then I got this weird behavior with the WLAN. And then I decided to install RUTX_R_00.07.25.2 and the error with the WLAN still exists.
I do not have any time based (schedules) WLAN on and off settings, if there is any, I don’t know.
The event log does not say anything in this matter with WLAN when my mobile phone tries to connect. After a reboot when I connect to the WLAN, the log says “… WiFi client connected …”.
And also what I realized: sometimes when I cannot connect to the WLAN, I login into the web interface via LAN and then there is an error showing up, something with log event cannot be read or written or something like that. It seems that it got stuck in something.
Switching off and off WLAN and/or radio does not solve the issue. I always have to reboot.
Sometimes the WLAN is completely not visible in mobile phone. And sometime visible, but not cannot connect.
Here in the forum one topic was proposed me: set WIFI radio to a certain channel instead of “auto”. This did not help. After the reboot WLAN worked, then after two days again the same symptoms.
Can you please help me to fix the issue. What information (log, data, etc.) should/can I provide you.
Greetings,
Thank you for bringing this to our attention, and apologies for the delayed response!
I have forwarded your case to our R&D team for further investigation. I will keep you updated as soon as I receive any news or next steps regarding your issue.
In the meantime, please don’t hesitate to reach out if you have any additional questions!
Best regards,
Martyna
Hi @Martyna ,
thank you for the reply. In the meantime I tried to identify the cause with the help of AI and this came out:
Device / firmware
RUTX11, RUTX_R_00.07.25.2.
Symptoms
After several hours up to ~1–2 days, 2.4 GHz Wi‑Fi stops accepting clients. The SSID may still be visible; phones/laptops fail to connect (e.g. Android: Connecting → Saved). LAN and mobile WAN keep working. Toggling Wi‑Fi/radio does not help — only a full reboot restores Wi‑Fi. The WebUI may also show event/log read/write errors.
What actually broke Wi‑Fi (on the device)
While the issue was active, logs showed the 2.4 GHz radio (ath10k / Qualcomm IPQ4019) in a firmware hang:
hostapd: Failed to set beacon parametersath10k_ahb … failed to send pdev bss chan info request (repeating every few seconds)- Soft restart (
wifi down / wifi up) could produce ath10k_ahb … failed to halt axi bus
- After that, the AP could look “up” (
AP-ENABLED, SSID visible) but clients still failed (e.g. PREV_AUTH_NOT_VALID)
So the direct cause of the Wi‑Fi outage is this ath10k firmware hang, not “no internet” and not a client-only problem. Soft Wi‑Fi restart is not a reliable recovery after the AXI halt; a full reboot is required.
What caused the ath10k hang?
Not fully proven.
- The hang is what killed Wi‑Fi. Why the firmware entered that state is not 100% clear from the logs.
- This class of
ath10k/IPQ4019 hangs is known to appear after hours/days of uptime (driver/firmware stability issue), sometimes without an obvious trigger.
About WireGuard on my unit
I separately had a local WireGuard misconfiguration: a watchdog kept restarting an unreachable peer about every minute (interface down/up, firewall reload, etc.). That is not “WireGuard in general breaks Wi‑Fi.” It is a bad config on my side.
That restart loop is a suspected trigger / stress factor for the hang (heavy recurring churn), because after reboot — with that WG setup left disabled — Wi‑Fi stayed stable for several days. I do not have proof of a strict causal chain like “WG restart → ath10k dies immediately.” I will re-enable WireGuard later, after dual-SSID Wi‑Fi has been stable for a few more days, and treat WG as a separate topic.
About /log/log.db
The event database was corrupted (database disk image is malformed). That explains the WebUI event/log errors. It does not cause the ath10k hang or client association failures. Overlay/tmp were not full. Moving the broken DB aside and letting the service recreate it fixed integrity (PRAGMA integrity_check → ok) without a factory reset.
Summary
| Item |
Role |
| ath10k firmware hang |
Direct cause of Wi‑Fi outage |
| Why the hang started |
Unclear; possible driver/firmware bug under load/uptime |
| Local WG watchdog loop |
Suspected trigger on my device only (misconfig), not confirmed as the sole cause |
Corrupted log.db |
Separate issue (WebUI logs), unrelated to the radio hang |
Useful checks while Wi‑Fi is broken (via LAN/SSH)
logread | grep -E 'Failed to set beacon|bss chan info|halt axi|malformed'
dmesg | tail -n 100
iwinfo
wifi status # redact PSKs before posting — shown in cleartext
sqlite3 /log/log.db 'PRAGMA integrity_check;'
Ask for Teltonika
Is this ath10k hang known on RUTX with firmware 10.4-3.6-00140 under 07.25.x? Any recommended recovery besides reboot, or known fixes in later builds?
So now the problem seems to be gone. And I am happy to do it without a reset 
I still need to activate WG after some days of testing the WIFI. But the information from AI might help the TeltonikaTeam to find the real cause and a potential bug.
Best wishes,
Wasilij
Hi @wasilij,
Thank you for the detailed information and for testing this so thoroughly. I’m glad Wi-Fi has been stable so far.
If the issue reoccurs, please download the troubleshoot file (System → Maintenance → Troubleshoot) while the problem is active, before rebooting the router, so the logs are still included.
The troubleshoot file may contain passwords, public IP addresses, serial numbers, and other sensitive information. To avoid leaking this information, we have sent you a form to your forum account’s registered e-mail address. Once the issue reoccurs, please fill out the form and we will let you know how to send us the file. In the Ticket ID field, please enter the ID of this thread, which is 21455.
I’ll pass your findings on to the team and get back to you as soon as I have more information.
Best regards,
Martyna
Hi @Martyna ,
I have some updates about the testing…
So as I mentioned, I could run the WIFI without errors for some days. Then I tried to switch on the things step by step as they were before. So the next I tried to switch on the second WIFI (for guests). And guess what. After one day the problem again occurred, I cannot see my first WIFI.
So this is worth to inspect in detail.
Yes, I got the mail to the form and sent it, but I thought I could upload there something (like the diagnostic files). So what should I do next after switching the second WIFI on to provoke the error to occur again, then download the files and then handle you … ?
see u
Wasilij