Hello.
I change Omada APs to wAP AX devices. Now WiFi in my home works perfectly. But I notice some problems with Traffic Processing option.
When I set it to on-capsman-secure devices connecting very well but there isn’t internet traffic or it’s very slow. When I change setting to on-capsman everything works ok and there isn’t any traffic problems.
Anyone have idea what’s wrong??
Congratulations, wise choice and welcome!
Capsman traffic processing is relatively new feature, only introduced some months ago. I would use traffic-processing=on-cap, this is the fastest by far. Someone did a benchmark and posted it here on the forum and basically it confirms your observations: capsman-secure is very slow, capsman is okayish for low bandwidth applications and on-cap can fully utilize hardware capabilities.
Hmmm.
Well, with secure option internet traffic almost stops.
As router and capsman I use x86 machine with 16GB RAM and Intel Quadcore CPU. So there is a lot of power but in on-cap setting, I don’t have traffic statistics.
Indeed. If you like statistics and/or need to firewall or apply queues to wifi, then on-capsman is your friend.
At its core, CAPsMAN is no more than a configuration server. The only use case I can think of for on-capsman processing is traffic statistics and I think that the on-capsman options are only there to satisfy some itch that because the CAPsMAN is at the heart of it, then traffic should go through it.
I use on-cap processing and if I wanted statistics for the wireless as a whole, I would put the traffic on dedicated vLANs and take the stats from there
Yes, it's me.... can be improved if using an x86 servers i think. But no licenses to test it.
CHR... is free...
Yes, but CHR With free license, is rate limited 
No, the "free" version is just unupgradable... See @normis post...
You can have a 60 day trial without any limitations.
yes and
after this time passes, your license menu will start to show "Limited upgrades", which means that RouterOS can no longer be upgraded.
simply you can not upgrade. but still 100% working...