I was able to get it semi-working by activating CAPsMAN on the HAP AC itself.
Then I noticed that the path to CAPsMAN is slightly different:
It is "Wireless --> CAPsMAN --> CAP Interface --> Manager" (HAP AC) instead of "WiFi --> Remote CAP --> CAPsMAN" (CRS326).
So next I disabled the CAPsMAN on HAP AC and tried the "WiFi --> Remote CAP --> CAPsMAN" route on the HAP AC.
It doesn't work.
I exported the configuration with CAPsMAN enabled in both ways and compared them against each other.
The glaring difference was this:
Naturally, I tried to enter those commands into the terminal on the CRS and I couldn't. The command /caps-man simply doesn't exist (doesn't show up when hitting F1, no auto-complete).
Allegedly, the CRS on RouterOS with license level 5 should be able to CAPsMAN other devices. Is this no longer true with the newer versions of RouterOS?
Then I noticed that the path to CAPsMAN is slightly different:
It is "Wireless --> CAPsMAN --> CAP Interface --> Manager" (HAP AC) instead of "WiFi --> Remote CAP --> CAPsMAN" (CRS326).
So next I disabled the CAPsMAN on HAP AC and tried the "WiFi --> Remote CAP --> CAPsMAN" route on the HAP AC.
It doesn't work.
I exported the configuration with CAPsMAN enabled in both ways and compared them against each other.
The glaring difference was this:
Code:
/caps-man managerset enabled=yesAllegedly, the CRS on RouterOS with license level 5 should be able to CAPsMAN other devices. Is this no longer true with the newer versions of RouterOS?
Statistics: Posted by itengelhardt — Sun Feb 04, 2024 11:45 pm