I am running RB4011/Wifi since about three months, as a result of a series of unfortunate events.*
It seemed quite attractive as an all-in-one home+homelab device.
I can confirm the "5GHz wifi dying after some days/weeks of uptime" issue exists.
But recently - after moving from 6.44.3 to 6.44.5 (which didn't fix it immediately) /and/ statically allocating frequencies - it seems fully stable for me now.
While playing with the secondary frequency setup I've managed to repeatedly crash(?) the wireless subsystem in a way that froze management layer, too (forum post)
, so there /are/ some gremlins in there.
But once i was done with the experiments and left it set up, wireless runs solid. Knock on wood.
Mikrotik isn't the best at the "plug it in, it just works" experience, and obviously there are some issues that need to be acknowledged - from hardware/driver incompatibilities with MT's kernel, as seen with the 5GHz wifi or with the SFP ports, to some features lagging behind the times due to home-brew implementations and inability to just drop-in the new upstream code.
There are upsides and downsides, like everywhere.
But from a "tinkerer/homelabber" perspective, I'm happy with the product. And I've seen bigger blunders and worse bugs on some of the uber-expensive Cisco gear I run in professional setting. **
It's not perfect, no. The choice of more basic RTL switch chips was quite surprising, for example. I agree it would be nice for the successor to have a more featureful switch which can be used with full hardware-vlan functionality in ROS. (which means, IIRC, the hardware must support two layers of vlans, because first layer is used internally for ROS to present the ports as independent on the CPU.)
But all in all, RB4011 is fun to play with, has a lot of features and horsepower for the price, and was a massive upgrade from my old home router. ***
Unless MT's going to jump the shark and pull some absolutely insanely stupid moves in the close future, I'm definitely going to be coming back for more hardware when time to expand comes.
* A nearby lightning strike killed the Realtek switch chip in my old OpenWRT home router, leaving the CPU and wireless functional, but with zero wired capability.
This happened just weeks after I decided to buy an EdgeRouter and retire the OpenWRT one to role of an AP.
I didn't want to fully move into the Unifi ecosystem with separate APs, having to build or buy a controller, and so on, while the independent airCube is also quite an unfinished product and focused on being controlled by a WISP.
I was also kind of frustrated with configuring EdgeOS as it's running majority off the shelf OSS components like quagga and dnsmasq but not allowing the full gamut of configuration settings to be set up via the Edge configuration/management layer.
The Unifi switches and "gateways" being Edge product equivalents with the configuration CLI removed and even narrower feature set "pushable" from the controller is also kind of frustrating.
Mikrotik on the other hand's is using mostly-custommade userland, with (near?) all the services like DHCP or routing being inhouse.
Many will consider this a bad thing - with good arguments such as long delays to implement some newer stuff like TCP OpenVPN or some newer IPv6 extensions - at least "we get access to all it can do", which kinda feels better to me.
** (Anyone remembers early IOS-XE 3.3 on Catalyst 3650/3850 series? These still suck on current code but nothing like in their early days.
Recent drama with 2960X switches having TPM fail, with the switch deeming itself a counterfeit and irreversibly erasing license files, reducing itself to nearly-unmanaged L2 mode.
AireOS 8.0 ported to the WLC-5520 platform based on Xeon rackmount server, lacking drivers for the CIMC and running fans at the max speed so you heard it outside of the server room.
All early AireOS 8.x until like 8.4 having massive wifi stability issues on old 11g clients, which's bizarre considering big business industrial settings with legacy hardware are one of top customers of Cisco wireless in the first place.
And that's just a tip of the iceberg floating in my whiskey glass...)
*** (That one's humble single core MIPS was choking itself to the point of making SSH connection take about two minutes to reach prompt when another PC in the apartment was running Steam game download on full rush.
Yes, I tried setting up QoS on it - it only made CPU melt down faster. On the RB4011, the Alpine barely sweats at 7-10% with a basic eight node queue-tree setup ensuring fair allocation and comfortable browsing speeds for everyone even with heavy downloads running. )