same situation here, with hap ax2 - random disconnects of one client

hAP ax2 here too but I work wired most of the time so I don't tend to be stressing the Wi-Fi. My set-up is a private and a guest network, also used by my neighbour. In order to do some testing/diagnostics on my hAP ax2, I put the guest network on a spare hAP ac lite. It's been like that for several months.

I've just realised that I've not had to tell my Amazon Echo is restart the radio for months either... my hAP ax2 and ac lite are right next to each other. So Amazon Echo connected over 5G to hAP ac lite, completely solid. Looking at reservations, some devices have been connected for several days.

Mikrotik and Qualcomm are already working on a solution as far as I was told by Mikrotik support. We will see a fix - I am confident. Big thanks to everyone who created a support ticket to help tracking down the issue.

Just to understand... those who have disconnects have CAPsMAN configured?
My hAP ax3 is very stable...

I don't have CAPsMAN configured on my ax3, but there is a disconnection problem, a support thread has been created and the problem has been confirmed. We are waiting for a fix.

Please please please,
stop complaining on this forum and create support tickets as intended.
As long as there are not enough examples of problems, they can not fix anything.
And, as there are far more users without problems (like me, no disconnects at all !)
the users with problemd are a minority ... And without signaling to support@mikrotik.com nothing happens

the existence of the problem is acknowledged by Mikrotik support, so your statement that it is experienced by a minority is wrong. Most likely, not everyone experiences it for different reasons, and some simply do not notice it, I think that this is how it should be.

Mikrotik and Qualcomm are already working on a solution as far as I was told by Mikrotik support. We will see a fix - I am confident. Big thanks to everyone who created a support ticket to help tracking down the issue.

+1
I have already posted a response from Mikrotik support, we continue to wait for a solution... it's sad that it takes so much time and there is no tracking or timeframe for a solution...

I see exactly the same behavior on AX2, normal operation on 7.14.3 and very poor operation on a later firmware

which is discouraging, because I also have AX lite and there Wi-Fi 2.4 works perfectly on any firmware, now on 7.18.2

that's why I see that on AX2 and AX3 there is QCA6018 and on AX lite there is QCA5018, did this mean that the problem is confirmed only for devices with QCA6018? and such as AX lite, L009 work well?

I see exactly the same behavior on AX2, normal operation on 7.14.3 and very poor operation on a later firmware

which is discouraging, because I also have AX lite and there Wi-Fi 2.4 works perfectly on any firmware, now on 7.18.2

that's why I see that on AX2 and AX3 there is QCA6018 and on AX lite there is QCA5018, did this mean that the problem is confirmed only for devices with QCA6018? and such as AX lite, L009 work well?

Ive heard of people saying that wap ax with a 5018 and 6102 mix work well.

7.20beta2 is even worse than 7.18.2!

Any news?

Yes. viewtopic.php?p=1146058#p1146044

Yes. viewtopic.php?p=1146058#p1146044

Ah, so the fix is for Chromecast devices. That would explain why my Google Nest Hub is causing the issues - it’s a Chromecast device.

Wow!!!
Got a message from the support team that they fixed the issue and it will be included in the next update:

This is an automated message. Our bug tracker reports that your issue has been fixed. This means that we plan to release a RouterOS update with this fix. Make sure to upgrade to the next release when it comes out. To be sure this specific fix is included, read the changelog when the next version comes out. If your issue is not mentioned, it might mean it will be in the next release.

We are waiting for a new release ROS.

Wow!!!
Got a message from the support team that they fixed the issue and it will be included in the next update:

This is an automated message. Our bug tracker reports that your issue has been fixed. This means that we plan to release a RouterOS update with this fix. Make sure to upgrade to the next release when it comes out. To be sure this specific fix is included, read the changelog when the next version comes out. If your issue is not mentioned, it might mean it will be in the next release.

We are waiting for a new release ROS.

Whaaaaaat?? OK, really keeping my eye out for the next release now

Hello all!

Got the following reply on my ticket:

This is an automated message. Our bug tracker reports that your issue has been fixed. This means that we plan to release a RouterOS update with this fix. Make sure to upgrade to the next release when it comes out. To be sure this specific fix is included, read the changelog when the next version comes out. If your issue is not mentioned, it might mean it will be in the next release.

If you would like any more details - please reply to this message and one of our support engineers will contact you.

Seems like they have been working on it. I've asked them for a pre-release fix if possible, if i receive it, i will be sharing news.

My sad story about AX and Mikroitk. I am not sure that CAP AX have same problems - but looks like it has same chip. More than 1 year ago one of my clients asked me to fix wifi in his home. He had only cheap router from ISP. I told him - sure man, you will have best wifi in whole world. Mikrotik just released super cool new AP - CAP AX. I took three of them and spent 3 days trying to make this setup working with Capsman - no luck. Random disconnets, prob;em with connects. If you connected to one AP all ok, but when you try to roam and connect to another AP- you stuck. You have to tap stupid wifi icon 100 times in row in order to reconnect. Than was my first and last experience with Mirotik AX and i am pretty sure i won't be using it any more for building wifi networks with 2 and more AP. Only simple setups for small offices and apartments with one device. I have returned these cool AX access points to the reseller and took TP-Link. Since then i install TP-Link and Unifi. Now i have only one CAP AX - at my home and second in the box. With about 200+ ROS devices in total under my administration. Sorry - my client can't wait 1y+ in order to get good wifi. And boys - i am not sure that this will be fixed in next stable release and there won't be more annoying bugs. I have just found this topic, red it and flashbacks from my experience forced me to post about it.

So, i got the pre-release firmware (7.21_ab85 for ARM64)

I've had it for an hour now and it is looking good. I know one hour is probably too early to say but i will continue to monitor it for the following days and let you know.

I will report back to you all on how it goes.

Hello, it sounds good. Did you just need to update the access points, or both capsman and the access points? And can you share the beta firmware?

Like I posted in the other topic, it looks like 7.20 and 7.19.2 will fix majority of AX related wireless issues that people had

Like I posted in the other topic, it looks like 7.20 and 7.19.2 will fix majority of AX related wireless issues that people had

Great news @normis!

Hope to see the beta soon ...

Like I posted in the other topic, it looks like 7.20 and 7.19.2 will fix majority of AX related wireless issues that people had

Happy days

Hello, it sounds good. Did you just need to update the access points, or both capsman and the access points? And can you share the beta firmware?

I've installed it only on the APs but keep in mind that i don't do much on those APs, only basic VLAN tagging and CAP. My CAPSMAN and main router/firewall/everything is a HEX Refresh running on the latest production release and i wouldn't put it there.

As for functionality, i see no disconnects and i've been running it since this morning. That behavior would definitely not be possible with the buggy driver.

Mikrotik initially asked me not to share the firmware but in the meantime they've made the nightly firmware public. Here's the link where you can download it from. Just be careful what you run in on. It is a nightly build and it will likely break other stuff.

Link where you can download it from (ver 7.21_ab85 is the one i have installed, looks what they made public is a newer version)
https://mt.lv/nightly-build

Thread where normis made it public:
viewtopic.php?t=198736&start=300#p1146916

Guys,
in order to avoid all the fuzz which was there with the RB5009-bootloader-mishap ...

Let's make this clear:

THIS IS A NIGHTLY BUILD.
AS INDICATED IN THAT OTHER THREAD: PROCEED AT YOUR OWN RISK AND DO NOT COME COMPLAINING IF THINGS BREAK.

Ok ?

Like I posted in the other topic, it looks like 7.20 and 7.19.2 will fix majority of AX related wireless issues that people had

Great news!!!

So, i got the pre-release firmware (7.21_ab85 for ARM64)

I've had it for an hour now and it is looking good. I know one hour is probably too early to say but i will continue to monitor it for the following days and let you know.

I will report back to you all on how it goes.

I've had this build running for 3 days without noticeable WIFI related issues.
That being said. Something else might be broken, but nothing impacting the features I use.

Still works after 24+ hours. Then again, i'm only testing VLAN Tagging and wifi functionality. Something else is likely broken.

What's important is that it looks like Mikrotik finally fixed the issue and we will receive a production ready fix in the coming months.

I can confirm that the issue has been fixed after upgrade to 7.21 !!! At last!

No more disconnections on the 5 GHz wifi on my router hap ax2.

Looks like wi-fi issue was resolved at 7.21 My HP laptop no longer disconnetcs under load.