New WAP ax owner and Mikrotik newby here, switching over from a legacy Cisco solution. Been setting up the wAP from a blank configuration as an AP. Device is direct to 1GB router (speed verified). Speeds limited to about 60Mbps consistently regardless of testing device. Updated RouterOS and Routerboard. No congestion at all on selected frequencies. Device is sitting on wall in line-of-sight about 10m away. Below is my config. Any suggestions on how to tweak is appreciated.
No need to explicitly set width. While the width for 2.4ghz was okay (20/40), the width for 5ghz (20/40/80) was limiting factor. wap ax supports 160mhz channel width.
What does the radio registration show for the devices' signal levels and connection rates? Are they what they should be? Also, I have not used 7.22.3 on my APs. I tend to stick with the long term branch, it's possible there is something new going on in 7.22.3 with wifi, IDK.
80MHz isn't that limiting. I have installations that use 80MHz so we can run more channels and they easily push 500-600Mbps with 2 stream APs.
60Mbps or so is what you typically see with 20Mhz 2.4GHz 802.11n APs from years ago. There is definitely something sketchy going with that speed unless perhaps he is only testing with 2.4GHz devices.
There really doesn't seem to be anything wrong with how you've set up the device, and 60 Mbps is really low, even on 2.4GHz. Additionally, the wAP ax is a relatively mature and problem free device...
I'd look into this:
Are you sure? Did you verify that the device actually links up at 1GbE, or only that it could? A 100M link would go a long way towards explaining your issues.
Additionally, I would try disabling wpa3 temporarily. Some client devices don't play nice with it (but if you have tested multiple, what are the odds...)
60mbit/s is what I get roughly on a 2.4ghz 20mhz link on a average signal level. I would not set the frequency to a fixed value either. Otherwise the config looks good. Minimal and no bloat.
Chiming in here - I did that exact stupid thing recently on a link capable of 2.5Gbps from the core to the AP, but I had pulled an old PoE injector out of the drawer that only does 100Mbps... I didn't check the link speed, just that it was up and running
AX select = ax-only on 20 and Ce/eC (no b, no g and no n)
N select = n-only on 20 and Ce/eC (no b, no g and no ax)
G select = g-only on only 20 (no b, no n and no ax)
"empty" select =
g / n / ax on 20
and n / ax Ce/eC (g do not support extended channel)
and NO "b"
The same also applies to the 5GHz interfaces, with the same logical operation.
AX select = ax-only on 20 and Ce/eC and 1C+3e combo (no a, no n, no ac)
AC select = ac-only on 20 and Ce/eC and 1C+3e combo (no a, no n, no ax)
A/N select (bug on name?) = n-only on 20 and Ce/eC (no a, no ac, no ax)
A select = a-only on 20 (no n, no ac, no ax)
"empty" select =
a / n / ac / ax on 20
and n / ac / ax Ce/eC (a do not support extended channel)
and ac / ax 1C+3e combo (a and n do not support triple extended channel)
I once noticed that I had the computer that I use for development suspiciously limited to 100 Mbps speeds. It turned out to be a rj-45 patch adapter (a small box that connects two patch cables into a longer one, quite common around here, but usually very cheap quality) that had two pins shorted.
What really surprised me was, however, that it had been like this for 3 months without me noticing...
I'm not at a sufficient level to argue with you on wifi stuff, but I have devices in front of me that are not capable of ax, connected to a Mikrotik ap that's explicitly set to "(band) AX". If what you're saying is true, is that not a bug, either in what is displayed or the actual behavior?
I recall someone from Mikrotik saying that "ax" means "ax and below" on this forum. There are even ongoing threads to have an option to disable b/g...
I just removed the ax band from my CAPsMAN profiles and re-provisioned the cAPs, and yep, there are the n, g and ac priorities on the status tab which weren't there before.
I had some flakiness with older devices and wonder now if this was part of it.
I don't believe the output of that channel priorities panel..... Until someone confirms by e.g. setting channel=2ghz-ax and not seeing nor able to connect using a device which is definitely not 802.11ax compatible.
To be clear, I unset the band in /interface wifi channel and then re-provisioned the cAPs. After doing so the cAP wifi interfaces shown in the interface list on the CAPsMAN have more channel priorities on their status tabs.
Good point.
It was a red herring. I returned my config to what it was previously (ax band specified in /interface wifi channel. The lower modes aren't disabled at all, based on what I see in WIFi Registration. Clients are connecting with bands N and AC even though only AX channels are shown in Interface, Wifi, Status, Channel Priorities.
Example cAP radio showing only AX channel priorities:
