Hello

When i change my CAP from local forwarding to capsman forwarding why there different performance?
When using local forwarding the throughput can more than 150Mbps but drop to around 80Mbps when switch to capsman forwarding,

Because everything has to go to the controller before it goes anywhere else. So you saturate your links. And you over run the processors.

So what the goal mikrotik have capsman feature if with this configuration the performance degraded?
Or there are trick how to improve the performance?

So what the goal mikrotik have capsman feature if with this configuration the performance degraded?

This feature was just fine with 802.11g (max 54Mbps code rate, 30Mbps actual data throughput) cAPs.

A nice feature: CAPsMAN connection can be routed over MAN/WAN links and capsman forwarding in this case makes cAP part of the remote LAN. Without capsman forwarding this obviously can't be done as easily.

But time progressed since and things are different now. So no need to fuss about an ancient feature not performing up to modern standards. (and I suspect capsman tunnel to have encryption not strong enough for today's standards either)

ROS has been around quite a long time. And Mikrotik does not like deprecating/removing functionality. And Mikrotik themselves see their market in cheap low-end devices as well, so this low-performing 80mbit is still something they may see a use-case for. somewhere in the rural area where 10mbit uplink is still your bottleneck

Hello

When i change my CAP from local forwarding to capsman forwarding why there different performance?
When using local forwarding the throughput can more than 150Mbps but drop to around 80Mbps when switch to capsman forwarding,

It's obsolete function, so question is, why do you want to use it?