“reassociating” - happens on AP: connection assumed to be lost, because Station that is considered already associated attempts to associate again. All connection related information must be deleted, because during association process connection parameters are negotiated (therefore “disconnected”). The reason why Station reassociates must be looked for on Station (most likely cause is that Station for some reason dropped connection without telling AP - e.g. data loss, configuration changes).
No beacon ?? Too High basic rate on AP???
No DHCP IP??
No internet detected?
Roaming attempt failed ??? (so no disconnect “reason=8 message” send to AP)
Disconnect messgae from client not received, transmission failure ???
I think, I found the issue: If the client sees too many APs with his SSID, it starts with “reassociating”, althouth there is no interference (many, many, 5GHz channels).
After reducing the amount of APs, everything seems to be working fine.
If the client sees too many APs with his SSID, it starts with “reassociating”
Or starts roaming quite often.
Don’t forget beacon overhead.
1 SSID instance per AP in a 20 MHz channel at 1Mbps basic rate (enforced 802.11b by some old client in 2.4GHz) consumes 3% of all air-time in that channel.
33 SSID in that 802.11b channel, and ALL air-time is gone. No device can send or answer anymore.
1 SSID in the better 802.11 or 5GHz channel with 20MHz consumes 0.5% of all air-time. 100+ SSID is not common.
It’s a warehouse with quite a strange wireless attenuation…
So, there are about 23 APs (5Ghz only) in 3 levels. So, sometimes, the APs can see other APs from the level above or below.
I did now reduce the number of APs a bit. Power is already very low (8dB), As I am also using most of the DFS channels, Airtime should be sufficient. There are only 3 SSIDs on every AP.