V7.23.1 [stable] 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.23.1 (2026-Jun-02 12:25):

  • app - fixed bogus configuration export;
  • app - fixed making empty directories when running configuration export;
  • bgp - fixed memory leak;
  • bridge - fixed stability issue when using DHCPv4 snooping;
  • disk - avoid reading SCSI stats all the time to allow disks to go to sleep;
  • disk - improved error message when a swap file is created without "file-size" specified;
  • ethernet - fixed stability issue with TSO on Alpine CPUs;
  • firewall - improved system stability;
  • ipsec,ike2 - improved TSi validation to prevent modecfg address conflicts;
  • ipv6 - do not disable IPv6 FastPath when Traffic Flow is enabled;
  • ospf - added missing interface parameters;
  • ospf - fixed unresolved route problem when "routing-table" setting is used;
  • ptp - rename "smpte" to "smpte-2059";
  • route - improved overall stability;
  • route - removed deprecated "/routing/route/rule" menu;
  • switch - fixed rare possibility of tx-timeout or simultaneous flap of all switch ports on devices with Alpine CPUs;

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.

Is SUP-215939 fixed in this release?

This sounds serious.

Big if true.

everything went smoothly no issue

Is it possible to do the same for ARM, especially for devices with 16MB ROM like the hAP ac2, cAP ac, cAP XL ac, Chateau LTE6, Chateau LTE7, wAP 60G, wAP 60G AP, LHG 60G, SXTsq 5 ac, LHG XL 5 ac, etc?

I keep seeing this after the last few updates, how do i fix it. Hap ax2 not touched any of that stuff.
acme

Thank you for the update. The update has resolved this issue:

However, this one is still present:

On my RB5009, /app export and /app export show-sensitive produce the following output:

The problem is that the RB5009 doesn't have any external storage attached, so /app settings disk cannot be configured (is none). As a result I cannot use the reset command to clear the setting:

image

The command fails because "need to configure disk to install apps to in /app settings". Which cannot be done because there is no disk available.

On a CHR installation with mounted disk partition, I can run the reset command for almost all apps, and /app export produces a clean output. However, /app export show-sensitive still shows two apps with secrets:

And there is no way to clear / reset / set to empty the secrets properties (failure: cannot change number of secrets).


To recap: Empty directories are no longer created. /app export still has bogus entries. Entries cannot be reset if device has no external disk. With external disk, most entries can be reset, except for two that have the secrets parameter that can never be empty, and will always show up with /export show-sensitive.

So for now, I'll still be using

/export path=!app show-sensitive

for my configuration backups.

From now I read any Improved System Stability for stable functions like firewall or routing as DOS vulnerability or other security issues. If they start showing up in Long-Term as well we know this is the case.

Still only a guess of mine and I can be dead wrong but I will treat them as this anyway.

I updated and it said "system;error;critical" and "System rebooted because of ping watchdog timeout."
Then I did a manual restart. And then it crashed into a kernel panic.

That would be nice, although maybe not enough since hotspot is relatively small package at ~130k...
On the other hand QCA9984 firmware (part of wifi-qcom-ac which is causing the most problems on these devices) is close to 500k and is used only on a couple devices with much more resources (like RB4011iGS+5HacQ2HnD-IN and Audience) so making that a separate package would really improve storage size usage...

And the Prestera DX driver used by the CRS switches with 32bit ARM CPUs:

which increases routeros for all ARM devices by 220KB (after compression). They should do the same as for the CRS804 (which is ARM64) and pull the switch chip driver out of the main package:

After upgrading a CRS305 and rebooting twice, Ethernet speed with a 10 Gbps ONT was very bad (less than 1 Mbps). Rebooting again fixed the issue.

I bet the changes being made to achieve VRF are breaking old things that used higher-layer features to solve lower-layer problems.

A colleague once said: "Opening a can of worms..."
At least they've already opened the can and are killing the worms one by one.

If someone did an upgrade and forgot that package, it would cripple the device. For many of those devices (i.e. NetPower16P or CRS326-24G-2S+IN), the management port is a part of the switch.

The bigger boys, like CCR2x16's and CRS804 have ports that go to the CPU directly.

Remember ROS 7.13? The wireless section was separated into its own package. What if someone forgot to install the wireless package on a hAP ac2?

That happened relatively rarely. What happened much more often was: "My hAP ac2 has no free storage left. Help!"

PS: this discussion on the package size thingy is off-topic.

admin@RB5009UPr] /system/routerboard> pr
       routerboard: yes         
             model: RB5009UPr+S+
     serial-number: XXXXXXXXXX
     firmware-type: 70x0        
  factory-firmware: 7.16.2      
  current-firmware: 7.23.1      
  upgrade-firmware: 7.23.1      

Did a upgrade with the package manager download and install.

[admin@RB5009UPr] /system/routerboard/settings> pr
              auto-upgrade: yes                       
               boot-device: nand-if-fail-then-ethernet
         preboot-etherboot: disabled                  
  preboot-etherboot-server: any                       
             cpu-frequency: auto                      
             boot-protocol: bootp                     
       force-backup-booter: no                        
               silent-boot: no                        
      protected-routerboot: disabled                  
      reformat-hold-button: 20s                       
  reformat-hold-button-max: 10m                       

Afterwards it did a double reboot but seems to not fully install the updated kernel.

Did a few reboots but kept getting autosupout files.

I disabled auto-upgrade, downgrade to 7.23 and went with a manual upgrade and download the 7.23.1 packages to the router.

No more autosupout files.

Not sure if it had to do with auto upgrade or just a bad package manager download.

TIA

That doesn't make the router unreachable via the Ethernet ports.

The inconvenience is not bigger than with someone going to the Interfaces window in WinBox, press Ctrl+A and click on the "Disable" button. The Interfaces window is even easier to reach than the Packages window (top menu vs. sub menu).

Similar to the upgrade to 7.13. The upgrade to 7.25 will automatically introduce routeros and switch-marvell on the ARM devices. CRS owners will simply ignore everything. 16MB AC WiFi devices owners who run out of space will read the forum or documentation and know to remove switch-marvell once. MikroTik can even build something into 7.25 that automatically removes switch-marvell from those devices.