After all, the problem has been known for more than a year and Mikrotik does nothing about it.
v7.14.3 was introduced April the 17th, 2024. After this release, a new(er) driver of Qualcom was introduced that caused problems for some users. Have been there, did a lot of tweaking and have zero problems currently using v7.18beta2 (and the same since all 7.16.x versions there were made available).
In the past, in hotels, guesthouses and other public premises, the majority of WiFi network was implemented by Mikrotik, but now I see Omada equipment being installed in its place. No one professionally dealing with networks will push for the problems that Mikrotik guarantees.
Can you please provide numbers?
To be honest, a new user with only 2 posts saying it has lost faith…either provide some constructive feedback or request for help. But stop complaining and talking about other brand(s).
v7.14.3 was introduced April the 17th, 2024. After this release, a new(er) driver of Qualcom was introduced that caused problems for some users. Have been there, did a lot of tweaking and have zero problems currently using v7.18beta2 (and the same since all 7.16.x versions there were made available).
Good for you. There are plenty of people here for whom the only fix that works is a rollback to 17.4.3. Someone posted above that they can reproduce the issue with a fresh / default config and just two devices. The “I just switched off WPA3 / set connect priority / … and it works for me, don’t know what y’all talking about!” crowd is just distracting from the real issue.
It would be beneficial to all to report these issues to Mikrotik support - instead on whining here. This is a community topic. Of course there will be comments like “I dont have this issue” just because this is not a Mikrotik support thread. It is a open discussion.
For context:
Two VLAN’s, ID 50 for home and ID 51 for Guest.
PPSK to have a single SSID, WPA2-PSK as that is only supported for PPSK: https://help.mikrotik.com/docs/spaces/ROS/pages/224559120/WiFi#WiFi-Securitymulti-passphraseproperties
For fast roaming ft=yes and ft-over-ds=yes (for devices that support FT) and connect-priority=0/1 for those who don’t.
Devices are (all the usual) brands like Samsung, Apple, Noika, HP, Microsoft, Dell, etc.
There are three wAP AX CAP’s (but also working just fine for cAP AX).
7.18beta also has no improvement for you? then your issue might be caused by something completely different.
from this topic we have seen many people who join in on the “me too”, but the issue was related to something else.
please make a full report of the issue with RIF file from 7.18beta, logs from client device, etc. and email to support@mikrotik.com
I tested again wap ax as STA on latest beta, still get deauth frames (beta on all MT devices). As I get random reason codes, I’m trying to collect them all (for fun).
Test was exactly the same as mentioned is SUP-174626 ticket, connection session was active about 6 days.
No improvement with the latest beta (7.18beta6). https://imgur.com/a/iFbIkgI
All WIFI devices break simultaneously. SIGH
And yes, I have been through the hoops with support with rif’s.
This is the what is logged related to wireless https://imgur.com/a/SK5qpJL
*EDIT: None of the devices listed in the logs are the Google Cast devices that “falls off the network”. And they keep their DHCP lease time. Meaning they are not disconnecting from WIFI, but the connectivity is still dropped (packet loss).
The error happen less if certain devices (Google Cast enabled) are “dormant”. I.e. not streaming content to them.
If I remove the devices (Google Cast enabled) from my wireless network, then there are no issues.
All of this information with tons of details has been provided to MK support and the ticket is still active. Though it’s been quiet from MK support for the last 3+ weeks.