@msabin wrote:
After much arguing over what was a problem with our client configs and what was a problem with our controller configs and what was due specifically to the code upgrade, we agreed that the primary evidence of the problem we were seeing was that clients appeared to the controller at somewhat lower RSSI than the client thought. Thus the client would keep talking and the controller would de-auth.
Apparently there's an identified issue where the controller mis-perceives the RSSI as low and there's a possibility that that issue is getting addressed.
Just got word from support that 6.1.3.8 may be out by 4/19.
In the case, I do not see anywhere that support replicated your specific issue. Replication of the issue is the first step. Unless support could replicate your issue in-house, there would be no bug filed, no issue identified, and coincidentally, no fix.
I would not upgrade to 6.1.3.8 expecting a fix unless support has confirmed that they replicated it in-house first.
Quite frankly, there could be something specific to your environment that is causing the issue. That would have to be identified, first.