please send the support output files from your setup where you see this problem to email@example.com
We need the information how to reproduce your problem.
well, if I only could...
Each unit (all 133C3 boards with R52 radio) that develops the problem becomes inaccessible. I took one home, and set it up again to AP (rb433AH running 5.17 with latest fw) and within 5 minutes disconnects started again.
In AP log it says: "key exchange timeout" or "control frame timeout"
I cannot log into the board, not by mac not by IP. (It is getting an IP on the wlan)
When I try to log into via ether1 (and mac, no dhcp-cl) I get the error: "unable to connect to xxxxxxxxxxx etc - timeout"
If I try to login via de AP it takes a long time before the winbox window is presented. If I than want to open any window the connection drops.
With other boards having the same issue I also cannot login. I get same kind of timeout errors in winbox loader, or in the logs I see "key exchange timeout" or "control frame timeout"
These boards had no issues before (v.5.14, 5.15 or 5.16)
It is also only a fraction of the total 133C3 boards. I have several that updated without any problems (so far) and that don't disconnect.
I also seem to find now that when I finally would manage to log in a board with the issue (sometimes after 30 mins of more I suddenly can log in) I find the timeserver client is not updating the clock. Settings are exactly the same as before and as other units that do update. In the log I could even see that before the update the time was set right, but now not any more......
Because I cannot log into the units any more, and when I can they never stay connected long enough, I can't downgrade as well.
I am not amused by this! I am forced now to change these boards by other units (mipsbe) which was not planned!
Show your appreciation of this post by giving me Karma! Thanks.
Rudy R. Puister
WISP operator based on MT routerboard & ROS.