RouterOS version 7.1.1 has been released “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.1.1 (2021-Dec-21 13:53):
*) backup - added “force-v6-to-v7-configuration-upgrade” option on backup load to clear RouterOS v7 configuration and trigger reimport of RouterOS v6 route configuration (CLI only);
*) backup - fixed automatic backup generation when resetting configuration;
*) bgp - improvements on detecting peers local address when IPv6 link-local addresses are used;
*) capsman - improved system stability when processing CAP packet by Mangle;
*) dhcpv4-server - allow adding comments;
*) ethernet - improved system stability when receiving large packets on devices with 88F3720 CPU (nRAY, LHGG);
*) l3hw - fixed HW offloaded routing when using 7 or more VLAN interfaces;
*) l3hw - fixed bonding source MAC address;
*) l3hw - improved system stability when using 7 or more VLAN interfaces;
*) ntp - print log change time with time-zone applied;
*) ospf - fixed distance if “originate-default” is set to “always”;
*) ospf - fixed neighbor stuck in ExStart;
*) ospf - fixed simple authentication;
*) ospf - improved overall stability;
*) ospf - improves stability when handling looped back OSPF packets;
*) upgrade - improved 404 error handling when checking for new versions;
*) webfig - fixed user policy lookup for skin designer;
*) winbox - made “Routing Filters/Rules” table sortable;
*) winbox - moved “IP/Route/Nexthops” and “IPv6/Route/Nexthops” menus to “Routing/Nexthops”;
*) winbox - updated default “Routing/BGP/Peer Cache” table appearance;
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.
Updated CRS326-24S+2Q+, 2x CRS328-24P-4S+, RB4011iGS+5Hac, 2x CRS326-24G-2S+, 4xCAP AC, 1 CAP XL AC successfull to 7.1.1 (ROS and FW) without problems.
I´ll keep an eye on any ROS problems.
So far I’ve upgraded the CCR1009-7G, CCR1009-8G and a hEX S all in my lab - all OK.
However, I would make the observation that after the upgrade to 7.1, my devices were still set to the “testing” channel, so when I hit “Download and Install” they initially started downloading 7.2rc1. I stopped them in time and switched the release channel back to stable.
Perhaps after an upgrade to 7.x, the release channel should be set to automatically default to “stable”, to prevent inadvertent upgrades to release candidates?
I mean, ‘testing’ was an old way of upgrading from v6 to v7, now you need to use ‘upgrade’ channel. And there’s no ‘upgrade’ in v7, so looks like everything works just like russelld expects, except he upgraded to v7 quite long time ago
I see. 7.1.1 is available in “testing” channel from v6 as well. So I get what russelld is talking about, but to be fair, when you update to “testing” channel, you still agree to install other “testing” versions as well, which 7.2rc2 is.
