7.24.2 [stable] is released!

Announcements
1

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.2 (2026-09-03):

This is an important security update. Most configurations are not at risk, but upgrading is highly recommended. To give time to update your systems, we are not currently publishing detailed information.

*) bgp - fix BGP link-local nexthops unreachable over a VRF and a crash when disabling an unnumbered connection;
*) btest - improve stability;
*) certificate - fix changing the built-in trust store setting (introduced in 7.22.2);
*) console - fix a memory leak in background scripts;
*) console - improve stability;
*) container - improve container image extraction;
*) dhcp - improve stability of DHCP handling;
*) disk - improve stability of the SMB server;
*) ethernet - improve stability on hAP be3 Media;
*) fetch - improve stability of the TFTP client;
*) ipv6 - add a neighbor discovery ping;
*) leds - fix LEDs set to interface status staying off when the interface is active;
*) lte - fix the RG650E-EU modem not bringing link up after a firmware update;
*) ping - add parameter checks for arp ping;
*) poe-out - fixed missing PoE-Out interface on hEX PoE lite, RB260GSP, OmniTIK 5 PoE, PowerBox;
*) ssh - refactor SSH internal processes and improved system stability;
*) system - improve stability;
*) webfig - improve stability;
*) winbox - fix the "addresses" spelling in read-only fields;
*) www - improve stability;

To upgrade, click Check For Updates under System/Packages menu and select the Stable 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.

3

Any information about which version will be next long-term and when?

4

7.23.4 in around 30 minutes to one hour

Longterm is out 7.23.4 [long-term] is released!

5

Ah, so people following long-term will have few hours to check their environment and make appropriate config changes against 2 versions worth of changes to receive security update, because backporting to 7.21 is too much work for you? Absolute joke... Welp, whatever. This stable release already narrows scope significantly so give it 6 hours and we should have reproducible PoC.

6

The bugs affecting network stability that I reported on the forum and to tech support haven't been fixed, but Logn Term has already been released! Bravo!

7

toxi, could you be more specific please? link to SUP issue numbers, so I know which to check

8

I wonder if this might have something to do with the "security" part. This is actually possible to know if most or small part of devices have their SSH exposed to public internet (to be able tell if "most configurations" are/are not at risk)...

9

Not sure what you mean, but SSH is not exposed by default to the internet on any home devices. Same as any other port. Home devices have their ports blocked by firewall from the public networks.

10

This is exactly what I was meaning.

11

CCR2004-16G-2S+

  1. using winbox 4.3 Check for updates is broken ...
  2. using winbox 4.3 Switching to testing ... check for updates does not work
  3. to upgrade from 7.24.1 stable to 7.24.2 stable I had to download the file manually and then install
12

SUP-221934
SUP-222003

In short:

  • the update to 7.24 (7.24.1) breaks the Wi-Fi radio bridge with the repeater, and the entire Wi-Fi network behind this radio bridge crashes.
  • a small bug with windows in the GUI in Winbox 4.
  • interfaces also freeze when editing information about them and when cloning (they randomly freeze).
13

I was able to upgrade from 7.24.1 to 7.24.2 without downloading manually. After upgrading everything looked normal, and internet access was working, but for a few minutes "Check for updates" was not able to reach the update site. It looks normal now - I didn't change anything. Perhaps the update site had a brief issue?

14

RB5009 check for updates, 7.24.2 is offered and downloaded, reboot from winbox, returns running 7.24.1 as if nothing happened.

(log shows reboot requested but no upgrade attempt)

Tried again and it worked OK. This is not the first time that happens.

15

possibly one of the mirror servers did not yet have the package, or something like that. Simply try again like you did.

16

Ok but when I click download, it says the download was OK and I have to reboot, and then it does nothing, that is not right IMHO.

When it fails to download, there should be an error message. I have seen that when e.g. the network was flaky.

17

wAP AX (wAPG-5HaxD2HaxD) was updated 7.23.2 -> 7.24.2

caps slaves-static is set to yes, but 10 of 14 wifi interfaces were recreated (old ones deactivated) and 1 remaining assigned to the wrong SSID. I needed to delete the old ones and assign the new ones to my bridge again.

18

Upgraded rb5009upr, 3 cap ax's, crs310 (RouterOS RouterBOOT), absolutely 0 issues.

19

RB5009 and wAP AX both upgraded straight from 7.24.1.

Didn't get the issue @pe1chl with 7.24.1 being offered so hopefully that's just a download mirror delay.

Also didn't get the issue @AndyKl had at either 7.24.1 or 7.24.2. I only have 2 secondary WiFi interfaces and they are both dynamic too. Hope you get that resolved quick and painless if possible.

20

Can we assume that (as usual) routers with all management ports protected are the not-at-risk boxes?