We are experiencing repeated 2.4 GHz Wi‑Fi outages on our RUTX50 unit. The Wi‑Fi network appears active in the UI, but all 2.4 GHz clients disconnect and the SSID becomes invisible to users, meaning devices cannot detect or connect to the network until the device is rebooted. This occurs after a few hours of uptime (1-4h).
The system logs show repeated errors such as:
ath10k_ahb a000000.wifi: failed to send pdev bss chan info request
hostapd: Failed to set beacon parameters
These errors correlate tightly with the Wi‑Fi stopping. Based on kernel logs, the ath10k driver appears to hang when trying to update beacon/channel information, and hostapd repeatedly reports being unable to set beacon parameters. Clients then disconnect even though the 2.4 GHz SSID is still shown as enabled.
We initially had this problem on our old RUTX11, which we assumed “had done its time,” so we purchased brand new RUTX50 unit — the exact same failure occurs on both devices.
We have:
Tried multiple channels and fixed bandwidth (20 MHz).
Tried rebooting the Wi‑Fi service, but only a full device reboot restores connectivity and uptime of the WiFi again.
This strongly suggests an issue with the ath10k Wi‑Fi firmware/driver on 2.4 GHz, rather than configuration or RF interference.
There are existing reports on the Teltonika community describing the same symptoms:
“RUTX50 occasionally drops 2.4 GHz Wi‑Fi — Wi‑Fi still shows on but clients lost, reboot fixes it” — users noted this started after firmware upgrades and affects primarily 2.4 GHz with IoT devices (smart plugs, cameras, sensors) connecting, requiring a reboot to restore service. (community.teltonika.lt)
“RUTX50 sometimes drops 2.4 WiFi connection — Wi‑Fi works but clients are lost; restarting Wi‑Fi doesn’t solve it but reboot does” — further confirms community experience of similar failures (logs and troubleshooting discussions included). (community.teltonika.lt)
Please advise if this is a known regression in the current firmware, and how we should resolve this issue. Is there a recommended firmware version, patch, or configuration change that will prevent this ath10k beacon/driver failure on 2.4 GHz?
To answer your question first, this is not a known issue, so we’ll take a look at what’s going on.
I can see that you are already on the latest firmware, but could you clarify which firmware you were on previously when you upgraded to 7.20.3?
Did you try resetting your device as a troubleshooting step? Does a phone find & connect to the WiFi? Does the issue occur only with one beacon, or with others as well if you have multiple? What power supply is being used to power the RUTX50? What antennas?
On top of this, could you also try disabling the Disassociate on low acknowledgement setting under Network → Wireless → SSIDs → “Edit” on the interface → Additional settings:
Next, under Network → DHCP → Server Settings, could you confirm that the server is enabled? If it’s disabled, this could very well cause the devices to either connect/disconnect, or not connect at all:
Thank you for getting back to us. Please see our answers below.
Regarding the firmware version:
Since the device is completely new, the very first thing we did was to upgrade it to the latest firmware (7.20.3).
On our previous RUTX11 device (which unfortunately has now been recycled), we were also running the latest firmware version.
Yes, we have performed a full factory reset of the device and reconfigured it from scratch, but the issue persists.
We are running two separate 2.4 GHz WiFi networks (SSIDs). Over the last day, we noticed that if one of the two networks is disabled, only a single SSID is broadcast and the WiFi then works as expected. When we activate both SSIDs again, the problem return within a few hour(s).
The RUTX50 is powered using the included power adapter.
This caught my eye. I believe it would be wise for me to collect the troubleshoot file from your device so I can see what’s happening. I’ve sent you a form to fill out, you’ll receive it in your email inbox. Simply fill it out with your contact details, and for the ticket ID use 17551
