Posted: Tue Nov 29, 2022 23:57 Post subject: SSID becomes un-connectable after sometime
Hello,
I have an issue where the router (Asus RT-AC88U, DD-WRT v3.0-r50671 std (10/26/22), though the problem has been going on for at least months, if not a year) will be running normally for a while, but every couple days, devices become unable to connect to one or both of my SSIDs. (I have one for 5GHz and one for 2.4GHz.) Devices will attempt to connect, but it will just fail.
If I SSH to the router and kill the 'nas' processes (one for each SSID), they automatically restart, and everything works again. However, I'd like to not have to do this as it's very annoying when devices fail to connect.
Has anyone else had this issue? I'm not even sure how to get logs of exactly what is failing, so if someone could point me to how we can debug this, I'd love to help get it resolved.
Enable Syslogd on Services page to see what is going on.
From the Command Line interface (telnet/Putty) you can see the whole syslog with:
cat /var/log/messages
The file /var/log/messages is where the syslog is writing to
Thanks for the links. I looked at those and was hopeful about making some config changes that someone suggested, but the problem persists.
I've found that ssh'ing in and issuing a "service nas restart" is the fastest way to get things going again. If I just kill the nas processes, I think it takes time for them to get restarted.
However, this is still very annoying.
I've turned on the logging and monitored it or looked back at it when the issue occurs, but I'm not seeing anything very different from normal things going on.
I often see lines like:
Code:
dhd_flow_rings_delete_for_peer: ifindex 0
Feb 22 17:05:09 Yesac2 kern.info kernel: [1150527.031287] CONSOLE: 1178402.228 wl1: Proxy STA xx:ba:xx:c7:xx:c7 link is
already gone !!??
Feb 22 17:11:17 Yesac2 kern.warn kernel: [1150895.293560] dhd_wait_pend8021x: TIMEOUT
Feb 22 17:11:18 Yesac2 kern.warn kernel: [1150896.378893] dhd_flow_rings_delete_for_peer: ifindex 0
Feb 22 17:11:18 Yesac2 kern.info kernel: [1150896.531211] CONSOLE: 1176800.900 wl0: Proxy STA xx:b4:xx:b4:xx:58 link is
already gone !!??
Feb 22 17:11:31 Yesac2 kern.warn kernel: [1150908.964921] dhd_wait_pend8021x: TIMEOUT
But nothing looks very different around the time that the failures happen.
Is there some way to get additional logging out of the nas? It is clearly something going on with that. It's as if the running nas process loses its configuration, because it will often prompt the client to enter the password again (and the correct password does not work).
Out of curiosity, is there a default password that nas will accept in the absence of a configured password? I'm wondering if I tried that and it connects me if that would tell us anything.
One thing that might even help is if I could write a script on the router itself to detect this problem and automatically restart nas. Though it still knocks every client off and they have to reconnect. But at least it'll recover on its own...