On Sun, May 19, 2019 at 05:38:03PM +0000, Lévai, Dániel wrote: > And for some reason -- and this is really strange, I know --, sometimes it > gets into a state where no client can connect/auth to the AP, and nothing > seems to be able to fix it other than a hard reset of the AP. On a Linux > client machine with wpa_supplicant(8) these are the log messages when this > latter happens: > > May 19 19:08:38 serenity kernel: wlan0: authenticate with <ap> > May 19 19:08:38 serenity kernel: wlan0: send auth to <ap> (try 1/3) > May 19 19:08:38 serenity kernel: wlan0: authenticated > May 19 19:08:38 serenity kernel: wlan0: associate with <ap> (try 1/3) > May 19 19:08:38 serenity kernel: wlan0: RX AssocResp from <ap> (capab=0x411 > status=0 aid=2) > May 19 19:08:38 serenity kernel: wlan0: associated > May 19 19:08:39 serenity kernel: wlan0: deauthenticated from <ap> (Reason: > 15=4WAY_HANDSHAKE_TIMEOUT) > > This just goes on and on and on.
And what do you see with 'ifconfig athn0 debug' on the AP?
