Thank you for the suggestions provided so far, including methods for configuring the CAPsMAN controller.Did you even look at the Help pages I provided ?
The info is there...
Capsman for AX devices:
https://help.mikrotik.com/docs/spaces/R ... iFiCAPsMAN
Based on my troubleshooting and analysis of my hAP ax lite (L41G-2axD) running RouterOS 7.18.2, I've encountered some conflicting information regarding how to configure the CAPsMAN controller, which I'd like to clarify with the community.
I have seen configurations/guides that suggest setting up the CAPsMAN controller by:
Enabling a CAPsMAN-related feature using commands like /interface wifi capsman set enabled=yes interfaces=...
Defining security profiles, configuration profiles, and provisioning rules using commands under the /interface wifi security add ..., /interface wifi configuration add ..., and /interface wifi provisioning add ... menus.
However, my system's actual behavior and status contradict this approach for RouterOS 7.18.2. My troubleshooting (including /system package print and analyzing the full standard default configuration export from RouterOS 7.18.2 on my device) clearly shows:
The dedicated capsman package is missing from the default installation.
When trying to use the standard CAPsMAN controller configuration commands like /caps-man security add ..., /caps-man configuration add ..., etc., I consistently get the "bad command name caps-man" error.
This strongly indicates that the primary command tree for standard CAPsMAN controller configuration (/caps-man) is not available on my RouterOS 7.18.2 system due to the missing package.
My understanding now is that the correct and standard method for configuring the full CAPsMAN controller functionality in RouterOS 7.18.2 requires the /caps-man command tree. The configurations defined under /interface wifi security, /interface wifi configuration, etc., seem to be intended for standalone APs or possibly belong to an alternative/older CAPsMAN configuration method (perhaps from earlier ROS v7 versions like 7.11.2, as seen in some guides).
Therefore, following a method that defines CAPsMAN policies using /interface wifi security/configuration/provisioning is, based on my system's state, not the correct approach to configure the standard CAPsMAN controller in RouterOS 7.18.2 and will likely not work as intended for central management using the standard CAPsMAN engine.
The root cause of my inability to configure CAPsMAN controller remains the missing capsman package, which prevents access to the necessary /caps-man commands.
My current focus is on successfully obtaining and installing the capsman-7.18.2-arm64.npk file from the official Extra packages to get the /caps-man command tree working, so I can configure the controller using the standard method.
Could someone confirm if my understanding of the required method for full standard CAPsMAN controller configuration in 7.18.2 is indeed using the /caps-man command tree, necessitating the capsman package installation, and that the /interface wifi ... methods for controller config seen elsewhere are not applicable here?
Thank you for your patience and guidance in clarifying this.
Statistics: Posted by VIPuts — Fri May 02, 2025 9:07 am
