wifi-unstuck runs every 10 minutes witch leaves the node or a piece of the network down for ten minutes

[javierbrk]

*/10 * * * * ((wifi-unstuck &> /dev/null)&)
can this be improved ?

[ilario]

If you just want to change that for yourself, it should (didn't test) be enough to change the value unstuck-interval and unstuck-timeout in /etc/config/lime-node wireless section and then run lime-config:

lime-packages/packages/lime-system/files/etc/config/lime-defaults

Lines 65 to 66 in ee32e4d

	option unstuck_interval '10'
	option unstuck_timeout '300'

If you want to change it for everyone, feel free to open a pull request :) But please consider that during the wireless scan, the wifi interfaces will not communicate with their peers for a short while. If you want to reduce the ibterval drastically (e.g. every minute) I would ask if you can try to measure how long is this silence time (e.g. with a very frequent ping between two routers). Likely it is less than one second, but I am not sure.

[a-gave]

It seems that the problem has been fixed upstream in ath9k and recently backported to openwrt-24.10. See openwrt/openwrt#21487.
Maybe wifi-unstuck-wa could be dropped when openwrt-23.05 became EOL.
I'll try to verify this on real devices which often became deaf and required the workaround.

[javierbrk]

Wow, nice catch ! Saludos Ing. Javier Alejandro Jorge

…

On Fri, 23 Jan 2026 at 21:58, a-gave ***@***.***> wrote: *a-gave* left a comment (libremesh/lime-packages#1208) <#1208 (comment)> It seems that the problem has been fixed upstream in ath9k and recently backported to openwrt-24.10. See openwrt/openwrt#21487 <openwrt/openwrt#21487>. Maybe wifi-unstuck-wa could be dropped when openwrt-23.05 became EOL. I'll try to verify this on real devices which often became deaf and required the workaround. — Reply to this email directly, view it on GitHub <#1208 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABE2I2BHDF5A3ATPTA2FJ2T4IK7SPAVCNFSM6AAAAACDXLZUMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOJTGI4DCMJTGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>