cAP ax TX errors on WiFi interfaces

RouterOS Wireless Networking
1

I was wondering if this is normal on ax devices, I seem to have lots of TX errors both on 2G and 5G radios:
2024-05-29 210304.jpg
Wifi seems stable. I have never seen this on my previous N/AC APs, there were always 0 errors even after months uptime.
The cAP is managed by CAPsMAN, but the same was happening even in bare AP mode. Not caused by a single client, it happens vith various client devices, some seem to generate more errors than others though. Latest stable ROS v7.14.3.

Is this something known and is this happening on every ax device? Or is it some misconfiguration? Or even possibility of faulty HW?

2

8940 of 1008150 = 0,89%

I would not worry about.

3

Thank you for the reply. So does it mean that this is sort of normal on ax devices?
I was more curious if other owners of ax APs could chime in, if they get the same erorrs then if would seem to be a “feature”, but if others do not see any errors then something must be wrong with mine.

4

Got another cAP ax and that one too has some number of tx/rx errors on all wireless interfaces over time.

So in case anyone will search for this in the future, this seems to be a feature, not a bug.
I am just surprised no one has mentioned this before.

5

Because it is no hardware error and not everyone notices these stats.

There could be many causes for these TX errors. Usually not a hardware defect. Most commonly e.g. neighbors wifi overlapping with your wifi channel.
For 2.4ghz wifi many times bluetooth from any other nearby device or interference from household devices like microwave oven, cordless phones can be a massive problem.
What I am not 100% sure if it applies, but I could imagine that even a unstable/low signal connection to a connected client device (e.g. far away, bad signal, etc.) could make this counter rise as well.

And it is a feature. It helps you debugging your wireless environment. But as I already said: 0,89% TX errors is negligible. I can see a similar RX error rate on my Linux notebook wifi statistics as well - without experiencing any issue at all.

After all it is a wireless medium. If you want zero interference and 100% reliable connection, you need to use cables.

6 
cAP ax
Flags: D - dynamic; X - disabled; I - inactive, R - running; S - slave; P - passthrough 
 #       N           RX-BYTE           TX-BYTE         RX-PACKET    TX-PACKET      RX-ERROR TX-ERROR
 0   RS  ;;; managed by CAPsMAN
         ;;; mode: AP, SSID: , channel: 5500/ax/Ceee
         w      1 271 163 074     11 946 300 900     4 112 317     10 870 907          901      689
 1   RS  ;;; managed by CAPsMAN
         ;;; mode: AP, SSID: , channel: 2412/ax
         w        22 721 307          89 172 682        52 547        103 646          413      253

hAP ax^2
Flags: D - dynamic; X - disabled; I - inactive, R - running; S - slave; P - passthrough 
 #       NAME        RX-BYTE           TX-BYTE         RX-PACKET     TX-PACKET     RX-ERROR TX-ERROR
 0   RS  wifi1   14 195 851 678     59 269 940 563     14 321 153    44 063 457        640  110 546
 1   RS  wifi2       76 883 508      1 209 620 526        412 185     1 604 886      2 057      703
7

Thanks, it is not that, I just wanted to know if it is normal or if I should be looking for a cause, that is all. And as I wrote, I was used to ac wireless giving me 0 errors even after a few months uptime in the same location with the same devices, so that is why I was suprised to see this on ax. The reason can also be the qualcomm drivers on the ax vs. the legacy on the ac, so it is highly probable that the errors were also on the ac, just not reported by the driver.