CAPsMAN Wave2 (ax2->ac3)

RouterOS Wireless Networking
1

Hi to all. I have hap ax2 (CAPsMAN) and hap ac3 (CAP).
Adjusted by CAPsMAN. The devices work in Wifiwave2.
Screenshot 2023-09-09 225958.png
The problem is that switching the client from hap ax2 to hap ac3 does not work.
Case

  1. The client connected to hap ax2 goes towards hap ac3
  2. The signal strength is -90, while the client is already standing near hap ac3 with a -50 signal
  3. Wifi on the client is disconnected, reconnected already to hap ac3
  4. The client goes back to hap ax2 - history repeats itself
2

I saw the following entries in the logs
with cap-wifi1 (ac3) there is roaming on wifi1 (ax2)
with wifi1 (ax2) on cap-wifi1 (ac3) there is no roaming (
…
Wait for some update or sell ac3? )))
Screenshot 2023-09-11 183138.png

3

Not clear how your config is like ?

You have a combination of local and capsman radios ? Which one is capsman controller ?

4

CAPsMAN ax2

/interface wifiwave2 channel
add band=2ghz-n disabled=no frequency=2472 name=channel_13
add band=5ghz-ac disabled=no frequency=5220 name=channel_44
add band=5ghz-ac disabled=no frequency=5240 name=channel_48
/interface wifiwave2 security
add authentication-types=wpa2-psk disabled=no name=HomeNet
/interface wifiwave2 configuration
add channel=channel_44 country=Ukraine disabled=no mode=ap name=HomeNet5 \
    security=HomeNet ssid=Home5
add channel=channel_13 country=Ukraine disabled=no mode=ap name=GuestWifi \
    security=HomeNet ssid=GuestWifi
/interface wifiwave2 cap
set caps-man-addresses=127.0.0.1 enabled=yes
/interface wifiwave2 capsman
set ca-certificate=auto enabled=yes package-path="" require-peer-certificate=\
    no upgrade-policy=none
/interface wifiwave2 provisioning
add action=create-dynamic-enabled disabled=no master-configuration=GuestWifi \
    supported-bands=2ghz-n
add action=create-dynamic-enabled disabled=no master-configuration=HomeNet5 \
    supported-bands=5ghz-ac

cap ac3

/interface wifiwave2
# managed by CAPsMAN
# mode: AP, SSID: GuestWifi, channel: 2472/n
set [ find default-name=wifi1 ] channel.band=2ghz-n .skip-dfs-channels=\
    10min-cac .width=20/40mhz configuration.manager=capsman-or-local .mode=ap \
    datapath.bridge=bridge disabled=no
# managed by CAPsMAN
# mode: AP, SSID: Home5, channel: 5220/ac/eeCe
set [ find default-name=wifi2 ] channel.band=5ghz-ac .width=20/40/80mhz \
    configuration.manager=capsman-or-local .mode=ap datapath.bridge=bridge \
    disabled=no
/interface wifiwave2 cap
set caps-man-addresses=192.168.88.1 enabled=yes
5

Hello, I am having a similar problem and I am looking for a solution with the support team.
When you enable wireless debug in the logging section, will “authentication rejected” appear in the logs when an error occurs? We may be experiencing the same problem.

For logging:

/system logging
add disabled=no topics=wireless,debug

2023-09-13 014705.jpg

6

Hello! Added logging according to your sample. But there are no entries in the logs with authentication problems.
Screenshot 2023-09-13 072706.png

7

@nopresent:
can you please provide full config of both devices ?

@İmposss
authentication rejected means what it says.
There is something wrong with authentication for that device/radio.
Please create new thread and post your problem and config there.

8

@holvoetn:
Added cofig, thanks
config_ax2.txt (11.4 KB)
config_ac3.txt (6.55 KB)

9

Hello, today we decided with the support team that the problem occurred because the device causing the problem does not support the IEEE Std 802.11‐2020 standard. The device I mentioned has Android 9 version and received the last update in 2019.
Thanks