7.23.7 [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.23.7 (2026-09-16):

  • lte - prevent the modem firmware from being deleted for RBSXTLTE3-7, EC25-EU&KNe, EG25-G&KNe, EC25-EU&SXTsq, EG25-G&SXTsq (introduced in 7.23.6);

If you have already upgraded to 7.23.6 or 7.24.3, follow these steps to restore LTE functionality on affected devices:

  1. Upgrade RouterOS to version 7.23.7 or 7.24.4

  2. Update the modem firmware:
    /interface/lte/firmware-upgrade [find] upgrade=yes

  3. Reboot the router.

For more details, see:
https://forum.mikrotik.com/t/warning-lte-interface-stops-working-after-upgrade-to-7-23-6-7-24-3

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.

Thanks, I'm moving the tests I was running from 7.23.5 to 7.23.7. Currently, the CHR is NOT showing any issues after the update.

Noticed my ansible stopped working on the upgrade. Did some digging and its dying at the initial login where it checks the identity. Found in SSH (from my machine and internally doing a /system ssh 127.0.0.1), doing a /system identity print

[admin@MyRouter] > /system identity print
name: M
y
R
o
u
t
e
r

Where I would have expected

name: MyRouter

I have only tested on my rb5009s, but I see this on all 14 I've upgraded.

This also happens on my RB5009 and on both of my wAP ax. How on earth did MikroTik manage to screw this up?

Edit: this bug was introduced in 7.23.6.

by no means do I know what I'm doing here, but my ansible plugin for routeros is here:
~/ansible-pylibssh-venv/lib/python3.13/site-packages/ansible_collections/community/routeros/plugins/cliconf/routeros.py

and I just changed this:

    identity = self.get('/system identity print')
    data = to_text(identity, errors='surrogate_or_strict').strip()
    match = re.search(r'name: (.+)$', data, re.M)
    if match:
        device_info['network_os_hostname'] = match.group(1)

To this:

 identity = self.get(':put ("name: " . [/system identity get name])')                                                                                                   
        data = to_text(identity, errors='surrogate_or_strict').strip()                                                                                                         
        match = re.search(r'name: (.+)$', data, re.M)                                                                                                                          
        if match:                                                                                                                                                              
            device_info['network_os_hostname'] = match.group(1)    

and my ansible is working again...

This build went ontp my hAP-ax2 without issue, but considering the current slew of new bug (coupled with no LTE gear), I backed it out and will wait to see what transpires, since I now have everything (local and remote) on 7.23.6 andeverything but OpenVPN is working. (Known good configs now get a "no crypto algorithm available" despite just about everything being selected. (This was seen in 7.23.5 as well ... it may have last been seen OK in 7.23.3, not sure . . . . ). Clients have NOT updated, so this isn't the BS that OpenVPN introduced.

SSL/TLS errors introduced after upgrading SUP-223981

@tadawson

Have you configured SCEP by any chance?

Seems I have really slow IPSEC connections ...
Did not have that on .5

i confirm this, its must be a bug or something

Upgraded my ac2 from previous long-term 7.23.5 and wifi suddendly comes back, so far so good. I also see the same system/identity/print result with each character per line but it's not a concern for me.

After the update, some of my devices cannot be connected to Dude as Router OS / Mikrotik, others work fine... I understand the problem is in TLS and updating the certification system. How can I overcome this? The problem has affected RB962UiGS-5HacT2HnTб RB951Ui-2HnD, RB962UiGS-5HacT2HnT, RB951Ui-2HnD, CRS112-8P-4S, L009UiGS-RM, RB750 (infinitely connection timeout, next attempt at)

It is the same on hAP ax S which I upgraded to a "long-therm" 7.23.6:

system/identity/print 
  name: h
        A
        P
        a
        x
        S

Good thing is that export does not screw it up too :slight_smile:

 system/identity/export 
/system identity
set name=hAPaxS

And of course on 7.23.7 it is the same, so yeah now we know.

So how on earth does fixing LTE firmware, mess up /system/identity/print.... So much for accurate changelogs & basic QA.

It must be system stability improvement introduced back in the old long-therm 7.23.6 which also screwed LTE modems :slight_smile:

Same on 7.24.4 as well. Looks "artistic" but serves no useful purpose

same here ... dude was unable to connect
also I was unable to connect to the remote devices behind the vpn endpoint using romon ...
I needed to downgrade dude machine, gateway, vpn endpoint ...
All back on .5 and it works again

The recent release looks like a bad joke, and it's not even funny. :slight_smile:

Interesting - I had the problem with MIPS device but Dude connected to ARM and ARM64 devices without problem. Maybe it really is related to this identity "format" problem after all. Let's see if this will be corrected in 7.23.10 or 7.24.8 :slight_smile:

I doubt the "format" issue is specific to system/identity value print, it is more likely some library function that is broken and that can be used in other places as well, pretty scary if you imagine that it can also be used to generate kernel netfilter rules for example :clown_face:, hopefully it is not the case but for now I will certainly not install this on anything...

7.23.6

sys/id/print
  name: h
        A
        P

sys/id/print  
  name: C
        A
        P