Strange capsman behaviour

RouterOS General
1

I have 3011 as GW with capsman manager. I have 4 cAP, everything in bridge mode (eth1,2,wlan1,2).
Now I`d like to separate 5GHz clients from 2.4GHz clients.
My setup:

  1. I created bridge-wifi with 192.168.10.1/24 addressin the GW(capsman)
  2. I`ve setup dhcp on the bridge-wifi
  3. I Made 2nd datapath2 (no bridge, no local or client forwarding) in the capsman.
  4. I edited config for 5GHz and change to datapath2
    5 Restarted caps client in the both APs

But now I can see the both radios in the CAP interface but the both are the shadow (XS not RS) and 2nd connect after 20minutes with no error in the log.
I could see this in the log:

22:40:33 caps,info AP_mk_obchodaci_strop-2: selected channel 5640/20-eeCe/ac/DP(27
dBm)

Radio was disconnected in the manager (CAP interface, empty MTU) and iconnect itself after 20min.


Where is the problem or what is the best way to make diiferent LAN managed via capsman?
I have several networks with quest networks in 2.4GHz in the different subnetr and all are working properly.

ROS 6.49.2 in all boxes.

2

About the timing … 5640/eeCe is using DFS “weather channels” , every attempt for channel selection will need a full 10 minutes of radar detection. (20 minutes indicates it needed 2 or more attempts).
During radar detection the radio TX is OFF and does not transmit anything. If radar is detected (even false positives exist), then the radar detection starts again for the required period.
DFS Weather channels are 5600, 5620 and 5640 (120,124,128) AFAIK. 5640/eeCe is 5600+5620+5640+5660
Other DFS 5 GHz channels have a 1 minute radar detect requirement. There are mostly only a few non-DFS channels (country regulation dependent).

3

I think youre right wtih the "DFS delay", today they called me they be able to connect internet via 5GHz today so it seems its all right.

4

Edit:
It`s strange because I can see all radios in XS status but I can see connected clients in capsman now.