I recently replaced 2 x cAP ac with cAP ax. The system contains additional 2 x cAP ac and is controlled via capsman (already switched to new version before the change to get FT support).
Now I have a problem that old WiFi clients that support only 2,4 G or 5GHz A/N protocols either can’t see or can’t connect to the cAP ax’s (they connect normally to the remaining cAP ac’s). New WiFi clients that support ax protocol work OK. When I go to Interface - Status under channel priorities i can see all ax, n, g channels listed but the auto fallback to older protocols doesn’t seem to work! Am I missing something?
As a quick fix, under WiFi Configuration → Channel → Band for 2,4GHz I have selected “2GHz N”. That has forces N only mode (there seem to be no auto fallback to G protocol?) so now my old clients work but I get only WiFi-4 working (on my old cAP ac’s without forcing the N protocol I got WiFi-5 before) and clients now very rarely use 5GHz band.
Is ax protocol fallback on Mikrotik broken or is it normal that ax doesn’t work with old g/a devices?
I have also noticed that using default (Croatia) settings 2,4GHz signal reach in cAP ax is much shorter that in cAP ac. TX power is lower on ax, but it should have higher gain antennas, so I am surprised that the signal reach is lower. Are others having a similar experience? Can this be fixed/mitigated?