RouterOS version 7.2rc6 has been released “v7 testing” 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.2rc7 (2022-Mar-30 15:21):
*) route - allow OSPF and RIP redistributed routes to be matched by routing filters;
What’s new in 7.2rc6 (2022-Mar-30 10:56):
*) ccr2004 - improved PCI timeout handling on CCR2004-1G-2XS-PCIe;
*) dude - fixed The Dude compatibility with ARM64;
*) l2tp - improved service stability when disabling L2TP server with connected clients;
*) l3hw - fixed default route offloading for CRS305, CRS326-24G-2S+, CRS328, netPower, netFiber devices;
*) lte - enabled multi-APN and name re-use support for Chateau;
*) lte - improved stability when modem disappears during firmware upgrade;
*) ntp - improved source address usage for reply packets;
*) ospf - properly set VRF for gateway;
*) poe - fixed PoE driver loading on CRS354-48P-4S+2Q+;
*) route - allow OSPF and RIP redistributed routes to be matched by routing filters;
*) route - fixed “table” menu emptying after RouterOS upgrade;
*) switch - properly limit maximum number of switch rules to 256 on RB5009;
*) tr069-client - fixed RPC download of “3 Vendor Configuration File” with branding package;
*) x86 - fixed VLAN tagged packet transmit;
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
If you experience version related issues, then please send supout file from your router to support@mikrotik.com. File must be generated while router is not working as suspected or after some problem has appeared on device
Please keep this forum topic strictly related to this particular RouterOS release.
This happens every time so shortly after the release announcement. It probably is some caching/synchronization issue. Wait some time and it will be correct.
I agree partitioning is important when testing! Fortunately it works on my 4011 but I agree it should work on all devices with sufficient storage.
(I would even like to see it added to CHR)
Don’t we all. But I like this “release early and release frequently” way: much better than a giant beta each two months. Let’s hope they keep it this way from now on.
Agreed. Regular small updates means the community can immediately start testing fixes and features on a more granular level meaning a more constant and organised/consistent flow of feedback to support team and opportunity to fix bugs before next incremental version update.
Really excited to see The Dude support fixed for ARM64. This means RB5009 users can use Dude in their network for the first time ever on this device. Good job Mikrotik!!
Is RC the new Beta? I do not see that any beta has been posted for 7.2, but multiple RC. (6 so far)
7.1 was some inn between with 6 rc and 6 beta (Posted)
Of course I like it that fixes for problems that were blocking for some people are released in such an intermediate version. In fact I wish that v7 is made feature complete and reasonable stable ASAP so it can replace v6 in the field. This set of fixes at least concentrates on actual problems and not on new subsystems.
My only gripe is that BGP does not get enough love…
How come SUP-59224 has been closed while nothing as been done on that front?
Can we specify the direction of the Cake queue please so that we start testing and managing the bandwidth properly. I imagine we will find bugs so now should be the time to implement it no?
On the HAP-Lite (and HAP-Mini) it is best to install the 6.47.9 long-term version and not upgrade any further. Later versions include “fragattack fixes” that kill the performance.
