Hi All,
I’m pretty new with CAPsMAN, I followed this guide for configure a new AP on my office: https://mum.mikrotik.com/presentations/MM15/presentation_2709_1444122809.pdf
The scope is to create an internal Wifi network that can access the LAN and a guest network with hotspot and captive portal.
You can see my configurations in attachments.
I have only one AP with 2 wlan (2Ghz and 5Ghz) and I’m using CAPsMAN manager from our firewall that is a VM on VMWare.
The problem is that if I set the wifi config in the cap configuration on the wireless tab everything works fine but with the provisioning not. I tried different configurations and none worked.
I want to use provisioning because I wish to handle multiple SSID on the same CAP.
UPDATE:
I did a few more tries without success. It seems that there is something deeply wrong with my configuration.
What I want to do (just to be clear) is use my AP with both the wlan (2Ghz and 5Ghz) for create a “normal” wifi network and a guest network.
The first one is accessible using a simple WPA key and can have full access to the LAN, the second must use a captive portal and can only access the internet.
SSID must be different (Inoptim-WIFI and Inoptim-GUEST).
Another mandatory thing is to use CAPsMAN, how can I do this?
Secondly the datapath options on your capsmanager are normally not needed when using “local-forwarding” (see: https://wiki.mikrotik.com/wiki/Manual:CAPsMAN#Datapath_Configuration).
You should set the bridge where your wifi-interfaces should be added to on your clients under /int wire cap, for example: “/int wire cap set bridge=bridge”. Additionally you should not add the wifi-interfaces manually to your bridge on your clients:
Please delete those two interfaces from that bridge since they will get added dynamically when the client connects to capsman and the configuration has implemented the “bridge-setting” under /int wire cap.
I need to mention that im not sure if the VLAN configuration will work with local forwarding! Maybe you will need to use capsman-forwarding. Not sure since we dont use client-forwarding with VLAN in our setups.
After you have made the changes please reconnect the client to your capsmanager and try it again
Edit: One more thing: I would suggest you to use the same software version (manager has 6.44.2, client has 6.42.10 in your case)