RouterOS version 7.20.5 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.5 (2025-Nov-27 10:17):
bgp - fixed BGP origin attribute initial value;
bgp - properly apply link.local connection setting when it is used as an interface;
bgp-vpn - fixed prefix matching for filters "dst" matcher;
ospf - fixed wrong LS Ack warning;
pimsm - added comment for static-rp;
route - fixed gateway print when gateway is equal to BGP peers address;
route - fixed some routes installed in main routing table instead of specified VRF;
route - make discourse work with destinations from VRF;
routing-filter - fixed inline filters that process BGP communities;
system - improved incoming TCP connection responsiveness;
user - improved login service stability on busy system;
webfig - fixed broken WebFig after going to Quick Set (introduced in v7.20.4);
wifi - improved regulatory compliance for Bangladesh country profile;
winbox - group L3 and L4 fields under switch rules menu;
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)
I encountered an issue, but I am not sure if it is related to this release
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.
That is not a bug report, it is a ChatGPT destillation of a single log message: “router was rebooted without proper shutdown”. That guy should better contact Mikrotik support instead of posting this AI collection of utf8 icons on linkedin.
Did you cast your vote ? If you don't it may take very long time to fix, if ever. From what I see Mikrotik is in the entirely new modus operandi, and it is driven by metrics. The poll in the announcement is exactly that. The numbers WILL be looked at (by the decision makers), and if your problem is not on the list, it will remain just that... a problem that nobody looks at. Unfortunately that how it works. Go ahead and cast your vote. But be aware, that RouterOS Software Engineers will hate you because that is how you put work on their plate, so be nice to them.
P.S. The scope of issues fixed in the latest release speaks volumes. From what I gather the main focus now is on the enterprise products.
One of my scripts that used to work in RouterOS 6.x still need to be reworked as it doesn't work in 7.x. version.
The script is several hundred lines long, so tracing the root cause makes it a whole separate project.
But unfortunately with most Enterprise level hardware, the support is not included and you have to pay even more than the already high price to get that. Even generally released software updates that mostly are just for bug fixing are not free for original buyers of the hardware, they need to have a maintenance contract for that.
I have OpenVPN working fine with concurrent connections from my phone and from my laptop and from a hAPac2 running 7.20.1 to my RB1100AHx4 previously running 7.20.4 and currently running 7.20.5.
I am using UDP and not TCP though if that is a consideration.
