Yep
, I concur that "it depends", but "it depends" is different from the initial (perceived) "not a Mikrotik issue, go away".
Let's see if we can find on
what exactly "it depends".
Obviously not at the same amplitude level of the (known) Apple issues, but an Asus Vivobook is not a rare device (though likely right now 99% of them are running WIndows and don't have this issue) but it looks like one that will likely be discarded by Windows users and that will fall in the hands of Linux users, not a niche, one-user-only-has-it device, and probably the problem is connected to the wifi card and/or its driver, so it likely extends to all notebooks with that card running Linux.
Replacing the card in a notebook, besides the cost of the new card, can be - depending on the model - a difficult task, if it was a desktop PC I would have suggested to try a new nic first thing, with laptops is not so easy.
@ansky
You should provide a complete configuration export, follow this:
viewtopic.php?t=203686#p1051720
there is still the possibility that the problem lies in some obscure setting in Mikrotik that some experienced user of the forum can spot and that can be changed without compromising your network security and without the sky falling on our heads (tomorrow).
I don't think that a different distro, likely using the same rtw88_8821ce driver, would behave differently, no idea if any other Linux (or - say - BSD) coming in a .iso bootable/volatile form BUT using a different kernel driver actually exists.
Very likely it won't make any difference, but for what it costs trying booting a non-debian derived .iso is something to try.
To recap, possible causes may be:
1) some "default" or "user modified" settings on the Mikrotik side <- if you provide your configuration we can check if anything is blatantly "wrong" in it.
2) some "default" or "user modified" settings on the Linux side <- you should know if you have changed anything and/or you can try resetting to default
3) some "peculiar" setting/behaviour of the driver <- in which case maybe there are other documented cases on Linux dedicated boards/mailing lists/whatever
4) some "peculiar" behaviour of the Asus Vivobook hardware with that driver
If #1 then Windows (or its driver) has a way to workaround it by default
If #2 then all distros will have the same settings and will fail in the same way (so it would be more likely to find similar documented cases)
If #3 it would still seem to me improbable that noone else has already experienced the same issue, Mikrotik devices may be not the most common around, but they are not niche, and as well that Realtek card is not a home made single specimen, but if you are running an older driver I would try latest first thing
#4 seems like the most probable (and also the most difficult to pinpoint/troubleshoot, unfortunately)
P.S.: Check this:
https://forums.linuxmint.com/viewtopic.php?t=394684