Problem with state cap in interface List

Subject: RouterOS 6.49.20 legacy CAPsMAN - local CAP interface on CAPsMAN manager stays disabled while remote CAPs work

Hi,

I have a reproducible issue with legacy CAPsMAN on RouterOS 6.49.20.

Hardware

  • CAPsMAN Manager: RB941-2nD (hAP lite)

  • Remote CAP #1: cAP lite

  • Remote CAP #2: cAP ac

All devices run RouterOS 6.49.20 (long-term).

Configuration

  • Legacy /caps-man (wireless package)

  • Local forwarding

  • Dynamic provisioning

  • cAP lite and cAP ac are discovered and provisioned correctly.

  • cAP ac also has a virtual 5 GHz SSID (slave configuration), which works correctly.

What works

  • Remote CAPs connect successfully.

  • Both radios on cAP ac are provisioned.

  • Clients connect normally.

  • Roaming works.

  • Virtual SSID on cAP ac works.

Problem

I would also like the local wireless interface on the CAPsMAN manager (hAP lite) to be managed by CAPsMAN.

When I enable CAP on the hAP lite:

/interface wireless cap
enabled=yes
interfaces=Willage
caps-man-addresses=127.0.0.1

(or using the manager IP address instead of 127.0.0.1)

the local wireless interface changes to:

managed by CAPsMAN
X Willage

The interface becomes disabled and stops transmitting.

If I disable CAP, the same interface immediately starts broadcasting again using the local configuration.

Observations

  • Remote CAP list contains only:

    • cAP lite

    • cAP ac

The hAP lite never appears as a Remote CAP.

Remote radios are visible and provisioned correctly.

The local wireless interface receives CAPsMAN parameters (SSID, channel etc.), but never becomes Running.

Another thing I noticed

In CAPsMAN → Interfaces I see:

cap6   RMB
cap9   MB
cap10  MB
cap11  B

where

  • cap6 = cAP lite

  • cap9 = cAP ac 2.4 GHz

  • cap10 = cAP ac 5 GHz

  • cap11 = virtual AP

However, on the cAP ac itself I see:

wlan1  RS
wlan2  RS
wlan3  DRS (Virtual)

Everything works correctly, but CAPsMAN Interfaces do not show "R" for cap9/cap10.

Questions

  1. Is it officially supported in RouterOS 6.49.x (legacy CAPsMAN) to have the CAPsMAN manager manage its own local wireless interface as a CAP?

  2. If yes, what additional configuration is required?

  3. Is the missing "R" flag on cap9/cap10 expected behaviour with local forwarding, or is it a display bug?

Thank you.

cap6 CAP lite

cap11,12 CAP ac