can anybody suggest any kind of strategy on how to fight this and get some better results. newly set AP, no encription, BTest server is runing on AP itself, BTest for Windows runinng on client. I am only one on 5GHz part of aether in my area, chanel is clear on there is only one client at the time connected to wAP

never run btest on the same device you want to measure performance, you will get much lower results because btest consumes most of the cpu resources

nvm

Little pre-history. This AP is part of 3 member group covering small office. I did managed to set all tree in correct configuration managed by CAPsMAN on rb750Gr3. Everything worked except I was getting transfer speed bellow expectations (copying speed maxing in the range of 10MB/s). To troubleshoot, I removed one unit from group to test it working as independent AP. That screenshot in first post was taken during that phase. I tried lot of things and finally did full reset, installed new drivers on my laptop and finally got some results (my assumption is that either I made some mistake in bridge configuration or some internal error made things go sideway). Copying was able to reach speeds of 30-35 MB/s - something I expected based on reviews I picked on the net. Wrapped everything and again joined AP to CAPsMAN just to be unpleasantly surprised that copying speeds returned to 10MB/s range while CPU was constantly ~50% on both wAP and rb750Gr3. Returned to googling and picked up idea to fiddle with local forwarding. I've enabled both Local Forwarding and Client to Client Forwarding in Datapath configuration to get CPU usage to drop to ~1% and copying speed to reach ~30MB/s again. As far as i am concerned, problem solved.

Can somebody explain what would be benefit of using CAPsMAN as traffic controller instead of using local bridges?

Sent from my TA-1012 using Tapatalk

One example could be that you have a couple of SSIDs and you want to keep them on different VLANs. Local forwarding would require the access points to be connected to trunk/tagged switch ports. In many installations the access switches don't know about VLANs at all, so you'd have to reconfigure the entire network.

Another case would be when you want to limit the bandwidth per SSID for example. In local forwarding there is no way to know the aggregated data flow in an SSID. The CAPsMAN would be the central choke point.

I've occasionally set up remote access points. Central forwarding provides an easy solution to get the client packets to the "home" network.

Local forwarding is a good solution in many cases, but doesn't fit all.