Just waiting for revision 2, with frequency amplifiers … cAPac is just a much better solution for now - I’m a bit disappointed, can’t behind a wall and no signal or bandwidth/speed! Side by side with cAPac I achieve over 100mb/ps and with cAPax 20-30mb/ps !
Thanks for sharing! I was about to buy a CAP AX for comparison to my CAP AC. Maybe Mikrotik launches an 802.11be access point this year and better skip the AX gear.
Good solution for many wireless clients in one hall, but this 24dbm is not real for me - not a solution for covering a large area with some walls!
Then I’m pretty sure something is way off with your config or the way you test because that’s not what I am seeing.
AX vs AC vs XL AC, the former always comes out first, even if those last 2 have wifi-qcom-ac drivers loaded (which is already a substantial jump over legacy wireless).
I have a single CAPax in a flat with walls out of reinforced concrete and a lot of interference through the windows. I have replaced a TP Link Archer C7 (ac) , which had nice coverage, but CAPax works way better. First I had many issues with it, but since 7.13 the problems began to disappear. 7.14.3 works like a charm with every device I have (no Apple device). I had to do a bit of a research in the forums to find how to configure it properly and I also got some friendly help from some forum dwellers after an upgrade has ruined my config (of course there was no backup).
Unfortunately I don’t have access to it now to paste the config sry.
Yep I get easy 200Mbps on my cap ax which is on my ceiling upstairs 15 meters away, and about 800Mbps in the same room from my hap ax2.
hap ax2 close
status: tcp upload
time-remaining: 23s
ping-min-avg-max: 1.77ms / 2.38ms / 12.9ms
jitter-min-avg-max: 1us / 275us / 10.6ms
loss: 0% (0/200)
tcp-download: 844Mbps local-cpu-load:81%
tcp-upload: 896Mbps local-cpu-load:50% remote-cpu-load:0%
cap ax far
status: udp download
time-remaining: 21s
ping-min-avg-max: 1.93ms / 2.56ms / 3.75ms
jitter-min-avg-max: 0s / 222us / 1.35ms
loss: 0% (0/200)
tcp-download: 230Mbps local-cpu-load:17%
tcp-upload: 290Mbps local-cpu-load:16% remote-cpu-load:0%
2.4G cap 20 wide is faster than what you quote
status: tcp upload
time-remaining: 27s
ping-min-avg-max: 1.62ms / 25.0ms / 125ms
jitter-min-avg-max: 4us / 31.9ms / 118ms
loss: 0.5% (1/200)
tcp-download: 69.7Mbps local-cpu-load:7%
tcp-upload: 91.2Mbps local-cpu-load:7% remote-cpu-load:0%
No.wait Wait… I messed up the 2.4G test as I had my scanner tool running see the silly ping, here it is…
BOOOOOOOOOOOOOOOOOOOOM
status: tcp upload
time-remaining: 24s
ping-min-avg-max: 1.97ms / 3.67ms / 30.4ms
jitter-min-avg-max: 1us / 2.03ms / 27.9ms
loss: 0% (0/200)
tcp-download: 133Mbps local-cpu-load:11%
tcp-upload: 147Mbps local-cpu-load:11% remote-cpu-load:0%
Hang on lets double check…
Network type : Infrastructure
Radio type : 802.11ax
Authentication : WPA2-Personal
Cipher : CCMP
Connection mode : Profile
Band : 2.4 GHz
Channel : 1
Receive rate (Mbps) : 258
Transmit rate (Mbps) : 258
Signal : 78%
Yep 2.4 20 wide
FACTUAL… INFO
I have capsman2 with a dozen of mixed devices - cAPac and cAPax, over 50. The wireless clients are mainly connected to the cAPac model. After one wall only connected to the cAPac! For this, only one type should be used in certain places!
Seems there is a huge missmatch in experience between users.
Can you please show how you did configure the cAP AX, @JohnTRIVOLTA?
This is not config.
Purely on that screenshot alone I see 15 radios using the same 5220 frequency …
You’re really killing that channel there.
Most ac, so I assume those are the cap ACs.
Then a couple of AX also using that 5220 (again: OVERLAP !!) and 1 with 5745, which is a UNII-3 frequency. I hope all your devices are able to use that frequency. Most will not be too happy with it, I am going to guess.
Ever heard of frequency planning ?
You should avoid overlaps, where possible.
You should also avoid using frequencies which can not be used by some of your clients (or accept they can not connect then).
I have with a customer a warehouse setup with 16 radios.
I use alternating 4 5GHz channels with no overlaps. None of the cells use a frequency which is the same as a neighboring cell.
Only lower ranges (5180 - 5240) because the scanner devices being used can only use those frequencies.
Similar with 2.4GHz frequencies.
They are planned in such a way (using 1/6/11 scheme) there is never an adjacent cell using the same frequency as its neighbor.
In addition to holvoetn great respons:
Specifically on the 2.4GHz radio, you want to use frequencies 2412, 2437 and 2462 and a channelwidth of 20MHz.
This will prefent interference as much as possible, but still be present.
Looks like a classic example of “all the gear and no idea”
So many CAPs, wondering how large the area and how many walls?
For all who comment, except the last last one: Аll the caps are on auto frequency selection and are located at a sufficient distance from each other, and those who are nearby in the same hall should choose one that does not overlap! In capsman2 no roaming room, but have FT - enabled for ALL.
The cAPac is much better in terms of coverage and stable signal and traffic vs cAPax. cAPax is better for many clients on one place with direct LOS - better CPU, more RAM! Models just shouldn’t mixed in one place!
I don’t know, but the conditions are the same, ~15m. distance and one wall. cAPac works at both frequencies better, achieving double and triple the data transfer!
Then I can make you a great offer: I’ll trade my cAP ac’s for your cAP AX’s.
Everyone happy!
I will use these units/cAPax/ where a large coverage is not needed, but there are more customers, such as halls behind over 100 guests. For other places I keep buying cAPac!
cap ac 
lol…
Teach me how to do Big Magic oh great one!
interface/wifi/radio/reg-info country=“Bulgaria” 0
ranges:
2402-2482/20
5170-5250/23/indoor
5250-5330/23/indoor/dfs
5490-5730/30/dfs
5735-5875/14
