I followed this video as a reference: https://www.youtube.com/watch?v=bHotZT41w3E
The setup is the same: hAP ax⁵ acting as the CAPsMAN controller and hAP ac² configured as a CAP, connected via LAN in different rooms.
Everything seems configured correctly, but the hAP ac² wireless interfaces do not appear under CAPsMAN on the hAP ax⁵. I can’t see what’s wrong. Any ideas?
Looks like a new model
Is wireless package replaced by wifi-qcom-ac in ac²?
As @ortazebra says, wif-qcom-ac package on ac2. And also wifi-qcom on ax3. This will allow new CAPsMAN to run. Or use the wireless package on both for old CAPsMAN. [Corrrection: wireless package does not work on ax devices]
There may be other issues to resolve, but lets start by making sure we have compatible drivers.
No, wireless package is not compatible with AX devices (including ax2 or ax3 or ax5). So it has to be wifi-qcom-ac (on ac2) and wifi-qcom (on axN).
@togglenation Please post full configuration of both CAPsMAN and CAP devices.
In a sense yes. Either can be installed and each has its own strenghts. Legacy wireless package supports proprietary protocols (nstreme, nv2), better diagnostics and visibility (wifi snooper, wifi scanner, etc.), better configurability (VLANs done in driver, etc.). But: works only with legacy CAPsMAN.
New wifi-qcom-ac is much faster, supports new features (such as 802.11 mobility r/k/v), works with new CAPsMAN. But uses more storage space[*] and more RAM.
[*] beware of ROS v7 and wifi-qcom-ac on hAP ac2 ... device has only 16MB storage space which will be barely enough for ROS and wifi-qcom-ac packages. If device has anything but (almost) trivial configuration, then storage space might drop to 0 which causes severe problems (starting with inability to upgrade ROS via normal means, also instability in running). Another issue might be with 128MB RAM (there were units with 256MB RAM which don't suffer from the problem), in certain cases device might run out of memory (and reboot) ... possibly if there are many active wifi stations connected to same AP.
My CAPSMAN router is hAP ax S , my CAPs router is hAP ac², so I assume it will need wifi-mediatek and hAP ac² will need wifi-qcom-ac
Will it be enough if i only switch to wifi-qcom-ac on hAP ac² ?
I am not sure to understand your doubts.
In a nutshell:
if you want wifi to work on the hAP Ax S you need wifi-mediatek on it.
If you want wifi to work on the hAP AC 2 you can choose between:
Only #2 will provide you with the settings under wifi (aka new CAPS/CAPSMAN) like the Ax S will have.
I’ve done everything that’s mentioned, and now all works just fine.
I’m assuming that i need to use 2.4g - n netwrok and 5g - ac network to make it work for hap ac2 since it doesn’t support ax.
Yep, n (only) on 2.4 GHz is fine, i.e. supported-bands=2ghz-n
Maybe you want to try with both n and ac on 5 GHz, i.e. supported-bands=5Ghz-n, 5ghz-ac.
Or simply omit setting supported-bands (or unset it from current settings) ... this way device will work with whatever hardware supports. Setting this property is only necessary when one wants to "downgrade" radio to older technologies.
If set to something hardware doesn't support (e.g. 2ghz-n on 5GHz radio), then radio will not start.