I have a bunch of cAPs installs out there and have a pretty good template to apply to my routers to function as the router and controller.
I set up the caps configurations to allow client to client forwarding and local forwarding.
After putting caps man on the primary router… I log into each cAP AC or wAP and set them to caps-mode via command line.
When the wireless access point comes back up… it gets the configuration from caps-man and they work. One SSID has a VLAN tag and that is applied properly. Several SSIDs are put on each radio… and work when tested.
A problem I seem to have nailed down…
If I set up caps-man on the hAP AC2 and then tell its wireless interface to JOIN THE CAP…
All SSIDs start transmitting and the configuration looks like the other caps.
The First SSID allows clients to connect and use the internet and local services.
EVERY OTHER SSID or Virtual AP or Slave cAP DOES NOT.
If you look at the registration table… you will see clients connected to that SSID/Interface. BUT NO TRAFFIC PASSES. It looks like its working in Winbox… but clients say they cant connect.
I mocked up the system at my office and when I connect to the First SSID on the radio… works perfect.
Connect to SSID 2 or 3 and the devices never gets and IP address from the router. Client devices get stuck on obtaining an IP address.
Now that I found this… I have turned off the Virtual APs on my routers that run caps man. This solved a bunch of client complaint tickets at once.
Can others confirm this?