I have some observations and questions concerning forwarding modes in Capsman V2.
I have done some experimenting and I can see by default Capsman will capture all traffic to/from an AP and route them over the common bridge interface in the Manager Forwarding mode.
This makes sense if the access points aren’t on the same ethernet switch and you are trying to unify a Wifi network that has it’s AP’s connected by routers and not switches. The system I was setting up had 4 Capman clients and switched/powered/managed by a 750UP and I could see it’s CPU was going to get overwhelmed very quickly doing the managed forwarding - it seemed pointless.
I then tried Local Forwarding mode and that works as well and I can see that Capsman is still controlling the behaviour of the APs but isn’t doing any bridging/forwarding for them with the subsequent lower CPU use. Much better!
I had also set Access List power levels to kick a client off if it was below -80dB. Does the kick/reconnect handover behaviour change if Local Forwarding mode is used instead of Managed Mode? In Local Fowarding mode I had an iPad that would drop and a few seconds later reconnect to another AP as I wandered around the house. The other site where I used Managed Forwarding seems a lot smoother with the AP transitions - no noticeable drop period.
I would recommend you suggest in the manual that if you are using Capsman in Managed Forwarding mode that the manager has plenty of CPU grunt, such as a RB850x2 or better - the 750UP, even the new one, won’t cope well.