I have network based exclusively on RouterBoard devices. All devices are on RouterOS v7.20.7. I use CAPsMAN to handle all WiFi devices.
Now I have plan to get some devices replaced and also expand network. I read some comments that new generation of devices are using new CAPsMAN and that it is not compatible with old CAPsMAN.
There are some claims that old devices should stay with old CAPsMAN and for new devices I would have to create new separate CAPsMAN and handle them separately. Information is scarce and not clear, search does not lead to nothing useful, so I have to ask.
If I get new generation devices would I be able to configure them to use the same CAPsMAN configuration as already existing devices do? By the same CAPsMAN I primarily mean to be able to manage configuration centralized in one place. Would I be able to set old and new CAPsMAN to share configuration?
I have quite complex CAPsMAN configuration with number of CAP interface, several SSIDs, various channels used, VLANS, Access Lists… and I am not happy to have to set and update all that configuration twice just because Mikrotik decided to introduce separate CAPsMAN for new devices.
Is there some tutorial that clearly explains what to do in such situation with “old” and “new” generation devices mixed in the same network?
This contradicts the usefulness of any subsequent question.
If you already have peripherals running 7.20.7 and already have wifi,
what difference does it make with new devices?
The "new" (and old) CAPsMAN are linked to the wi-fi radio drivers used on the single, specific devices.
Set aside - for a moment - CAPsMAN.
Some (older) devices radios settings are under wireless (old architecture/drivers).
Newer devices settings are under wifi (new architecture/drivers).
Some devices in the middle can be set either under wireless or under wifi depending on which driver is in use.
In practice, if the device runs any of wifi-qcom or wifi-qcom-ac (or wi-fi-mediatek) it needs to be managed by the "new" CAPsMAN, if the device runs wireless package it needs the "old" one.
Some capabilities of the "old" CAPsMAN are lost (or the way to replicate them is different) in the "new" CAPsMAN, just like some features of the newer drivers are different when compared to the old ones.
It is said that it is matter of devices, not just RouterOS version, like, new devices have to use new WiFi and new CAPsMAN, and old devices have to use Wireless and old CAPsMAN.
All my devices now have WiFi and Wireless but all wireless interfaces are in Wireless. WiFi is empty. I guess this means, these are “old” devices and there is no support in WiFi for them.
I understand that new devices have wireless interfaces in WiFi not in Wireless and new CAPsMAN has to be set there. Old devices cannot use new CAPsMAN and new devices cannot use new CAPsMAN.
I might be wrong but info on all this is scarce and confusing.
Thanks. You did not help much as you mostly repeated what I already found.
Wireless interfaces are not a problem. It is understandable, different set of drivers etc.
Confusion is with CAPsMAN. For start, they insist that both are called the same, although they are not the same and not even compatible, and there is no clear instructions how to handle situation.
So far it seems I would have to set two CAPsMAN that are completely separate, i have to configure each independently to get then to the same job, if I do some configuration change I have to do it in both places, if I want to check network status, i have to check both places… etc… it seems like salty joke. The whole point of CAPsMAN is to have everything in one place.
To make it worse, my network is actually three physically separate networks, and I already had to do some partial replication of CAPsMAN configuration as there are people who move a lot among three networks and they have to have proper access wherever they are.
I have to spend substantial budget for network upgrade and I do not want to end up in some mess I cannot handle.
I have responsibilities and have to answer to higher instances both in budget spending and reliability of the network. Just because of this uncertainty I am considering to ditch Mikrotik completely and switch to other brand that is more reliable.
According to the good Mikrotik guys ALL the info you need can be found in this table (also linked in the given thread):
If you decide to leave the Mikrotik ecosystem for a better vendor/manufacturer, make sure to let Mikrotik know how a relevant part of the decision is due to their confusing and lacking documentation.
Thanks again, but all this info I already found and it is useless as explanation how to seemingly upgrade. They are paying particular attention not to touch that question.
I have years of experience with Mikrotik and I am sure they do not care. After all, proof is this mess they created.
Similarly with update that wrecked all OSPF because new OSPF was incompatible with old one. It their manner, to provide new “better” stuff with no attention to vertical compatibility.
As others already explained there are 3 classes of devices and the possible solutions are different for each of device class. If you want to get more concrete advice about how to improve/upgrade your setup, start by writing concrete information about your setup ... you already wrote that all of your devices are running ROS 7.20.7; proceed with writing exact device models you're using (also include the CAPsMAN device, it does matter). Without you telling us concrete information we can only re-iterate the general information you received above and which you claim to know already (but obviously fail to apply to your particular setup).
Seen in another way, devices that cannot run the "new" CAPsMAN (i.e. they cannot run either wifi-qcom or wifi-qcom-ac) are largely (or all?) pre-AC (or pre-wifi5) speed, so - even if wortking just fine - are to be considered obsolete in the view of a network update/expansion.
So it should be considered replacing them with at least AC devices, which brings us back to what rextended stated, all the devices will be able to run the "new" CAPsMAN, and - once everything will be migrated to it there will be only the "new" CAPsMAN managing all devices.
In other words there will be the need of only one (large) migration from the "old" CAPsMAN to the "new" one, complex as it may be, but very likely - unless this migration is properly tested and planned - it will take some time and so - temporarily there will be the need to run both versions side by side.
for a better vendor/manufacturer, make sure to let Mikrotik know how a relevant part of the decision is due to their confusing and lacking documentation.