CAPs still reassociating..

13:48:27 caps,info 4C:34:88:86:E0:A7@cap1 reassociating 
13:48:27 caps,info XX:XX:88:06:E0:A7@cap1 connected, signal strength -56 
13:48:42 caps,info XX:XX:88:06:E0:A7@cap1 reassociating 
13:48:42 caps,info XX:XX:88:06:E0:A7@cap1 connected, signal strength -50 
13:48:51 caps,info XX:XX:88:06:E0:A7@cap1 reassociating 
13:48:51 caps,info XX:XX:88:06:E0:A7@cap1 connected, signal strength -52 
13:49:26 caps,info XX:XX:88:06:E0:A7@cap1 reassociating 
13:49:26 caps,info XX:XX:88:06:E0:A7@cap1 connected, signal strength -48 
13:49:31 caps,info XX:XX:88:06:E0:A7@cap1 reassociating 
13:49:31 caps,info XX:XX:88:06:E0:A7@cap1 connected, signal strength -54

Anyone can explain why is this happening?
CAP Access list is empty.

    
       routerboard: yes
             model: 2011UAS-2HnD
     firmware-type: ar9344
  factory-firmware: 3.0
  current-firmware: 6.41.2
  upgrade-firmware: 6.42.5

Same problem

Some problems that trigger this:

  • wrong authentication password
  • wrong security profile: e.g. missing TKIP or AES when needed.
  • the client remembers an old and different security profile, with different characteristics (Delete known network (SSID) on the client to re-learn)
  • client does not receive an IP address (DHCP fails) and cannot communicate
  • some clients will drop the association if it does not give internet access. (Every type of client OS has a different test procedure for internet)
  • bridge does not learn the MAC address. Set WLAN bridge port to learning mode “auto”, and check that the MAC address comes in the bridges host table

Anything that prevents the client from using the wifi connection for its intended traffic may make the client restart the association process.

Enable wifi debug logging, there might be some more information ( /system logging add topics=wireless)

Same problem.
Has anyone found any solutions?

Hi!

Same issue, here…

Did you ever solve this?

Thank you and best wishes

https://wiki.mikrotik.com/wiki/Manual:Wireless_Debug_Logs

“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 ???

Hi!

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.

Truly reducing or lowering transmit power ?

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.

Air time consumption/reservation is till a received signal level of -96dBm. That’s quite below the usefull signal level.

Reducing power in the AP might slow down the TX interface rate! So even busier channel.

Sniff wireless to see what’s going on. Wireless Sniffer is in any MT.

Hi!

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.