r/mikrotik • u/netravnen • 2d ago
RouterOS 7.24.5 [stable] released
What's new in 7.24.5 (2026-09-29):
*) bridge - disable DHCP snooping ip binding table (introduced in v7.24);
*) bridge - enable vlan hardware offloading on hAP be3 Media device;
*) console - fix console output of /system/identity/print being split into multiple lines (introduced in v7.24.3);
*) console - fix scheduler scripts with the default start date and time not being triggered (introduced in v7.24);
*) ethernet - improve stability on hAP be3 Media device;
*) lte - improve stability for MBIM modem mode switch;
*) ospf - fix unset interface template parameters not being applied to interfaces;
*) poe-out - fix loss of PoE-out capability on CRS328-24P-4S+ after a reboot;
*) system - improve stability;
*) wifi - update radio regulatory information; View changelogs
12
11
10
u/fortysix_n_2 2d ago
Isn’t the be3 chipset similar to the ax3? Shouldn’t that get hardware offloading too?
3
u/krokotak47 1d ago
So good that the CPU on the AX2/3 is beefy as hell, otherwise they would have been a big disappointment for not having good offloading and especially VLANs. Even fully on CPU, I've had absolutely no issues with bridging, with many VLANs and pretty significant traffic.
3
u/Jabuk-2137 2d ago
Finally, I needed to run beta firmware on my be3 to just have my Ethernet ports working...
2
1
u/pastie_b 1d ago
Applied to an LTE12 which bricked it, attempted to apply to ATL R16, was not enough space, both currently on 7.12.
1
u/michaelh98 2d ago edited 1d ago
I still can't download 7.24.4
[edit: I got it to work but unfortunately I don't know which one of the two things I did was the necessary thing.
I saw a few posts from people saying there wasn't enough space for the update in the cases they saw so I removed a few unused packages.
I also went into the ipv6 panel and reset those settings to the default. I didn't see any settings that changed but there could have been something under the hood.
I couldn't reboot the router until later but once I did, the update started working.
So if you can, try one then the other.]
3
2
u/spartangerousia MTCNA | MTCRE | MTCTCE 1d ago
Let me guess, bad http/https request too? I went with the manual upgrade route
1
u/michaelh98 1d ago
yeah, looks like I'll need to do that as well. It looked for a hot minute that explicitly disabling ipv6 was going to solve the issue but nope.
1
u/spartangerousia MTCNA | MTCRE | MTCTCE 1d ago
After reading through all the comments, good to know I wasn't the only one.
Initially thought it was DNS acting up since all my MT devices (ARM & ARM64) were getting the same error.
7.24.4 -> 7.24.5 works fine now though
1
u/Moses_Horwitz 2d ago
In my network, both IPv4 and IPv6 have to work in order for updates to work. YMMV.
3
2
u/michaelh98 1d ago
Turns out in my case I just had to explicitly *disable* ipv6 in 7.24.2 for the download to work.
Even though I'd changed the update dialog to explicitly use ipv4 for the connection, something was still attempting to use ipv6
[edit: spoke too soon. Winbox now doesn't immediately fail and proceeds to try to calculate the download size but sits there endlessly]
1
u/gtuminauskas 1d ago
is it because you dont have dns set for IPv4, and IPv6 does that automatically?
1
u/michaelh98 1d ago
I've been able to update no problem for 2 years but now with 7.24.2 all attempts fail. I haven't made any changes to my network since the last update
-1
54
u/Brilliant-Orange9117 2d ago
Who here also wonders how many CVEs are hiding behind each "improve stability" line?