mikrotik lcd panel free sample

Probably the selected serial port is used by PPP client or server, or by the serial console. Check the availability and use of the ports by examining the output of the /port print command. Alternatively, select another port for connecting the LCD, or free up the desired port by disabling the related resource

The current MT LCD module scrolls and displays the configured info every X (user settable) seconds. This is nice except when you need to watch something. For example, say you just want to watch traffic on Ethernet 1. It is frustrating to watch it for the 10 seconds and then have to wait for it to get through everyting else. This is where the buttons come in.

60-day free trial license is available for all paid license levels. To get the free trial license, you have to have an account onMikroTik.comas all license management is done there.

You will have to have an account registered on MikroTik.com. Then you can request the desired license level for trial from your router that will assign your router ID to your account and enable a purchase of the license from your account. All the paid license equivalents are available for trial. A trial period is 60 days from the day of acquisition, after this time passes, your license menu will start to show "Limited upgrades", which means that RouterOS can no longer be upgraded.

Note that if you plan to purchase the selected license, you must do it before 60 days trial ends. If your trial has ended, and there are no purchases within 2 months, the device will no longer appear in your MikroTik account. You will have to make a new CHR installation to make a purchase within the required time frame.

To request a trial license, you must run the command "/system license renew" from the CHR device command line. You will be asked for the username and password of your mikrotik.com account.

It is a special key which is issued by the MikroTik support team if you accidentally lose the license on a x86 instance running RouterOS, and the Mikrotik Support employee decides that it is not directly your fault. It costs 10$ and has the same features as the key that you lost.

Note that before issuing such key, Mikrotik Support can ask you to prove that the old drive has failed, in some cases, this means sending us the dead drive.

1)Go to your account management in mikrotik.com and fill the "support contact form" or write a direct e-mail to support@mikrotik.comPlease provide detailed information about why replacement key is required

If for some reason you have lost license from your router, upgrade router to the latest RouterOS version available and use "Request license key" in your mikrotik.com account. Use soft-id and serial number available under System/License menu in RouterOS when requesting license. Apply received license or contact support@mikrotik.com if request feature do not work.

Formatting, and Re-Imaging the drive with non-MikroTik tools (like DD and Fdisk) will destroy your license! Be very careful and contact mikrotik support before doing this. It is not recommended, as MikroTik support might deny your request for a replacement license. For this use MikroTik provided tools Netinstall or CD-install that are freely available from our download page.

MikroTik hardware comes with an embedded license. You cannot move this license to a new system in any way, this includes any upgrades applied to the MikroTik router while it was still working.

The keys that you purchase from other vendors and resellers are not in your account. Your mikrotik.com account only contains licenses purchased from MikroTik directly. However, you can use the "Request key" link in your account, to get the key into your account for reference, or for some upgrades (if available).

The licenses are stand alone keys and MikroTik does not have any remote control over your devices. Therfore, we are unable to verify if you use your license or not. This is why MikroTik cannot terminate any issued licenses.

Netinstall is a tool for installing and reinstalling MikroTik devices running RouterOS. Always try using Netinstall if you suspect that your device is not working properly. The tool is available for Windows (with a graphical interface) and for Linux (as a command line tool).

There are multiple ways how to put your device into Etherboot mode. Make sure you read theEtherbootmanual before trying to put the device into this mode. Methods vary between different MikroTik devices.Wait for the device to show up in Netinstall, select it and pressBrowse.Navigate to yourDownloadsfolder (or wherever you saved your RouterOS packages) and pressOK

Etherboot mode is a special state for a MikroTik device that allows you to reinstall your device usingNetinstall. There are several ways to put your device into Etherboot mode depending on the device you are using.

TheResetcan be found on all MikroTik devices, this button can be used to put the device into Etherboot mode.An easy way to put a device into Etherboot mode using theResetbutton is by powering off the device, hold theResetbutton, power on the device while holding theResetbutton and keep holding it until the device shows up in yourNetinstalllwindow.

Some devices come with a serial console that can be used to put the device into Etherboot mode. To do so, make sure you configure your computer"s serial console. The required parameters for all MikroTik devices (except for RouterBOARD 230 series) are as following:

A container is MikroTik"s implementation of Linux containers, allowing users to run containerized environments within RouterOS. The container feature was added in RouterOS v7.4beta4.

Before the LCD touchscreen can be used, it needs to be calibrated at least once. After the first successful calibration, data is stored on the router. If no calibration values are present, calibration process will start automatically.

Take-screenshot function allows to create BMP image of currently displayed LCD screen and saves it in File List with specified name. Screenshots without file name are not saved, screenshots with an existing file name are overwritten.

Interfaces menu provide configuration for interface display timing in Stat Slideshow. Up to 10 additional (non-physical) interfaces can be added to the LCD.

A Page is an screen that can contain up to 12 interface bar graphs. Sub-menu allows to configure which interfaces are shown in a page. Up to 5 pages can be added to all interface graph screen and up to 12 interfaces per page. To add an interface to a page, it first must be added under /lcd interfaces sub-menu.

PIN code number allows to protect sensitive menus on the LCD screen. The PIN number will be asked if Read-Only mode is disabled and you add an IP address, reset or reboot the router. Default PIN is 1234

Since v6.0, LCD has a menu structure. Menu screens consist of buttons that are used to navigate the menus. A scrollbar is shown on the right side of the screen if it does not fit on the actual display. The screen can be dragged up or down to access more options if they are available. At the top of each menu screen is a "Back" button that jumps to the previous screen.

If the router has default configuration - user named "admin" with no password, then a warning on LCD will appear. This screen shows IP"s assigned to the interfaces which could be used to connect to the router.

Stat Slideshow screen is similar to the "Stats" screen, but the interfaces are switched after they timeout. Settings for slideshow are stored in RouterOS submenu /lcd interface

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while the router is not working as suspected or after some problem has appeared on the device

Why does it take so long to run SFP+ Mikrotik transceiver on RB4011iGS+5HacQ2HnD? It started to behave this way a few 7 releases back and since that moment I always have to wait much longer for communication with my LAN.

Sorry, but I can´t agree. My RB4011iGS+5HacQ2HnD is connected via SFP+ with my CRS326-24S+2Q+ with an MikroTik DAC-Cable and regardless if I soft- or hardreboot my device the SFP+ connection came up without any issues.

Sorry, but I can´t agree. My RB4011iGS+5HacQ2HnD is connected via SFP+ with my CRS326-24S+2Q+ with an MikroTik DAC-Cable and regardless if I soft- or hardreboot my device the SFP+ connection came up without any issues.

Good point, maybe its the SFP+ module brand I"m using as they are not a Mikrotik brand and probably don"t get tested at Mikrotik. The SFP+ I"m using at both ends the Maxxwave MW-SX+MM-US. But it worked perfect all these years till the moment of the latest 7.5 [stable] update, so it only makes sense its a bug since 7.5beta11 worked perfectly.

I would not recommend mixing the use of OpenVPN with MikroTik OVPN. It is not the same thing. And it is not tracking the releases of the real thing.

I made a ticket with Mikrotik support last week when we ran into a problem on SW02 in the MLAG stack where port 1-12 stopped working for some users. I was recommended to upgrade to 7.5. I did this this weekend and today I got the from the customer that network was slow. I tried to pinpoint the problem. Made 2-3 speedtest from servers and had full speed. But traffic internal like SQL, SMB and RDP where very slow. At some time my winbox timed out towards both switches. When I connected to the switches with mgmt on bridge it was also slow and hard to download and upload files.

Since from mikrotik manual help page mention about its better to have different storage for the container, hAP-AC3 i think better with its USB port (will use USB to Sata3 SSD).

If we need to start doing netinstalls before sending them out in the field... I wanna see a big f--king warning on the top of EVERYTHING from the Mikrotik domain.

If we need to start doing netinstalls before sending them out in the field... I wanna see a big f--king warning on the top of EVERYTHING from the Mikrotik domain.@gotsprings ....

I"m still hoping that someone at MikroTik has a list of features of v6 that are no longer working in v7, and assigns some priority to fixing those or putting up a list of features in the documentation that "are gone and will not come back".

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while the router is not working as suspected or after some problem has appeared on the device

qsfp 4 x breakout cables still don"t work - ccr2116 qsfp to original mikrotik breakout cable "Q+BC0003-S+" still has no link. last known working version was ros 7.2.3. all other versions after 7.2.3 just don"t have a stable link anymore.

Offtopic: Good to see your powers clipped. Simping for mikrotik and telling that all bugs or missing features are user"s fault doesn"t help in the long run. One of the worst moderator on a technical forum.

"Simple" TCP might not be so simple ... I guess the tricky part of netinstall binary is that it includes BOOTP/DHCP server and TFTP server, additionally device opens sort of control connection (could be it"s actually a service which gets started after device boots from image received from netinstall server via TFTP) which allows netinstall binary to push actual npk files and default configuration ... none of which is possible using simple TFTP. Surely netinstall could relly on other (standard) servers to provide these services, but that would mean multiple servers (by multiple vendors) with appropriate config. I guess that would proove a nightmare for every Mikrotik user but hard-core network admins. I guess the tricky part is to bind BOOTP/DHCP and TFTP services to correct interface, at least BOOTP/DHCP service has to listen to "raw" IP/UDP network interface to catch those broadcasts from client. Even standard ISC DHCP server on linux used to bind to raw network device to deal with requests reliably (I"m not sure about recent versions though).

It looks as if the mikrotik is sending all traffic out of all interfaces, when torching them, you don"t see all traffic coming from another port for example.

The CoA request is supposed to set a new traffic rate limit (using the Ascend codes) to a user, and I"m using this for Hotspot. However, it"s worth checking if the same happens to PPPoE servers under the same conditions. I"ve reported this as the code SUP-100186, for MikroTik staff to see

Mikrotik Dyna dish rev3 and CCR 1016 have problem with watchdog timer and devices reboot when cpu is 80-100% .I run bw test on tcp connections and devices crash.when i back on 6.48.6 all is good.

MikroTik ... could you please provide a list with hardware which supports MACsec with support regarding hw-offloading ... you yet implement some devices with chips which are capable of do MACsec in hardware ....

Many MikroTik"s devices come with a built-in switch chip that can be used to greatly improve overall throughput when configured properly. Devices with a switch chip can be used as a router and a switch at the same time, this gives you the possibility to use a single device instead of multiple devices for your network.

The serial port to be used as a serial terminal needs to be free (e.g., there should not be any serial consoles, LCD or other configuration). Check the previous chapter to see how to disable serial console on a particular port. Use /port print command to see if some other application is still using the port.

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device

ErfanDL please contact support@mikrotik.com with more details, such as, what version you upgraded from, what kinds of clients, and if all are affected, and attach a supout.rif file from the device, if possible while it"s running 7.2, and clients are experiencing this issue.

ErfanDL please contact support@mikrotik.com with more details, such as, what version you upgraded from, what kinds of clients, and if all are affected, and attach a supout.rif file from the device, if possible while it"s running 7.2, and clients are experiencing this issue.

My RB4011 is behind a box from my ISP (Free in France). This box will route 8 /64 ranges to the mikrotik, but onky to a link local address (in fe80::/10)

Mikrotik"s SNMP MIB is not being answered in this release. Updated machine is very colorful in the monitoring right now :-/ apart from that, update on CRS328 went very smooth.

If you have specific improvement ideas in mind that should be added to https://help.mikrotik.com/docs/display/ ... forWindows ,please write to support@mikrotik.com

If you have specific improvement ideas in mind that should be added to https://help.mikrotik.com/docs/display/ ... forWindows ,please write to support@mikrotik.com

My suggestion was as specific as it gets, can"t be more specific since netinstall is closed-source project of Mikrotik"s. I don"t know how to make it more clear: document describing timing of button presses to enter various modes is vague and seems it doesn"t apply very well to audience. I even went into trouble of running wireshark and bootp messages never came through during button presses. As I explained, when setting boot mode to try ethernet once, it tried just fine, which IMO rules out problems beyond ether1 of audience.

BTW, I filed very concrete (unrelated) trouble report (SUP-77961) which is sitting there without any response whatsoever since March 25th. So I don"t see how e-mailing support@mikrotik with some vague ideas could help you more.

If you have specific improvement ideas in mind that should be added to https://help.mikrotik.com/docs/display/ ... forWindows ,please write to support@mikrotik.com

1. please fix IPv6 on help.mikrotik.com it has been down for quite some time already. when you cannot keep IPv6 working on the webservers it is better to remove it.

I won"t bother to understand why MikroTik devs implemented a half-broken-overclocking scaling governor as to tell you the reason behind it, feel free to ask them!

However IMHO, based on your experience, clients should ask Mikrotik to change the way they work instead of asking them for a "last RC to release" changelog. Don"t you think ?

There are different "defacto standards" and there are "company" standards. Mikrotik adopted the software lifecycle terminoligy and the uses an adapted release-cycle. No need to "bitch" around, why does Mikrotik not just bugfix in RC releases - as wikipedia tells us? We already know they do it differently. Ever since. Honstly, they could call it alpha/beta/trunk or whatever. It does not matter.

I"d go with ROS ... but triggered by particular configuration. And I guess you would do Mikrotik developers a favour if you created a supout.rif file while running 7.2 slightly before unit would crash/reboot ... and open a support ticket. The supout file would give devs opportunity to analyze the state of device prior to crash.

I"d go with ROS ... but triggered by particular configuration. And I guess you would do Mikrotik developers a favour if you created a supout.rif file while running 7.2 slightly before unit would crash/reboot ... and open a support ticket. The supout file would give devs opportunity to analyze the state of device prior to crash.

To the MikroTiks listening in: thanks for a great job. Breakdowns suck but with rapid recovery available I"ll still choose affordable & "progressive" over the "enterprise offerings".

To upgrade, click "Check for updates" at /system package in your RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device

The MikroTik devices do not have a real time clock. What you normally see is a counter that counts timer interrupts, but it is not battery backed up.

And hopefully MikroTik at some point revise the first boot v7 procedure to set the time from the v6 database that is being converted (e.g. inside the crossfig program).

The MikroTik devices do not have a real time clock. What you normally see is a counter that counts timer interrupts, but it is not battery backed up.

And hopefully MikroTik at some point revise the first boot v7 procedure to set the time from the v6 database that is being converted (e.g. inside the crossfig program).

dakkonsoulblade - We will look into this and try to see if there is anything we can do about this. Meanwhile please send console output to support@mikrotik.com.

dakkonsoulblade - We will look into this and try to see if there is anything we can do about this. Meanwhile please send console output to support@mikrotik.com.

SNMP["/usr/bin/snmpbulkwalk" "-M" "/opt/librenms/mibs:/opt/librenms/mibs/mikrotik" "-v2c" "-c" "COMMUNITY" "-OQXUte" "udp:HOSTNAME:161" "IPV6-MIB::ipv6RouteTable"]

zapata - The shutdown command is working properly for us. Can you please provide supout file to support@mikrotik.com that would be generated after you did execute this command but the router actually did a reboot, not a shutdown?

Quite accurate description. Upgrading from 6.x to 7.x is an experiment that I would not risk in a production environment. We use Mikrotik routers since more than a decade in an amateur radio envorinment at https://hamnetdb.net/?m=as&q=db0hup and even there we will not upgrade to 7.x. I haven"t seen such a mess with upgrading before, not exactly a success story.

Tried Wireguard in both ends with v.7.1.2 site to site doesn"t work. Not even a sinlge packet is transmitted. Followed every single guide found (even from help.mikrotik.com)

mada3k - Are you sure that all of them are missing, not just a part of them? Please write to support@mikrotik.com and send supout file from your router.

Patrinus - Please send supout file from your router to support@mikrotik.com. We have fixed a similar problem with UPnP. However, it was fixed after this build was created.

Cray - In general, IPsec is working just fine in this version. If you still experience this problem, then please provide supout file to support@mikrotik.com from both endpoints of this IPsec connection. Make sure that files are generated after the connection was lost without any apparent reason.

starfotr - Please provide actual examples to support@mikrotik.com. Provide supout file and detailed description of what is missing after an upgrade. We have not received any complaints like this from anyone else.

elbob2002, qatar2022 - Please send supout.rif files to support@mikrotik.com from your devices and shortly describe your setup, specify connected devices.

nishadul, pe1chl, indy - Look under Tool/Profile which processes are causing the load and try to determine if the load seems to be appropriate for your configuration. If not, then please provide supout file to support@mikrotik.com.

kehrlein - Please send supout.rif files to support@mikrotik.com from your devices and briefly describe your setup, specifying the connected devices regarding the link flapping issue. The same goes for RoMON. Make sure that you generate the supout file while it is not working as expected. Please create two separate tickets.

mada3k - Are you sure that all of them are missing, not just a part of them? Please write to support@mikrotik.com and send supout file from your router.

Patrinus - Please send supout file from your router to support@mikrotik.com. We have fixed a similar problem with UPnP. However, it was fixed after this build was created.

Cray - In general, IPsec is working just fine in this version. If you still experience this problem, then please provide supout file to support@mikrotik.com from both endpoints of this IPsec connection. Make sure that files are generated after the connection was lost without any apparent reason.

starfotr - Please provide actual examples to support@mikrotik.com. Provide supout file and detailed description of what is missing after an upgrade. We have not received any complaints like this from anyone else.

- I have a S2S VPN between my Mikrotik with another Mikrotik (Both on 6.49.4) using L2TP/IPSec. Imagine this remote Mikrotik as a Jump Server Network

- I have deployed another hAP AC2 to the same Mikrotik hub that receives the L2TP on version 7.1.3 trouble device with version 7.1.2 and that works fine (I get access to the GUI).

- Any other Mikrotiks that I have in the similar setup on version 6.49.x works without this issue. Only this one that is running version 7.1.3 that I cannot access via WebFig nor Winbox. Only works SSH.

In general of course MikroTik requires expertise to configure the network at a lower level than typical consumer routers, but in some places (like this) it gets a bit ridiculous.

mada3k - Are you sure that all of them are missing, not just a part of them? Please write to support@mikrotik.com and send supout file from your router.

Patrinus - Please send supout file from your router to support@mikrotik.com. We have fixed a similar problem with UPnP. However, it was fixed after this build was created.

Cray - In general, IPsec is working just fine in this version. If you still experience this problem, then please provide supout file to support@mikrotik.com from both endpoints of this IPsec connection. Make sure that files are generated after the connection was lost without any apparent reason.

starfotr - Please provide actual examples to support@mikrotik.com. Provide supout file and detailed description of what is missing after an upgrade. We have not received any complaints like this from anyone else.

Queue implementation in MikroTik RouterOS is based on Hierarchical Token Bucket (HTB). HTB allows to the creation of a hierarchical queue structure and determines relations between queues. These hierarchical structures can be attached at two different places, the Packet Flow diagram illustrate both input and postrouting chains.

Since Mikrotik doesn"t document the crossfig magic – in fact, it"s just the name for the internal process that does the config conversion during upgrade process - no user sees it - just runs between the reboot. As such, they don"t offer it a tool to try outside of upgrading an actual router, you can"t know if you"re in that 5%. And, if messed up the conversion in the previous rc/beta of V7, it doesn"t run on upgrade from V7 to another V7 – only V6 to V7 once.

Mikrotik"s answer is likely a fair one: test it and see if it works for you, be sure to backup if you do. With BGP, being pretty central to internet routing, you"d want to at close 100% otherwise you"re not just messing up one router, but an entire network/company.

I actually don"t want to look at the source – if I did I could run OpenWRT et"ll on something with a Wi-Fi 6 chip. I do think Mikrotik does an EXCELLENT job at putting common interface over all the services, while still curating what are no doubt a lot of custom drivers/hardware – certainly work we"d rather not do ourselves. So I accept that means there might be incomplete features over the latest Linux builds & RFC/IEEE protocols. In fact, the main think I like ROS table-driven – in fact I describe is like putting SQL over OpenWRT.

FWIW I have CS background, so I actually bought a Mikrotik long ago because it had LUA support – so know feature do disappear/change. 100% agree with @pe1chl on filter rules... still I don"t know what Mikrotik were thinking by leaving the "table-based system" that used everywhere else - surely there could have been a wat to rationalize the route filter interface with the rest of ROS.

They"ll likely point to https://help.mikrotik.com/docs/display/ROS/RouterOS – but the better question is what"s the status of them, some look incomplete IMO WRT V7.

They"ll likely point to https://help.mikrotik.com/docs/display/ROS/RouterOS – but the better question is what"s the status of them, some look incomplete IMO WRT V7. Some of this causes unnecessary posting in the forum, to find out answer that should just be documented....

We know you guys are as much hyped as we are for this release! As much as we appreciate your passion about your particular needs and bugs fixed as soon as possible, note that RouterOS v7 is still actively being developed in most parts and is not a direct replacement for RouterOS v6 yet. We highly value every feedback received and can assure you that every single post you make in RouterOS version release topics is read by MikroTik staff and taken in account.

That is an interesting observation - it may be related to a problem I have reported to MikroTik before. Did you get this issue after upgrade for sure? Or could it have been introduced by another change? And what was your previous version?

We know you guys are as much hyped as we are for this release! As much as we appreciate your passion about your particular needs and bugs fixed as soon as possible, note that RouterOS v7 is still actively being developed in most parts and is not a direct replacement for RouterOS v6 yet. We highly value every feedback received and can assure you that every single post you make in RouterOS version release topics is read by MikroTik staff and taken in account.

We know you guys are as much hyped as we are for this release! As much as we appreciate your passion about your particular needs and bugs fixed as soon as possible, note that RouterOS v7 is still actively being developed in most parts and is not a direct replacement for RouterOS v6 yet. We highly value every feedback received and can assure you that every single post you make in RouterOS version release topics is read by MikroTik staff and taken in account.

Totally don"t want to mare the accomplishments in V7 and no doubt the long push it"s taken on Mikrotik"s end – easy to write about a problem, it"s much hard to fix the code.

Due to the fact that we have made a huge progress in RouterOS v7 stability, we have decided to release it in the testing channel. Please test it where you can and report your feedback on this forum page or send an e-mail to support@mikrotik.com.

That is an interesting observation - it may be related to a problem I have reported to MikroTik before. Did you get this issue after upgrade for sure? Or could it have been introduced by another change? And what was your previous version?

That would be the method that should work, but it doesn"t. It works only on devices with more than 16MB Flash. Reported to MikroTik some time ago, they would investigate. But to fix it, they would first have to release a new 6.49.x version that includes the fix and that you could install as an upgrade, and only then the upgrade to a combined package (and thus also to v7.1) would succeed.

6.48.4 and 6.47.10 were rock solid for me. Credit where credit is due. You at MIkrotik do make nice equipment for cheap, despite the occasional problem.

Thanks! I changed my configuration with the bridge, and this issue is fixed. I remark that I didn"t have this problem with any 6.x release, so, at least for my case, it is a "v7" only bug. Nevertheless, I opened a support ticket, attaching the supout.rif file related to the "old" setup, and referencing your bug report. While I understand that probably the "MikroTik suggested" way to configure is using a bridge instead of a VLAN interface, this is still a big issue, that many other users may experience as well when they upgrade to v7.

Also, the server may identify itself using a certificate whose root CA is not stored in your Mikrotik"s certificate store, hence TLS handshake failure.

He"s referring to Splunk post above probably, but that"s nothing (doesn"t ask for money or something, it"s just a guide on how to use the service and the script required to do so) compared to other users advertising their shady business all over the forum (posts, topics, signatures, images linked to own webserver etc). But if MikroTik is OK with it, why should we care.

The problem is, Mikrotik try to be enterprise or ISP aimed vendor, not home-toys producer. And waiting for years for 7.0 upcoming (yes, it rotates to 7.1 without 7.0 stable release at all!) and getting only version rename instead of stabilizing of current feature set seems to be not what serious guys are used to do.

You are right, "serious guys" deliver you equipment and software and never upgrade it for you, no access to free upgrade downloads, no access to support, unless you pay even extra (above the elevated price) for a "support contract" where your support tickets are handled just like at MikroTik: sometimes you get quick resolution of your problem, sometimes it is just denied ("cannot reproduce") or never fixed because you are a low priority relative to big enterprise.

e.g. MikroTik cap AC uses IPQ4018 chipset, 128 MB RAM, 16 MB ROM. MikroTik tells us, that wifiwave2 drivers (with MU-MIMO support) needs also more RAM, but

Does MikroTik use ATH10K (opensource) driver package or drivers directly from chipset vendors? Has MikroTik tried to load the wifiwave2 package on a IPQ4018 access point with 128MB RAM only? Was it really not possbile to work with it afterwards?

I believe MikroTik did this in part due to complaints: people with routers that have auto upgrade scripts to upgrade to the latest "stable" were complaining that they might have hundreds of devices upgrading to v7 unintentionally when v7 stable was released, and asked for a v7-stable release tree separate from the v6-stable release tree, and MikroTik has done this.