Hey everyone,
I’m in my first 10+ project utilizing the new CAPsMAN and I ran into some issues and I’d like to hear your opinion about those.
I use the latest version of Winbox (3.39) and RoS 7.10.2 at the moment.
1.) Winbox - Provisioning - Rearrange: There is no way to order the provisioning templates. If I need to rearrange them I need to create those in the order that is needed. It’s not a big issue but a nuisance that did work in legacy CAPsMAN
2.) Winbox - Provisioning - Name-Format: As before, it’s not a big deal but there’s no way to set the name-format via Winbox; did work in legacy CAPsMAN, too.
3.) Winbox - Registrations: In CAPsMAN1 you could klick on any device in the registration table and copy it to the access list. You could also open up the information via double click and were able to copy and paste the displayed infos to your windows clipboard; CAPsMAN2 does not support this, (hopefully) yet?
4.) Running CAP on CAPsMAN device: It took me ages to get my cAP ax that has the role of CAPsMAN to get the all the configurations in the corresponding template provisioned to the interfaces. I encountered several issue which were
- For a long time I only had the info “managed by capsman” in red letters on the local interfaces but they got no configuration. I then realized that the provisioning via the tab Remote Cap didn’t do anything and I had to trigger the provisioning via the Radios tab
- Once I joined an interface/radio I was not able to exclude it again without disabling or deleting a few key elements of the configuration. I’d really like to know if there is a simple or elegant solution to exclude an radio interface from CAPsMAN that is running on the physical device that is managing CAPsMAN.
- If i disable CAP after the interfaces were successfully joined they still get provisioned even if the manager on the interfaces was set to capsman only and the device got restarted after disabling CAP. Can someone else reproduce this behavior?
- Running a CAP interface on the same physical device as the CAPsMAN service took a lot of trial and error. I had the same issues on my cAP ax and on a hAP ax2 of a colleague of mine… Is there anything I have missed, is it really that much different than joining a CAP from a different device?
5.) I really do miss the option to channel all the traffic via the CAPsMAN device, especially for temporary setups. Am I the only one who set up their caps in that way? (Datapath → Local-Forwarding: no)
Thx for commenting in advance!
EDIT: I just realized that it seems that #4 are non-issues because the scenario is not supported? 