They said that hap ac2 won’t ever get WifiWave2, and there we have it, and it is working great. So maybe, just maybe, Mikrotik could give us another surprise and enable new Capsman on mipsbe devices, at least ones with enough memory (like mipsbe based wAP ac?).
It would be great if you can help to split wifi-qcom-ac in 2 packages, only one IPQ4019 or QCA9984 driver ?
Due to hap ac2 has space limit while upgrade to this version with zerotier package space need another 117 kB more, log are said like that
This split may help to fixed this issue, as we can reduce size of package.
If it can solve space problem this must be great support.
It has been a problem for two years, yes. But there is no explanation why this problem even exists. In any other Linux system you can separately install drivers for each device without having such conflicts. When you have more than one driver that would support a certain chip, there would be a way to work around that by having the drivers detect their hardware in a certain sequence.
(so wifi-qcom would pickup the 5 GHz device and wireless would pickup the 2 GHz device, and find the 5 GHz device already supported by wifi-qcom so it would not bother with that)
I would have expected that now that you can have BOTH management menus available at the same time, you would be able to do this on a RB4011.
Let’s not forget, ROS is, while based on it, not as flexible as Linux.
I think the base problem on RB4011 is effectively that there are 2 different chipsets used, one for each of the radio bands and somehow ROS is only able to use 1 driver: either legacy, either wave2. But not both.
However, that’s pure speculation from my side.
I assume their legacy wireless is not just a driver alone. possibly the legacy wireless has interaction with several system modules (routing/firewall) and makes it impossible to have new/legacy running same time.
The page shows that “New Capsman only controller” needs “routeros” only, while the video “https://www.youtube.com/watch?v=AkBIQxi-VKs” shows that “Package since 7.13” for “CAPsMAN for up to WiFi5 APs” is “routeos+wireless”. Which one is correct?
Because you are quoting “new capsman ONLY”, but video talks about old WiFi5 devices, which in the table is “running two capsmans at the same time” (old + new)
For using the old CAPsMAN, the (additional) wireless package is required.
The new CAPsMAN is part of the routeros package, this new CAPsMAN version can be used for managing the wifi-qcom (all ax devices) and wifi-qcom-ac (supported ac devices) packages.
In other words, a switch like CRS326-24G-2S+IN that acts as new capsman only just needs routeos 7.13 without package “wifi”. On the other hand, an AP like RBwAPG-5HacD2HnD that supports new wifi just needs routeos 7.13 with package “wifi-qcom-ac”. Is it correct?
Yes, I read it again. My AP runs with routreos + wifi-qcom-ac and is waiting for capsman’s control. My switch acts as new capsman with routeros but cannot find AP’s wifi interface. Because the table does not mention the switch device but wifi device only, I am not sure whether my switch needs wifi-qcom-ac or I neglect something else.
Any hint would be appreciated.
Eventually new caps works. Now the way to putting AP under new CAPMAN’s control is the following 3 steps on AP. No1. WiFi–WiFi–CAP-Enable; No2. Configuration–create New WiFi Configuration–Configuration–Manager–capsman; No3. Apply configuration to WiFi interface.
According to the table RB4011iGS+5HacQ2HnD should run dual capsman using routeros+wireless package. Here http://forum.mikrotik.com/t/remote-cap-in-7-13-using-capsman-1-and-2/172106/1 people are struggling to have it running. Looks like CAPsMANs are conflicting each-other. Can we get a clear statement if it stable and possible at all for the particular product?
Any hint for a proper setup? it should not come to a hint game.