Can I just clarify my memory on this one. On a hAP ax2, you can’t have local Wi-Fi on the router enabled AND have both configuration for legacy CAPsMAN and new CAPsMAN?
When you install the wireless package, the wifi-qcom package disables but both CAPsMAN interfaces are present. If you try enabling wifi-qcom, wireless is disabled and legacy CAPsMAN interface disappears.
You've probably already answered yourself.
Just checking that this was the restriction mentioned when ROS v7 was introduced. Is this a hardware or software limitation?
No idea, this is probably more of a question of semantics. But from my experience with devices without wireless hardware on the board, new CAPsMAN works just fine with no need for wifi-qcom or any wireless package. And I seem to recall that to get old CAPsMAN on the same device, the wireless driver had to be installed. So I think both would coexist on a device without wireless hardware on the board.
It then makes sense that with wireless hardware on the board, you can use the wireless driver and run both new and old CAPsMAN. But if you run the wifi-qcom package [or wifi-qcom-ac], the wireless package will, of necessity, be unloaded, resulting in the old CAPsMAN not being available.
The problem is how wireless card drivers are packaged into optional packages. Optional package wireless, which is required for running legacy CAPsMAN, disables the other optional package wifi-qcom, which contains required drivers for ax wireless cards. And vice versa.
I seem to remember a trick to have both packages active at the same time, it was posted on this forum.
But then forcing both CAPsMANs to run on same device doesn't give any benefits other than having configuration on single device. Configurations are distinct and both CAPsMANs don't cooperate, so running legacy CAPsMAN on a separate (legacy) device won't affect any function of a hybrid (legacy+new capsman) wifi network.
Indeed… only realised this during testing. Client RB4011iGS has gone from v6 to v7 update and has both “WiFi” and “Wireless” options with their separate CAPsMAN configurations - but only RouterOS and Wireless packages, no hint of wifi-qcom.
I know we’ve been through this all before but IMO they could have been named better like “Wireless (legacy)” and “Wireless (new)”. Okay to change WinBox but scripting is kind of stuck now. Will become less of a problem over time as the older kit is retired.
It’s just another of those things that catches out non-technical users and keeps Mikrotik firmly in the hobby home or supported environments, i.e. not really SOHO.
