I currently have an RB5009 and I use CapsMan V2 on it to provision several hAP AX3 as APs. I recently acquired an hAP AX S unit, and tried to provision it from the RB5009. This did not work. I enable Cap mode on the AX S unit, and I can see this unit in the Caps manager “Remote CAP” tab, but I can’t see the radios from this new unit under the Radios tab. The Hap AX S uses ‘wifi-mediatek’ as the WiFi package, not Wifi-Qcom. Is this the reason I can’t provision it? Should CapsMan V2 work to provsion the AX S unit? What am I missing? As always, help is appreciated.
How do your provisioning rules look like?
As above and on the CAP [hAP ax3], using webfig WiFi -> WiFI -> CAP is the CAP enabled and a valid CAPsMAN server specified?
It does not work this way. CAP can still join CAPsMAN and not have radios provisioned. It is all up to the CAPsMAN provisioning rules.
Interesting...
Can you test using wifi-mediatek driver on RB5009 ?
Shouldn't be needed but worth to try.
Apart from that, your provisioning rules might be worthwhile as wel to be reviewed.
I found my mistake. For each WiFi radio on the CAP, you need to specify the manager as ‘capsman’. Double click of the WiFi interface, and under the configuration tab there’s a ‘manager’ variable. Specify capsman here. The bold lines below beginning with 'set' are the steps I forgot.
When I reset the configuration of the AX S to Cap mode, the following configuration was applied:
/interface bridge
add admin-mac=04:F4:1C:9D:30:D7 auto-mac=no comment=defconf name=bridgeLocal
/interface wifi datapath
add bridge=bridgeLocal comment=defconf disabled=no name=capdp
/interface wifi
#no connection to capsman
set [ find default-name=wifi1 ] configuration.manager=capsman datapath=capdp
disabled=no
#no connection to capsman
set [ find default-name=wifi2 ] configuration.manager=capsman datapath=capdp
disabled=no
/interface bridge port
add bridge=bridgeLocal comment=defconf interface=ether1
add bridge=bridgeLocal comment=defconf interface=ether2
add bridge=bridgeLocal comment=defconf interface=ether3
add bridge=bridgeLocal comment=defconf interface=ether4
add bridge=bridgeLocal comment=defconf interface=ether5
add bridge=bridgeLocal comment=defconf interface=sfp1
/interface wifi cap
set discovery-interfaces=bridgeLocal enabled=yes slaves-datapath=capdp
/ip dhcp-client
add comment=defconf interface=bridgeLocal
/system clock
set time-zone-name=America/Chicago
1 Like
Again, thanks for your comments and suggestions.
Sorry i am late…
I picked up a hAP S as I was hoping it would fill a spot I need in installs all the time.
I quickly found out that the Media Tec driver doesn’t interact the same as QUALCOMM driver. I have devices that connect for a while then drop. I have devices that show as connected but don’t pass packets. I have roaming behavior COMPLETELY different from the wAP AXs.
Basically… I have more problems that it caused. hEX poe still needed.
So the hAP S is sitting in a box waiting for caps-man updates.
Using 160MHz channels?
Nope.
I live in a crowded environment. 80Mhz is fighting. 160 MHZ… my own APs would be my own worst enemy
My finding is that some phones like my S24Ultra takes some more time to connect hAP ax S when it broadcasts 160Mhz network, but laptops based on IntelAX211 have no problem with that. It happens when hAP works as standalone router, with vlan filtering etc.
In my home setup :
RB5009 with capsman
1x L23UGSR-5HaxD2HaxD with https://www.printables.com/model/945288-mikrotik-routerboard-l23ugsr-5haxd2haxd-box/files
1x wAP AX ( for tests replaced by hAP ax S)
After connecting hAP ax S there is no difference in roaming or I didn’t noticed any oddities compared to wAP ax. Good to mention that those APs don’t broadcast with “full power”, its limited to 12dB on each device - reason is that place have 4 rooms and each AP serves 2 rooms, resulting in good signals everywhere and functional roaming, even with 160MHz channels.
One oddity I noticed is that when L23UGSR-5HaxD2HaxD broadcasts in 160MHz channel and hAP ax S in 80 MHz channel devices prefer sticking to 160MHz channel longer and roams to hAP less often despite better signals from hAP
My thermostats won’t stay connect to the hAP AX S. My garage camera shows as connected but wont actually pass packets.
I tried to use ACLs to tell the devices not to connect to the hAP. That didn’t work and was not going to be a solution I was going to “just accept in the wild.”
Which band do they use? 2G/N? 2G/AX? WPA2 or WPA3?
Thermostats use 2.4G-N WPA2
Camera uses 2.4G-G WPA2