Just got myself a pair of HAP Ax3 routers running on OS v7.7. Been trying to get WiFiWave2 interfaces working on Capsman (configured via CLI as Winbox GUI does not have this option) but to no success. Interface recognized to be controlled by Capsman but no wifi clients can successfully login to the router.
Am using configuration profiles (specifying country, ssid) + channel profile (specifying band type and channel width) + security profile.
Seeking all the gurus here for comments and pointers if anyone has successfully gotten this to work.
I would like to see that also. Actually, I don’t understand why Mikrotik doesn’t address this as well in their Wiki.
It doesn’t help anyone to provide features without any tools to configure them.
Verbatim reply from support - The configuration example in the documentation is written for a setup where CAPsMAN manages an interface, which is on a different device.
To manage an interface, which CAPsMAN is on the same device, just set
/interface wifiwave2 set wifi2 configuration.manager=local configuration=5gConfig(configuration profile which I setup)
For remote devices, I just have to follow the documentations to get it working e.g.
/interface wifiwave2 cap set enabled=yes
/interface wifiwave2 cap set caps-man-addresses=x.x.x.x
/interface wifiwave2 set wifi2 configuration.manager=capsman (or capsman-or-local)
Tell me, did anyone check if such a configuration supports CAPs that do not know how to wave2? Or do they still need a separate CAPSMAN server for them?
Current (in reality pre-beta) version of capsman2 doesn’t support legacy capsman clients and legacy capsman doesn’t (and never will) support wave2 clients.
However, in another thread some MT staffer wrote that MT will consider adding support for legacy capsman clients to capsman2. As usual, no commitment has been made and there’s certainly no ETA. But crowds (myself included) are thrilled by such a possibility and some even consider it “almost done”.
/interface/wifiwave2/capsman> print
enabled: yes
ca-certificate: auto
require-peer-certificate: no
package-path:
upgrade-policy: none
generated-ca-certificate: CAPsMAN-CA-18FD74FE92C0
generated-certificate: CAPsMAN-18FD74FE92C0
/interface/wifiwave2/capsman/remote-cap> print
Columns: ADDRESS, IDENTITY, STATE, BOARD-NAME, VERSION
# ADDRESS IDENTITY STATE BOARD-NAME VERSION
0 127.0.0.1 ax3 Ok C53UiG+5HPaxD2HPaxD 7.8beta2
Standart FW including:
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
Looks like does provision, but still nothing happans.
Addad hAP ac3 with WifiWave2 as CAP controled by Capsman on hAP ax3 . Still dont wokr. All i can see:
on Capsman hAP ax3
/interface/wifiwave2/capsman/remote-cap> print
Columns: ADDRESS, IDENTITY, STATE, BOARD-NAME, VERSION
# ADDRESS IDENTITY STATE BOARD-NAME VERSION
0 MikroTik Ok RBD53iG-5HacD2HnD 7.7
1 127.0.0.1 ax3 Ok C53UiG+5HPaxD2HPaxD 7.8beta2
on cap hAP ac3
/interface/wifiwave2> print
Flags: M - MASTER; B - BOUND; I, R - RUNNING
Columns: NAME, CONFIGURATION.MODE
# NAME CONFIGURATION.MODE
;;; managed by CAPsMAN
0 MBI wifi1--2Ghz ap
;;; managed by CAPsMAN
1 MBI wifi2-5Ghz ap
I really hope they’ll add support for capsman forwarding in the next release, not the best solution to add vxlan/eoip everywhere and bridge cap interfaces locally