You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having a problem where all my wireless clients are dropped on a wifi that is running on radio1 of my WRT32X. This used to happen once every week or so, but it seems to have gotten more frequent with it happening once every couple of days.
Versions: OpenWrt 19.07.2 r10947-65030d81f3 / LuCI openwrt-19.07 branch git-20.067.35699-cf18bdd
All packages have been recently upgraded. This used to happen on 19.06 too but it's become more frequent recently.
Here are some things I've noticed:
Memory usage keeps steadily increasing as soon as this happens. If I don't reboot the router, the router will eventually crash and reboot itself due to it running out of memory.
top doesn't show me any processes using too much memory, so I don't know exactly who is leaking memory when it happens (the memory leak is more likely to be a symptom than the root cause).
As soon as this happens, dmesg becomes flooded with messages such as "[ 1983.388642] ieee80211 phy0: staid 13 deleted" (with different "staid numbers")
A router restart is sufficient to make things go back to normal.
This only happens for my 2.4GHz network for IoT on radio1. It does not happen for my 5GHz network on radio0, which stays stable.
luizribeiro:
I'm having a problem where all my wireless clients are dropped on a wifi that is running on radio1 of my WRT32X. This used to happen once every week or so, but it seems to have gotten more frequent with it happening once every couple of days.
Versions: OpenWrt 19.07.2 r10947-65030d81f3 / LuCI openwrt-19.07 branch git-20.067.35699-cf18bdd
All packages have been recently upgraded. This used to happen on 19.06 too but it's become more frequent recently.
Here are some things I've noticed:
FWIW, this is my current /etc/config/wireless: https://gist.github.com/luizribeiro/d15e3598747c126c0728696f5ebe8960
Any thoughts on what else I could be looking at to pinpoint where the bug is?
The text was updated successfully, but these errors were encountered: