RouterOS version 7.20.6 have been released in the "v7 stable" channel!
Before an upgrade:
Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
Device has enough free storage space for all RouterOS packages to be downloaded.
What's new in 7.20.6 (2025-Dec-04 14:00):
bgp - fixed missing VRF parameter in template configuration after upgrade;
console - improved service stability and memory allocation when using "regexp" operator;
console - improved service stability when executing commands that can timeout;
dhcp - execute "lease-script" with DHCP server creator user permissions;
pppoe-server - fixed client disconnects when multiple servers with different service names are active (introduced in v7.20);
routerboard - do not show "upgrade-firmware" if available installation is older than minimal supported one;
socksify - listen on all addresses for incoming connections;
system - updated PCI id names;
To upgrade, click "Check for updates" at /system package in your 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. 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.
I have a pair of CCR1009 routers at one location. They function as L3VPN MPLS routers, providing several VRRP gateways for the location's subnets in several VRFs. Unfortunately, after upgrading from version 7.19.6 to 7.20.5, and then to 7.20.6, the following messages began appearing in the logs shortly afterward:
daemon err XXXXX script error: action timed out - try again, if error continues contact MikroTik support and send a supout file
At the same time, all routes disappear in all VRFs on the router. However, BGP and MPLS continue to function, according to information from RouterOS.
The only solution is to downgrade back to version 7.19.6.
OpenVPN still doesn't work on firmware version 7.20.6 stable (7.21rc1 dev).
Link to the problem: V7.20.4 [stable] is released! - #157 by toxi
I created a support ticket #[SUP-200620] - 2025/10/03
Things of this kind infuriate to the level that makes to want to start flood everywhere about the ignorance of these who removed access to download archive
I lost about an hour of worktime yesterday to this ignorance.
I understand that newbie can probably have some ease findind a match about WHAT to download from the new download section, but it’s a nightmare for others.
Is it too much asking for a SINGLE long page with all the stuff together (like before, even better) ?
it’s crazy spending 2h getting files for every different arch..
where am I supposed to get older version when I NEED them ?
A mounth ago I stupidly deleted the custom script I made to download all versions every now and then.. it was a couple of years that I didn’t use it.
I don’t even know if it still would work ..anyone is still using something similar ? can you share.. thanx.
Upgraded a CRS309 from 7.20.5 to 7.20.6 and I saw strange messages in the logs about OSPFv2 and OSPFv3 default processes starting. Looks like the default OSPF instances (default-v2 & default-v3) were enabled automagically. I’m not sure if this has happened earlier, but I’m pretty sure I never have configured it by myself. Could have happened in a previous release. (I don’t have remote logging enabled, sry, I know…)
I think mikrotik very directly implied there was a CVE against that version and older, and they didn’t really want people downloading those versions.
Thanks for the schema! I used your info to recreate my deleted script—this time I’ve put a bit more care into it. While I was at it, I added a PowerShell version for Windows users. I initially asked GPT to help with the translation, but it made a mess, and I had to figure out how to fix it. I’m pretty terrible at PowerShell, but with some help I managed to get it working.
Here’s the repository with the scripts in case you need them:
If you only need one arch → you typically have a single “default route” → MT web site (pun intended)
If you’re the kind of guy who tests one specific version and then, maybe a month later, starts upgrading and netinstalling a bunch of devices → you probably want multiple/all arches handy in a convinient folder on you PC/LAN.
In my case, I often work in places with limited internet (aka proxy whitelist) or totally air-gapped… so yeah, you got me.
we are using the 7.19.6 that is working error-free everywhere. I don’t dare to upgrade. I have a bunch of customers with their router to the latest stable to test, but in any case I will upgrade to a newer one if it doesnt fix an unfixable security issue or bug…. Till now 7.19.6
(pun intended)