certificate - remove "GoDaddy Class 2 CA" from built-in root certificate authorities store;
console - improve stability;
crypto - improve stability (CVE-2026-67278);
ipsec - fix duplicate connections on IKEv2 retransmissions;
ipsec - improve stability;
lte - fix multi-APN data connections not working on R11l-LTE7 and R11e-LTE6 modems;
ospf - improve stability during recalculation;
ppp - improve stability;
ptp - add manual configuration of PTP message intervals and per-port enabling and disabling;
ptp - fix PTP offset instability under heavy background multicast traffic;
ptp - fix PTP timestamps showing the wrong time on CRS510;
sfp - improve QSFP-DD breakout link establishing to NVIDIA DGX Spark and other devices;
system - improve stability;
user - improve failed login delay logic (CVE-2026-16347);
webfig - improve stability;
wifi - update radio regulatory information;
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)
0voters
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.
That depends how you define "security fixes". Unauthenticated remote code execution? Likely no. Attacker controlled heap overwrite? Probably all of them, since MikroTik doesn't consider this class to be security vulnerability
On our CRS812-8DS-2DQ-2DDQ (98DX7335) routed traffic was offloaded on 7.23.3.
On 7.24.1 and 7.24.2, with the same config, it is not offloaded at all -
everything is routed by the CPU, while l3-hw-offloading still reads yes.
Toggling it, levelling the firmware and rebooting, disabling the VRF and the
VXLAN bridge port changed nothing.
This is SUP-222890, opened on 3 September with supouts from the broken 7.24.2
and the working 7.23.3 state. Still waiting for a reply.
I see no l3hw entries in the 7.24.3 changelog - is this a known regression,
and does 7.24.3 touch it? I would rather not upgrade a production border
router to find out.
MikroTik hAP ax² upgrade went smoothly. Cloudflare DoH is working perfectly with built-in certificates. We cleared out the manually imported ones. Thank you
How much longer? You broke basic netinstall in 7.24.3 again — another "improve stability" that ends up as a brick and an endless bootp loop
Description:
How many times are you going to step on the exact same rake with regressions? Year after year it’s the same story: first, you spend months fighting bugs in IPsec/IKEv2, proving the obvious with proofs, and now you break the one thing without which a device can't even be recovered — basic netinstall.
In the exact same Live CD environment:
Version 7.24.2 works fine.
Version 7.24.3 just drops into an endless loop with non-stop bootp messages in the terminal.
The changelog is silent as usual, except for the default "improve stability" cop-outs everywhere. If you manage to break basic functionality out of the blue, it's no wonder such a mess is going on with more complex features.
Command where everything crashes:
/system routerboard settings set boot-device=try-ethernet-once-then-nand
and then
./netinstall-cli -e -v -a 192.168.88.3 routeros-7.24.3-arm64.npk user-manager-7.24.3-arm64.npk wifi-qcom-7.24.3-arm64.npk
Fix your netinstall-cli already and start properly testing releases before pushing them out, instead of making users spell out bugs from scratch every single time.
Control links (in case you actually decide to check it yourselves):
Upgraded EC25-EU&KNe from 7.24.2 to 7.24.3. Upgrade broke lte. It said it needs a firmware upgrade. firmware upgrade and reboot doesn't solve, the same error stayed.
Had to downgrade to 7.24.2, run firmware upgrade again and reboot.
All of my 8 devices except 2 updated to 7.24.3 via scheduled ansible script at night. I can see for these 2 devices from script log that "system is up to date" and manually system->packages also reports 7.24.2 as latest. Was the update pulled or do update servers have an issue?
