RouterOS version 7.20.2 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.2 (2025-Oct-21 10:28):
bridge - fixed incorrectly blocked ports by STP (introduced in v7.20);
console - fixed incorrect ids in /file/print relative mode (introduced in v7.20);
console - improved stability when printing ids for a non-existent directory (introduced in v7.20)
dhcpv6-client - improved system stability when DHCPv6 client uses "rapid-commit=no", "accept-prefix-without-address=no" and receives only prefix from the server;
dhcpv6-server - do not force set "address-pool" on static bindings with unset pool option after system reboot;
evpn - added basic logging support;
evpn - fixed MAC mobility;
firewall - reduce maximum connection tracking entry count;
iot - fixed an issue preventing LoRa downlink packets from being broadcasted;
ip - removed duplicate CLI parameters for socksify;
log - cleaned up older config by removing leading slashes from "disk-file-name" values;
mpls - fixed LDP label binding if nexthop is link-local address;
poe-out - fixed RB5009 PoE-in indication on cold-boot with no other power source;
routing-filter - change "^$" regexp to bgp-path-len=0 on upgrade from v6 to v7;
routing-filter - use bgp-out-med for set bgp-med on upgrade from v6 to v7;
snmp - fixed SNMP SET operation (introduced in v7.20);
snmp - set maximum message size to 8 KB;
system - fixed ".auto.rsc" file execution (introduced in v7.20);
system - fixed package list fetch from local upgrade server;
system - fixed Windows executable compatibility with Microsoft AppLocker;
winbox - added IP/Socksify menu;
winbox - added support for 200Gbps/400Gbps Rate fields;
winbox - fixed Ethernet Tx Stats (introduced in v7.20);
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.
CHR on Proxmox was inaccessible over IP-winbox after upgrade. RoMON connection was possible and it looked like all IP connectivity (from inside) was OK despite inability to connect to instance over IP address.
In 7.20.2, the MTU value for a VRRP interface created on a VLAN interface created on a Bonding interface is set to 0, and after a system reboot, the MTU value is set to the same as that of the parent Bonding interface (in my case, 1500). As a result, the "MTU > L2MTU" warning for the VRRP interface appears after a reboot.
Noticed also that issue is not occurring if button event is disabled prior boot and then enabled again when booted (event is working on button press), so I think this excludes HW issue.
The upgrade went smoothly. Unfortunately it didn’t fix the veth container issue. I did not that this was not included in the bug fixes for the release so I was hopeful it may have snuck in.
No other issues found yet.
There is a bug in that silly “bgp - automatically create output.network blackhole routes” feature introduced in 7.20: it makes a blackhole route for every BGP connection. I have 5 BGP connections advertising my network and I get 5 blackhole routes in the table.
I would still prefer when this entire feature be removed. When it is kept, at least make it working properly.
Issue with the PPPoE service was not directly related to the PPPoE. The problem, which at least we managed to find and investigate, was caused by PPPoE running on a router which uses NAT. When lot of interfaces for some reason have to go down/up, this causes NAT action to lookup connection tracking table. The table can be huge. Number of interfaces determines how many times table must be looked-up and of course many other parallel processes are running at the same time. Complexity of the process is not directly related to the number of connections in conntrack, but the size of the table.
We have improved situation (returned as it was before) by reducing maximum connection tracking table size. So the reason of this change is directly related to this “PPPoE issue“.
pbr3000 - If you have the same problem even with 7.20.2, then please provide new supout file from the problematic situation on your support ticket.
Yes, we still have the same problem with fewer disconnected customers than 7.20 and 7.20.1. I'll to create new supout files and send them again. 7.19.6 is flawless.
on another note, i downgraded the CRS328-24P-4S+RM on work because since 7.20 SSH is hanging after login, and our production chain stalled because of that (we use it to automatize 911G configuration), and 7.20.2 haven’t fixed it.
