Community discussions

MikroTik App
 
najkon
just joined
Topic Author
Posts: 5
Joined: Wed Jun 20, 2018 2:49 pm

CAPs still reassociating..

Sun Jul 01, 2018 2:58 pm

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
 
İmposss
just joined
Posts: 11
Joined: Sat Jan 16, 2021 5:30 pm

Re: CAPs still reassociating..

Sun Jan 24, 2021 7:06 pm

Same problem
 
User avatar
bpwl
Forum Guru
Forum Guru
Posts: 1290
Joined: Mon Apr 08, 2019 1:16 am

Re: CAPs still reassociating..

Sun Jan 24, 2021 11:36 pm

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)

Who is online

Users browsing this forum: No registered users and 35 guests