Has anyone already tested cAP ac with RouterOS v7.4rc and did wireless single/multiclient benchmarks both with 2.4 and 5.0 GHz radio and compared the results to the results with OpenWrt v22.03rc5 (https://firmware-selector.openwrt.org/?version=22.03.0-rc5&target=ipq40xx%2Fmikrotik&id=mikrotik_cap-ac)?
Do it yourself.
You can find a bit of perf info here: https://www.reddit.com/r/mikrotik/comments/uy3nhg/poor_wifi_performance_on_cap_ac/
And from the looks of it, folks won’t need to use custom builds anymore. Specific pull requests have been reviewed and will be merged into master branch.
https://github.com/openwrt/openwrt/pull/10135
Is there anything in particular you are looking for?
Yes, i have installed openwrt 22.03 rc5 on 2 cap ac’s for about 2 weeks at work. With irqbalance active and cpu governor set to performance the throughput on speedtest.net is about 390 Mbits dw/up with 80 mhz channels and about 220-230 Mbits dw/up with 40 Mhz ch. On iperf it shoulf be a bit more but i didn’t test it yet.
The stability looks good: no complaints until now. The auth is wpa2-eap and it works without problems. The wifi package wich come by default is wpad-basic-wolfssl and does not contain wpa2-eap but i uninstalled it and installed wpad2-wolfssl.
I had 1 user wich connects to a different access point from time to time, and his experience was bad. I noticed he is now allways connected to the close cap ac (wich runs openwrt).
I don’t use 802.11rkv yet as i have a lot more cap ac’s with routeros installed and when i activate this feature, the ap it’s like a “magnet” for all clients on 3 floors who see the signal.
The only feature that i miss is capsman who allows me to see all the connected clients.
Thank you for your report.
The only feature that i miss is capsman who allows me to see all the connected clients.
DUDE sees all connected clients also for stand-alone (non CAPsMAN) MT RouterOS AP, with more details (uptime, MAC address, wlan interface, Signal strength, Signal CCQ, interface rates, RX/TX counters, Last IP , Last seen since , Comment field, etc etc etc, just as the local Registration table.
the ap it’s like a “magnet” for all clients on 3 floors who see the signal.
Analyze the beacons and you might find why this is. (e.g. BSS load info missing…
And as you look at beacons anyway, see A-MPDU and A-MSDU size what explains performance difference. http://forum.mikrotik.com/t/ac2-vs-ac3-wifi-not-over-200mb/148289/1
(Beacons on wifiwave2 to be analyzed, when hAP ac3 arrives one day)
MT is strict and correct in following the EIRP max power as per regulated region. Other brands easily go 10dBm higher, and in the illegal range. (Or are set as such by SW config.)