V7.19.3 [stable] is released!

*) system – added new "switch-marvell" and "wifi-mediatek" packages to support upcoming products;

Finally the mystery revealed:
http://forum.mikrotik.com/t/v7-14beta-testing-is-released/172080/464

Yes I did.. Cr*p

I have a question regarding the RouterOS v7.19 update process. My understanding is that, prior to updating to v7.19, I need to upload the v7 universal package and then reboot. This should update my factory-firmware version to 7.18.2. It’s also critical for me that I do not want to set protected-routerboot=enabled or disable the reset pin. Is my understanding correct?, and are there any other critical steps or considerations I should be aware of to ensure a smooth update?

Noone needs to upgrade rooterboot unless you want to enable proctected rooterboot and a error measage advices so.

Do not use v7 general package to update RouterBOOT, otherwise it will cause the device to become bricked. My RB5009UG+S+IN became bricked after using V7 general package to update RouterBOOT. I have already filed a bug ticket.

Not many devices support protected routerboot upgrade and it looks like exact list of supported devices is not easy to find.

19:57:14 system,error upgrade failed, free 73 kB of disk space

Before I upgraded I checked:

                  version: 7.16.2 (stable)
                      cpu: ARM
           free-hdd-space: 616.0KiB
          total-hdd-space: 16.0MiB
               board-name: D53G-5HacD2HnD
                 platform: MikroTik

But 616kb free space was not enough for upgrading to 7.19.

:slightly_frowning_face::slightly_frowning_face::slightly_frowning_face:

Take care with this release! I have several devices that suffer issues with certificates, including malfunction of fetch and CAPsMAN. Investigating…

Maybe this applies ?

Is that a comment for me? I have exactly the certificates installed that I need. It worked before, and things should not break with an update.

Looks like removing and reimporting the certificates helps, at least for public CA certificates.

No idea how to handle the CAPsMAN case… In worst case I have to start over with a clean CA. In that case the built-in certificates are of no help, definitely.

I guess things like IPSec could be effected as well…

Updated my ax3 and ax2 (cap) and two remote ac2. All fine and working as expected. CAPsMAN is working. The ax3 sent the update to the ax2 without issues.

Also did the Routerboot upgrade on all devices on system/RouterBoot Upgrade using Winbox.

Just upgraded a “dumb” cap ac which runs in cap-mode wifi-qcom-ac and nothing else. This free-hdd-space is melting…

before:

                   uptime: 3d20h36m16s
                  version: 7.16.2 (stable)
               build-time: 2024-11-26 12:09:40
         factory-software: 6.44.6
              free-memory: 32.2MiB
             total-memory: 128.0MiB
                      cpu: ARM
                cpu-count: 4
            cpu-frequency: 448MHz
                 cpu-load: 1%
           free-hdd-space: 824.0KiB
          total-hdd-space: 16.0MiB
  write-sect-since-reboot: 704
         write-sect-total: 60495
        architecture-name: arm
               board-name: cAP ac
                 platform: MikroTik

after:

                   uptime: 2m35s              
                  version: 7.19 (stable)      
               build-time: 2025-05-22 07:53:44
         factory-software: 6.44.6             
              free-memory: 36.0MiB            
             total-memory: 128.0MiB           
                      cpu: ARM                
                cpu-count: 4                  
            cpu-frequency: 448MHz             
                 cpu-load: 0%                 
           free-hdd-space: 196.0KiB           
          total-hdd-space: 16.0MiB            
  write-sect-since-reboot: 205                
         write-sect-total: 61102              
        architecture-name: arm                
               board-name: cAP ac             
                 platform: MikroTik

And one thing I noticed on another device:

/ip dns adlist
add comment="Multi PRO mini" disabled=yes url=https://raw.githubusercontent.com/hagezi/dns-blocklists/main/adblock/pro.mini.txt

I have this disabled adlist. But ROS still trys to import the list - I can’t figure out why? I have the default dns cache size of 2048kib and of course this fills it up immediately. But it should not - why does routeros import a disabled list?

 2025-05-22 21:39:16 dns,error [adlist] adlist read: max cache size reached
 2025-05-22 21:39:16 dns,error [adlist] could not add name, stopping import
 ....to finally
 2025-05-22 21:49:25 dns,error cache full, not storing
 2025-05-22 21:49:25 dns,error cache full, not storing [ignoring repeated messages]

cache-used:

/ip/dns/print
                   cache-size: 2048KiB
                   cache-used: 2004KiB

Once I remove the single, disabled entry from /ip/dns/adlist suddenly the cache drops to normal:

/ip/dns/print
                   cache-size: 2048KiB
                   cache-used: 217KiB

Why does a disabled adlist take up DNS cache? This can’t be right.

I think some previous versions cleared a little more space after a second boot. Have You tried it?

This is already after the second boot (because of firmware auto-upgrade).

:index_pointing_up::index_pointing_up::index_pointing_up:

Oh, now there are dynamic services in the services section?
Finally, the system services from other RoOs sections are visible.

If only they were in the firewall too…

Opened SUP-188791 for my certificate issues…

good evening everyone.
has anyone already tested it and how it behaves on a ccr1072?

what firmware do you recommend that I can use to have a properly functioning Border?

at the moment I have 7.16. 2 but I detect traffic drops and Peers

thank you for the advice.

  • __


Dream

If you plan to use HAP AC2 and beyond - change the flash drive to a larger capacity. And also buy a license for it…