v7.1.4 and v7.1.5 is released!

RouterOS versions 7.1.4 and 7.1.5 has been released “v7 stable” channel!

Before an upgrade:

  1. Remember to make backup/export files before an upgrade and save them on another storage device;
  2. Make sure the device will not lose power during upgrade process;
  3. Device has enough free storage space for all RouterOS packages to be downloaded.

What’s new in 7.1.5 (2022-Mar-22 13:03):

*) route - fixed “table” menu emptying after RouterOS upgrade;

What’s new in 7.1.4 (2022-Mar-21 13:23):

*) bgp - fixed VPNv4 route sending to remote peer;
*) bridge - fixed destination NAT when using “use-ip-firewall” setting;
*) bridge - fixed filter rules when using interface lists;
*) bridge - fixed priority tagged frame forwarding when using “frame-types=admit-only-untagged-and-priority-tagged” setting;
*) capsman - improved stability when running background scan on CAP;
*) crs3xx - improved maximum allowed ACL rule calculation;
*) crs3xx - improved system stability when creating many ACL rules on CRS317, CRS309, CRS312, CRS326-24S+2Q+ and CRS354 devices;
*) l2tp - improved system stability when processing L2TP control messages;
*) lte - made “no” the default value for “use-network-apn” parameter;
*) lte - made “RG502QEAAAR11A06M4G” the last OTA firmware version update for Chateau 5G in RouterOS 7.1.x release tree;
*) ntp - improved source address usage for reply packets;
*) ospf - fixed default route origination when “default-originate=if-installed” “redistribute” is enabled;
*) ospf - fixed incorrect LSA types when changing area types;
*) ppp - added “comment” option for PPPoE servers;
*) queue - improved system stability when using more than 255 unique packet marks;
*) route - fixed ECMP load balancing in FastPath;
*) route - fixed route addition to VRF from BGP;
) route - fixed routing configuration export on SMIPS devices;
) route-filters - renamed "-set" to "
-list";
*) sfp - improved SFP module detection on CRS106 and CRS112;
*) switch - fixed port-isolation misconfiguration detection when using multiple switches;
*) traffic-flow - do not handle NAT events when “nat-events” is disabled;
*) ups - fixed UPS support;
*) winbox - added “VPN” tab to “Routing/BGP” menu;
*) winbox - added “VRF” parameter for “SSH” and “Telnet” menus;
*) winbox - do not show “Antenna Scan” button on devices that do not support it;
*) wireguard - allow same peer’s public key for different interfaces;
*) wireless - added “3gpp-info” parameter to interworking configuration;
*) wireless - added EAP-AKA to interworking’s realm configuration;
*) wireless - fixed interface initialization on Metal 2SHPn;

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.

Thanks, going to try it later today.

I have now 7.1.5 running on my 4011 and the route tables and all the lines that make use of the routes are still there. I am pleased that I can look into using the new features.

It was smooth sailing this updating. First make backup and an export with show-sensitive active, also download the new and the current version of RouterOS.

Thanks for making that possible on request by many, I assume.

:slight_smile:

RouterBOARD 750G r3, Update from v7.1.3 it break routing table, i dont know if bug or not all my routing table is gone, i restore the routing table with backup it seem okay now, still watching for any bugs

In my opinion, the current version of ROS 7 is designed only for arm devices and CPUs with four cores. When placed on an SXT 5HPnD with 400Mhz cpu, its processor often goes 100% down. I don’t know what has changed, but old antennas with low-power cpu start to hang even with ROS 6.x.x when exposed to a load (instead of being limited in load, the unit hangs).

Why is the below fix still not in stable release?

What’s new in 7.2rc2 (2022-Jan-28 11:00):

*) arm - fixed “shutdown” command on hAP ac^2;

break routing table
I am too

i have the same problem to 3 devices so it is a bug. I hope for a bugfix release soon

2x hap ac2, 1x hap AC3. No lose/break routing table issue at all.

2x WapAC ok, 1x RB3011 (no firmware update, still 7.1.1) ok

same here for a RB4011, update from 7.1.1

There’s a couple of fixes that suggest 7.2 is coming to stable soon, the biggest being:

*) lte - made “RG502QEAAAR11A06M4G” the last OTA firmware version update for Chateau 5G in RouterOS 7.1.x release tree;

That’s release tree, not stable tree, or stable branch.

Does anybody is already able to get advertised routes per BGP Peer on v7 stable?

On v7.1.4 release notes, those are the changes that are almost related to that:

But nothing explicit on advertised routes per peer.

A thread on this forum existis since 2021 November about this:
ROSv7 equivalent of /routing/bgp/advertisements print

@emils Is that on your radar?

This version make my hap ac3 bootloop

bad luck, both of my hap ac 3 are working on 7.1.4

Currently using v7.99 (internal test image) on RB5009, shall I upgrade? Random crashing issue was not fixed by the test image.

RB4011 upgraded from 7.13, all routing tables are missing.
Seems the only way is to add manually. (not tested backup/restore

@strods
http://forum.mikrotik.com/t/v7-2rc4-is-released/156082/1
“pe1chl, msatter, CTassisF, osc86, IntLDaniel, ivicask - Very sorry for missing routing configuration after an upgrade. We are working on a fix for this.”
You broke your promise :stuck_out_tongue:

This is also a big one for me. It would help get v7 into more widespread use for iBGP and eBGP - especially for peering and transit.

[quote=qntsystem post_id=920577 time=1647947973 user_id=70507]
When will Docker be supported again? T_T T_T T_T T_T
[/quote]

After they fix the bugs for RB5009 and Chateau owners who can only use RouterOS7 on their hardware.

OSPF stopped working - invalid area and invalid instance.

Fix was to change the Router ID in instance from “main” to the IP address of the router.