v7.2.2 [stable] and v7.2.3 [stable] are released!

Announcements
1

RouterOS version 7.2.3 has been released in “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.2.3 (2022-May-02 18:18):

*) system - fixed RouterOS bootup when wifiwave2 package is installed (introduced in v7.2.2);

What’s new in 7.2.2 (2022-Apr-28 21:01):

*) bgp - added initial support for prefix limit;
*) bgp - improved stability when editing BGP template;
*) bonding - fixed LACP flapping for RB5009 and CCR2004-16G-2S+ devices;
*) ccr - added visible “passthrough” flag for interfaces on CCR2004-1G-2XS-PCIe;
*) ccr - usability and stability improvements for passthrough interfaces on CCR2004-1G-2XS-PCIe;
*) cd-install - allow selecting on which drive to install RouterOS;
*) conntrack - limited full Connection Tracking warning to 1 message per minute;
*) crs3xx - fixed storm rate on 1Gbps interfaces for CRS354 devices;
*) defconf - suggest user to set up new password;
*) dhcpv4-server - fixed minor logging typo;
*) fetch - improved full disk detection;
*) filesystem - fixed possible boot failure on RB850Gx2 and RB1100AHx2;
*) filesystem - improved long-term filesystem stability and data integrity;
*) gps - fixed minor value unit typo;
*) ipv6 - removed bogus commands from IPv6 neighbors menu;
*) l3hw - improved offloading for directly connected hosts on CRS305, CRS326-24G-2S+, CRS328, CRS318, CRS310;
*) l3hw - improved route table offloading for CRS317, CRS309, CRS312, CRS326-24S+2Q+, CRS354, CRS5xx, CCR2x16 devices;
*) leds - fixed ethernet LED behavior on wAP R ac;
*) leds - fixed wireless related LED behavior with WW2 package;
*) lte - added SMS sending support for MBIM protocol;
*) lte - added support for generic PXA1802 based modems;
*) lte - disabled wait for LTE auto attach;
*) lte - hide slave interfaces from export;
*) lte - improved stability when upgrading LTE firmware on Chateau 5G;
*) mlag - fixed MAC address moving between bridge ports;
*) mpls - do MPLS forwarding for nexthops without mappings;
*) mpls - fixed MPLS MTU and path MTU selection;
*) mpls - fixed MPLS forwarding after any interface configuration parameter is changed;
*) ospf - fixed GRE interface compatibility with OSPF;
*) ospf - improved stability when enabling or removing interface-template entries;
*) ovpn - fixed memory leak on TILE architecture;
*) ovpn - fixed packet processing on MT7621A;
*) ovpn - improved Windows client disconnect procedure in UDP mode;
*) ovpn - improved service stability when processing frequent disconnects in UDP mode;
*) ovpn - improved stability when forwarding traffic on TILE;
*) ping - fixed socket allocation after VRF change;
*) ppp - fixed “remote-ipv6-prefix” parameter unsetting;
*) ppp - fixed active sessions sometimes getting stuck;
*) ppp - fixed issue with multiple active sessions when “only-one” is enabled;
*) queues - improved stability in large list of queue scenarios;
*) rb5009 - fixed 10G linking issues with Intel X520, XXV710 NICs;
*) route - fixed “table” menu emptying after RouterOS upgrade;
*) route - fixed static routes in VRF becoming invalid after reboot;
*) route-filter - fixed community matchers;
*) rsvp-te - improved stability when “Resv” received for non-existing session;
*) supout - added RIP section;
*) system - fixed IP service initialization in VRF after system startup;
*) system - fixed rare partial loss of RouterOS configuration after package upgrade/downgrade/install/uninstall;
*) torch - properly capture all related IPv6 traffic;
*) upnp - improved stability when processing incomplete HTTP header;
*) vpls - fixed “pw-l2mtu” parameter usage;
*) vrf - fixed VRF leaking;
*) winbox - do not show “unknown” area under “Routing/OSPF/LSA” menu;
*) winbox - do not show type value for NXDOMAIN entries under “IP/DNS/Cache” menu;
*) winbox - made “Interface Templates” table sortable under “Routing/OSPF” menu;
*) winbox - properly clean up SFP module information after it is unplugged;
*) winbox - properly clean up disk after a failed file upload;
*) winbox - show PVID column by default under “Bridge” menu;
*) wireless - fixed EAP-TLS authentication;
*) wireless - fixed GUD version in 3gpp information;
*) ww2 - fixed VLAN tag handling;
*) x86 - improved support for i40e driver;
*) x86 - improved support for Intel E810 NIC;

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.

v7.2.1 [stable] is released!
CRS328 does not boot 7.1b2?
Software life cycle and release management (re: auto upgrade)
v7.3 and v7.3.1 [stable] is released!
CHR upgrade peering issue after v.7.2.1
2

WARNING: Some users report unbootable devices after updating if wifiwave2 is installed

Thanks.

(@holvoetn It says this has been fixed on 7.3b37 and 7.2.2 should not be used if wifiwave2 is used)
What’s new in 7.3beta37 (2022-Apr-25 15:29):
*) system - fixed RouterOS bootup when wifiwave2 package is installed (introduced in v7.3beta34);

The Dude Server is now inside Extra packages for each supported platform.

Please!

Don’t start the usual mess like on all other topics.
Report only specific errors and open separate topics for each issue,
leave only here a brief description and the link to that topic.

3

Reboot hung on RB4011iGS+5HacQ2HnD after ROS Update from 7.2.1 to 7.2.2, but after hard poweroff the router came back with 7.2.2 installed (puhh…)
Updates on 5x CAP AC without issues, also on RB5009.

4

my audience with ww2 is bricked.
the update was pulled from the dl page since then.
patience is a virtue

5

crs305 and crs309 took very long time for reboot (minutes), but they came up eventually.

I’m still waiting for hap ac^3 to come back online; unfortunately, it is remote, so if it doesn’t come back up I will have to drive there :frowning:

For other devices (cap acs, sxts), I’m going to wait.

6

You have installed wifiwave2 on hAP ac³?

7

Yes

8

Does this have all the fixes from v7.3 beta 37?

9

Upgrade on Chateau LTE12 no issues.

10

Read and compare the changelogs.

11

[quote=marco44 post_id=930537 time=1651494924 user_id=169074]
Bricked another ac3 with wifiwave2
[/quote]

That issue was fixed with 7.3b37.

It should be mentioned this version 7.2.2 is not to be used for devices using ww2 !

This is NOT stable … my view.

12

[quote=holvoetn post_id=930540 time=1651495056 user_id=185526]
[quote=marco44 post_id=930537 time=1651494924 user_id=169074]
Bricked another ac3 with wifiwave2
[/quote]

That issue was fixed with 7.3b37.

It should be mentioned this version 7.2.2 is not to be used for devices using ww2 !

This is NOT stable … my view.
[/quote]

I am amazed that MikroTik promotes a version to “stable” with such an issue present, and without mentioning it in the release notes.

13

Must all of us compare the changelogs? It's a tedious process. I have the same question. Please can someone advise if it's worth upgrading to 7.2.2 from 7.3beta37. Due to the ww2 issue it seems 7.3beta37 is more up to date than 7.2.2 as it contains more fixes. It my assumption correct ?

14

Yes, because obviously on next beta version are present more experimental fix and functions

15

[quote=holvoetn post_id=930540 time=1651495056 user_id=185526]
[quote=marco44 post_id=930537 time=1651494924 user_id=169074]
Bricked another ac3 with wifiwave2
[/quote]

That issue was fixed with 7.3b37.

It should be mentioned this version 7.2.2 is not to be used for devices using ww2 !

This is NOT stable … my view.
[/quote]

bbbwuahhh…same here…coming from 7.2.1…WTF?

Using backup Routerboot does not work…trying netinstall now…have to find a pc with phys. ETH and a PSU first…gnnnhhh :-/

16

PIM-SM still broken.

17

Another great STABLE release from MT. Guys you should wake up and fire the person who is responsible for testing those stable builds. I have 2x hap AC3 and Im lucky I did not install this very stable biuld. The problem has been announced at 2:35 p.m. Im just curious how long MT will leave this build on their update servers and how many bricked wifiwave 2 devices they will need to react.

18

Yeah if the config-corruption-on-upgrade fix could make it to 7.2.2, why not include a similarly urgent/known fix that would literally prevent routers from being bricked on upgrade if they have wifiwave2 installed?Seems the best build right now is still 7.3beta37 despite being several days older

19

You mean fire the users??!? We are the BETA testers. It’s the only explanation ive heard that makes sense

20

Yeap, as I always read this forum before upgrade, this time I did not. My ac3 with ww2 is now bricked. Stable version, hahaha.