7.24.6 [long-term] is released!

Before an upgrade:

  1. Remember to make backup/export files before an upgrade and save them on another storage device;
  2. Make sure the device will not lose power during upgrade process;
  3. Device has enough free storage space for all RouterOS packages to be downloaded.

What's new in 7.24.6 (2026-10-30):

  • bridge - fix BPDUs leaking to the wrong dual-connected bond in MLAG (introduced in v7.24);
  • bridge - fix VLAN-tagged traffic being looped back in MLAG setups on CRS8xx series switches;
  • dude - fix the server not starting at boot when data-directory is on a USB disk;
  • ethernet - fix occasional packet loss on hAP be3 Media;
  • fetch - fix HTTP fetch getting stuck in a "bad HTTP response" state;
  • ipsec - fix IKEv2 EAP-TTLS client failing with invalid trust store (introduced in v7.21);
  • ipsec - fix IPsec tunnels failing after migration from the old QKD settings;
  • ipsec - fix IPsec tunnels not establishing when an address my-id is configured on the responder;
  • ptp - fix PTP support on CRS804-4DDQ;
  • quickset - fix the WAN interface being selected incorrectly;
  • route - improve static route handling performance;
  • routing-filter - fix any-regexp community matcher matching an empty community attribute;
  • routing-filter - fix community delete, filter and modify with regexp-only community lists;
  • routing-filter - fix host matching in address lists with more than 64 ranges;
  • sfp - fix DAC EEPROM corruption when disabling 400G ports on CRS804 and CRS812 switches;
  • system - improve stability (includes CVE-2026-98432);
  • system - stop the flash configuration store from growing on dynamic configuration changes;
  • wifi - reuse freed station association IDs;
  • wifi-mediatek - fix roaming between APs belonging to the same MLO group;
  • winbox - fix bridge filter window disabling valid fields for IPv6 rules;

To upgrade, click Check For Updates under System/Packages menu and select the long-term Channel in RouterOS configuration interface, or head to our download page: http://www.mikrotik.com/download

  • Everything went smoothly
  • I encountered an issue after the update (please post about the device, configuration, and unexpected symptoms)
  • I encountered an issue, but solved it (please post the solution)
0 voters

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

Please keep this forum topic strictly related to this particular RouterOS release.

I'm sure this has been asked 100 times already, but just to be sure: 7.24.5 stable + the changelog here = 7.24.6 long-term... right?

I'd really wish Mikrotik did a Change log from the previous long term to the latest Long Term so we didnt have to piece together our own collage of release notes. its not the end of the world and other vendors are guilty of it as well but when they're consecutive dot point releases they are easy to follow, when they jump from 7.21.x to 7.23.x then to 7.24.x it is a little harder to follow as the change log can consist of stable and long term elements in the period between.

Upgrade seems fine.

Still issues with WebFig and inconsistent data with WinBox 4.

Also issue with WebFig and colume table setting. Check design skins that are enabled but not showing up on page.

For example, if I enable all colume table setting for ipv6 addresses in WinBox. There not showing up in WebFig.

WebFig still needs a lot of work. But yeah, for the love of GOD! Can someone just work on WebFig and match it with what WinBox has.

I have tcp syncookies and tcp time stampes enabled. Should I disable it?

Originally my MT router was behind another router with these options enabled.

I came to ask the same question. Authors, please answer.

I am seeing a slightly higher CPU usage. Normally was almost idle, after the upgrade (RouterBOOT included) I have a mean 1% CPU usage.

Fine here at 0%

Since the last long-term, 7.23.8, i'm guessing that these are the changes plus the ones listed in this topic.

Trying a cold boot.

I'm guessing too, but I'd like to know for sure. If it were clearly written in the changelog, there wouldn't be any question.

It is also completely unclear when you need to update the bootloader and when it is not necessary. Because two reboots take longer on critical objects. Why not update the bootloader in one reboot after so many years is also not clear to me.

Its always recommended to update the bootloader.

Keep the versions in sync, no questions asked.

The thing is currently bootloader version number is not in sync with bootloader version and in many RouterOS releases there are no changes to bootloader code...
I prefer previous practice when bootloaders used to carry their own (actual) version numbers so one would know exactly when to upgrade...

There are questions here. If updating the bootloader is important and officially recommended, why isn't it forced and updated in a single reboot? It's a strange decision to leave the old bootloader by default, allowing the device to malfunction. And no one can say exactly how, because the bootloader can differ from the firmware in any number of ways, and everyone's experience is different.

Okay, so let's say I decided to strictly follow the official recommendations despite the default option to not update the bootloader. Can I do this in a single reboot along with the firmware update to minimize downtime? As far as I know, no.

The bootloader doesn't suffer modifications at every release (they are mentioned in the changelog if any), the version of the bootloader was detached from the RouterOS version in the past but someone decided that it's best to keep the versions in sync so every RouterOS since then has a "new" bootloader even if the only thing changed is the .. version.

That's exactly what I'm saying: this doesn't make sense, and it would be better to update the bootloader version only when there are real changes (like firmware for LTE modems), or at least update it automatically along with the firmware during a single reboot, so that the versions are synchronized for all users. This makes sense, but for some reason it's done the other way around.

It's just a version sync. It's just how it works even if nothing has changed.

Yes, using the method rextended suggests:
What is the proper way to update? - #5 by rextended

If you want full changelog you go from 7.24 to 7.24.5 and then append 7.24.6 changes here, making sure to remove any double entries in (7.24..7.24.5) for fixes that were backported to previous long-term train. Or you could just switch to stable, because long-term is just oldstable and seems to last for exactly one version anyway.

I'm talking about CVE-2026-98432.
I'm coming from 7.24.5, but 7.25 seems too unstable, so I'm sticking with 7.24.6 for now :wink: