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

emils · Mon May 02, 2022 2:26 pm

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.

rextended · Mon May 02, 2022 2:48 pm

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.

Ullinator · Mon May 02, 2022 3:01 pm

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.

doneware · Mon May 02, 2022 3:07 pm

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

rextended · Mon May 02, 2022 3:17 pm

You have installed wifiwave2 on hAP ac³?

mafiosa · Mon May 02, 2022 3:30 pm

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

infabo · Mon May 02, 2022 3:31 pm

Upgrade on Chateau LTE12 no issues.

rextended · Mon May 02, 2022 3:32 pm

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

Read and compare the changelogs.

Mon May 02, 2022 3:37 pm

Bricked another ac3 with wifiwave2

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.

pe1chl · Mon May 02, 2022 3:58 pm

Bricked another ac3 with wifiwave2
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.

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

fragtion · Mon May 02, 2022 4:02 pm

Does this have all the fixes from v7.3 beta 37?
Read and compare the changelogs.

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 ?

rextended · Mon May 02, 2022 4:05 pm

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

Hominidae · Mon May 02, 2022 4:11 pm

Bricked another ac3 with wifiwave2
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.

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 :-/

Rfulton · Mon May 02, 2022 4:17 pm

PIM-SM still broken.

Rox169 · Mon May 02, 2022 4:33 pm

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.

fragtion · Mon May 02, 2022 4:36 pm

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

JJT211 · Mon May 02, 2022 4:37 pm

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.

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

RafGan · Mon May 02, 2022 4:43 pm

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

Mon May 02, 2022 4:53 pm

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

Netinstall using older version which worked before.
Or go immediately to 7.3b37.

Hominidae · Mon May 02, 2022 4:57 pm

...jep...and the hap-ac3 is now fully bricked, as netinstall (v7.2.1) does not seem to work either.
According to this: https://help.mikrotik.com/docs/display/ ... andJumpers the LED should go off when entering netinstall mode, but it never does go off....it starts flashing green, but then returns to solid blue.

.....anyone care to elborate on how to unbrick this unit?

Mon May 02, 2022 4:58 pm

...jep...and the hap-ac3 is now fully bricked, as netinstall (v7.2.1) does not seem to work either.
According to this: https://help.mikrotik.com/docs/display/ ... andJumpers the LED should go off when entering netinstall mode, but it never does go off....it starts flashing green, but then returns to solid blue.

.....anyone care to elborate on how to unbrick this unit?

Read one post above ...

My device was also bricked (bootloop), I was able to revert back to older version.
7.3b37 fixed the issue.

rextended · Mon May 02, 2022 5:02 pm

If netinstall work on your pc, push button before power up the device, keeping it pressed when power up until it DOES appear in netinstall.

(@holvoetn... thanks...)

Hominidae · Mon May 02, 2022 5:13 pm

...thats the problem...it never does appear in netinstall...

Mon May 02, 2022 5:16 pm

...thats the problem...it never does appear in netinstall...

It may require several attempts.

Windows computer ? Make sure ALL network interfaces are disabled except the one you want to use for netinstall.
I had more success using Linux box lately when battling this bootloop fun ... (almost first time right every time).

RafGan · Mon May 02, 2022 5:31 pm

Yeap, as I always read this forum before upgrade, this time I did not. My ac3 with ww2 is now bricked. Stable version, hahaha.
Netinstall using older version which worked before.
Or go immediately to 7.3b37.

Thank you for your answer, but I was made it many times from years.

mkx · Mon May 02, 2022 5:45 pm

...thats the problem...it never does appear in netinstall...

I fell into same pot hole on my audience. When trying to netinstall using 7.2.1 x64 windows, device never showed in the netinstall window. The funny thing is that wireshark did show TFTP traffic going on. So then I used netinstall 6.49.6 (the 32 bit windows) and device showed there. But couldn't make it install 7.2.1 (*). So I fired netinstall 7.2.1 again and there was device. Installation of 7.2.1 went smoothly afterwards.

(*) When trying to select packages to install, originally 7.2.2 system and wifiwave2 packages were selected. If I clicked "unselect" or if I clicked the check in front of system package, netinstall binary crashed. It turns out one has to unselect other packages first (in my case wifiwave2 7.2.2), only then select different version of system package.

....

Then I did some more experimenting ... I uninstalled wifiwave2 package, rebooted. Then uploaded system package version 7.2.2 and rebooted. Audience still working fine. Upgraded routerboot, rebooted .. audience still going strong. Uploaded wifiwave2 package, rebooted ... bootloop again. Back to netinstall, downgrade to 7.2.1. Wifiwave2 configuration partially lost ... which did not happen before on this device (I started with clean netinstall of 7.2rc4, then 7.2rc5, 7.2 and 7.2.1).

JJT211 · Mon May 02, 2022 6:07 pm

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

Netinstall possible or is it completely bricked? If so, thats fukt

EDIT: Looks like it is possible, just needs some perseverance

infabo · Mon May 02, 2022 6:11 pm

To sum it up: Seems like literally noone tested upgrading a device with wave2-extra-package installed before releasing a stable release.

verbovet · Mon May 02, 2022 6:28 pm

I have CCR1009-8G-1S-1S+ and Audience connected to it. Both had 7.2.1. I upgraded CCR to 7.2.2 (both packages and firmware). Everything looked OK, except that Audience was not able to connect to CCR, including I can't connect to Audience with winbox.

I switched to the long term channel and downgraded to 7.1.5 on both devices.

eddieb · Mon May 02, 2022 6:52 pm

RB1100 and RB2011 upgraded from 7.2.1 without problems

RafGan · Mon May 02, 2022 6:55 pm

Yeap, as I always read this forum before upgrade, this time I did not. My ac3 with ww2 is now bricked. Stable version, hahaha.
Netinstall possible or is it completely bricked? If so, thats fukt

EDIT: Looks like it is possible, just needs some perseverance

Netinstall to 7.3.b37, configuration restored from backup file and it works with ww2 :-)

jbl42 · Mon May 02, 2022 6:58 pm

What's new in 7.3beta37 (2022-Apr-25 15:29):
*) system - fixed RouterOS bootup when wifiwave2 package is installed (introduced in v7.3beta34);

And the same bug was also introduced in 7.2.2 "stable", which was released later than 7.3beta37...

Bugs introduced in v7.3beta34 also appear in 7.2.2 "stable"?
A "stable" version released after the beta version containing the fix does not contain the same fix?
A "stable" version is not booted at least once during MT internal testing on a box with wifiwave2?

Having developped SW myself for many years, I really wonder how MT manages to produce such blunders again and again.
Sorry MikroTik, but something with your SW dev and test processes is more than broken.

...thats the problem...it never does appear in netinstall...

In my experience, Netinstall often fails to detect devices after the ethernet link to the MT device goes down and up again while netinstall is running.
Either place a dumb switch between the PC and the MT box to netinstall, so the PC ethernet link stays up during reboot while entering Etherboot.
Or first put the MT box in Etherboot mode, wait for the link to come up and start Netinstall after the link is up.

With both approaches, devices show up in Netinstall almost immediatly. At least for me.

pcunite · Mon May 02, 2022 7:04 pm

Having developed SW myself for many years, I really wonder how MT manages to produce such blunders again and again.
Sorry MikroTik, but something with your SW dev and test processes is more than broken.

I have a software development background too. There is a lot to like about MikroTik. If we step back from the immediate issue (RoS v7 is public beta) we can see smart, helpful, and talented people following a broken process. This is a concern for management and I do wonder what is the incentive for them to change that process? What is happening makes them look juvenile and brand damaging.

pe1chl · Mon May 02, 2022 7:11 pm

What's new in 7.3beta37 (2022-Apr-25 15:29):
*) system - fixed RouterOS bootup when wifiwave2 package is installed (introduced in v7.3beta34);
And the same bug was also introduced in 7.2.2 "stable", which was released later than 7.3beta37...

Bugs introduced in v7.3beta34 also appear in 7.2.2 "stable"?

Well, of course there is always some "freeze" moment where code is no longer being ported into a "stable" version, and it may be before the release of the last beta.
But in case of such a blocking problem I would expect either a delay of the stable version, or a warning "do not upgrade to this version when you use wifiwave2".

herbrico · Mon May 02, 2022 7:20 pm

Hi to all. Upgraded RBD23UGS-5HPacD2HnD, RB1100AHx4DE, RBM33G, 2011UiAS-2HnD from 7.2.1 to 7.2.2 without problems.

cfikes · Mon May 02, 2022 7:31 pm

...thats the problem...it never does appear in netinstall...

I've never had NetInstall work on a Windows machine. Never had it fail on Linux.

Larsa · Mon May 02, 2022 7:50 pm

If we step back from the immediate issue (RoS v7 is public beta) we can see smart, helpful, and talented people following a broken process. This is a concern for management and I do wonder what is the incentive for them to change that process? What is happening makes them look juvenile and brand damaging.

Yeah, there is some room for improvement (diplomatically speaking) especially when it comes to stable releases. It's definitely a matter for the management team.

Znevna · Mon May 02, 2022 8:02 pm

@MikroTik: The offer to send me some devices to test every release on them before public posting still stands ^^

jbl42 · Mon May 02, 2022 8:03 pm

But in case of such a blocking problem I would expect either a delay of the stable version, or a warning "do not upgrade to this version when you use wifiwave2".

In the normal world yes. In the world of Mikrotik labels like "stable" and "RC" and are just randomly attached to versions and do not mean much.
So there is also no problem relasing "stable" version with known severe issues. Once you have lost your reputation, you can do as you please.

What bothers me more more is the stuff like the

"bgp - added initial support for prefix limit"

tragedy:
First they do not implement this crucial feature. Than MT offcials deny here in the forum it is required at all. Than it turns out they did not only not think about it, they also implemented BGP in a way making it hard for them to implement such a crucial feature.
This means BGP is designed and implemented by staff not having basic knowledge about real life application of BGP.

Bierkameel · Mon May 02, 2022 8:58 pm

RB5009 still reports "Warning: cpu not running at default frequency" within System>Routerboard.

hecatae · Mon May 02, 2022 9:00 pm

Upgrade on Chateau LTE12 no issues.

Thank you for confirming, but I will stay on the 7.3beta.

Dear Mikrotik Support, thank you, my Audience is now relegated to an access point due to repeat breakage of the wifiwave2 package in both 7.3beta34 and 7.2.2 stable because of lack of testing.

Mon May 02, 2022 10:00 pm

Everyone - We are very sorry for the issue with ww2 package. We are working on a fix for this problem and will publish it as soon as possible.
Rfulton - Have you opened a support ticket regarding this issue and provided supout files problem the problematic devices?

lvader · Mon May 02, 2022 10:09 pm

For l2tp issue in 7.2.x, I've noticed it also became broken, and after some investigation noticed that default ipsec policy got modified somehow.

So, if you have in your config after upgrade something like

/ip ipsec policy set 0 dst-address=2001:xxxx/128 src-address=2001:yyyy/128

reset it back to defaults:

/ip ipsec policy set 0 disabled=no dst-address=::/0 group=default proposal=default protocol=all src-address=::/0 template=yes

jbl42 · Mon May 02, 2022 10:44 pm

Hi strods

No issue, thanks for your hard work.
Normally I'm not the type getting grumpy in vendor forums. The reason I did tis time is the following:

*) leds - fixed wireless related LED behavior with WW2 package;
*) ww2 - fixed VLAN tag handling;

So those two ww2 related fixes were tested on 7.2.2 before release despite the fact 7.2.2 does not even boot with ww2 installed?
It's magic...

Rox169 · Mon May 02, 2022 10:45 pm

Once I tried to netinstall hAP AC3 and I had the same problem. I could not get hAP AC3 to flashing mode. Is there anyone who knows how long we should keep pressing reset?

Mon May 02, 2022 10:46 pm

Keep pressing until it shows up.
Can take some tries.

eworm · Mon May 02, 2022 10:48 pm

*) conntrack - limited full Connection Tracking warning to 1 message per minute;

Reading this... Can we have something similar for DNS, please? At least if DoH is enabled the DNS subsystem can flood the log extensively.

ZupoLlask · Tue May 03, 2022 12:00 am

*) conntrack - limited full Connection Tracking warning to 1 message per minute;
Reading this... Can we have something similar for DNS, please? At least if DoH is enabled the DNS subsystem can flood the log extensively.

+1

Hominidae · Tue May 03, 2022 12:44 am

So, I am the one who get bricked device (HAP ac3). Is it possible to bring it back to live? I've tried to download 7.3beta37 netinstall script and firmware, than connect lan1 port with Ethernet cable, on my PC I set 192.168.88.3 ip and default gateway (disabled systemd-networkd unit), started netinstall. Than, I hold reset button and plug the cable in device, it start flash pink, then blue, than flashing green, than constant green, and then blue again. I tried to hold 5, 10, 15, 20, 30 seconds, no result. The link shows as up on my Linux machine, but the netinstall still “Waiting for RouterBOARD...”.

I finally managed to get it working for mine.
Note, that netinstall 7.3beta37 did not work in Win(x64) and not in Linux as well...only netinstall.exe v6.49.6 (win) worked, but only after using a dumb switch in between PC and hap-ac3.
I tested in parallel with a wAP-ac (6.49.6), that actually showed the exact same netinstall behavior.

I am really anrgy, as it took me literally 5-6 hours to setup and test...even with linux and dump switch in between did not work with netinstall v7.3beta37.
As there was no netinstall-cli 6.49.6 for linux available in the MT archives, this was my last resort.
Only with this final setup netinstall for hap-ac3 and wAP-ac worked reliably/re-produce-able...

- set PC to IP 192.168.88.2/24
- enable netinstall and bootp server with IP 192.168.88.3 (different IP from PC)
- on hap-ac3 connect to LAN1, then press&hold reset before and after connecting power....keep holding reset until device shows up in netinstall-UI (approx 2-3secs after LED turns blue again)
- I then used v7.2.1-routeros + ww2 npk with netinstall and installed a backup config.

hope this helps someone....my lesson learned is I will move away from MT and as soon as TP-Link omada series offers a WiFI 6E solution, I will go there and never look back.

Thanks MT for nothing and all the fish.

rumahnetmks · Tue May 03, 2022 6:46 am

Argh the wiviwave2 package make my hAPAC3 bootloop forever...

Jotne · Tue May 03, 2022 8:19 am

I am really angry, as it took me literally 5-6 hours to setup and test...even with linux and dump switch in between did not work with netinstall

I do not see why all is upset. Yes, its not good that software do breaks the router.
Many users posts and ask for auto upgrade of routers, and this is why you do not.

1. Upgrade a router just minutes after a new release. Just stupid thing to do. Wait some weeks.
2. Did you do this on a production unit, again your fault. If you have a network of routers, always test on a same type of router with same config and see if all goes fine.
3. Last but not least, do READ this forum!!! It will save all of you for problems.

Not the first time I have written this, and I am not sure it will be the last.

Tue May 03, 2022 8:20 am

1. Upgrade a router just minutes after a new release. Just stupid thing to do. Wait some weeks.
2. Did you do this on a production unit, again your fault. If you have a network of routers, always test on a same type of router with same config and see if all goes fine.
3. Last but not least, do READ this forum!!! It will save all of you for problems.

Not the first time I have written this, and I am not sure it will be the last.

Put it in the signature part of your user account ;)

On a serious note, I fully agree with your statement. My devices are work and home related. I do take a risk testing on the home setup (mainly family wrath !!) but I will never adjust any of the work devices before I know for sure it works on my home stuff.

Jotne · Tue May 03, 2022 8:20 am

Argh the wiviwave2 package make my hAPAC3 bootloop forever...

Did you read this forum before upgrade?
Did you read the post above before you posted this post.
This is just repeating what is already known.

Jotne · Tue May 03, 2022 8:21 am

Put it in the signature part of your user account ;)

Does not help if owner of Mikrotik Routers does not bother to read the forum.

Rox169 · Tue May 03, 2022 8:42 am

Put it in the signature part of your user account ;)
Does not help if owner of Mikrotik Routers does not bother to read the forum.

If the upgrade is making from routers bricks Mikrotik should remove it ASAP. No one expect from stable version this bricking firmware....

gabacho4 · Tue May 03, 2022 8:51 am

If the upgrade is making from routers bricks Mikrotik should remove it ASAP. No one expect from stable version this bricking firmware....

It didn’t brick any of mine. Everything is relative and, as has been said before, rushing to install a new release means you assume risks. Before EVER installing an update, I check out the forum. Once I determine that the issue doesn’t affect me (2xRB5009 and HeX) I update.

Tue May 03, 2022 8:53 am

If the upgrade is making from routers bricks Mikrotik should remove it ASAP. No one expect from stable version this bricking firmware....

I'm not saying the problems could not have been avoided and this particular one is a real goof-up (since the fix WAS available already in 7.3b37) but ... there is a small company in Redmond also known for releasing (sometimes CRITICAL) hotfixes each time they release a new major version.
It's called ... Microsoft.
On my personal laptop, I never upgrade until at least a month when a new major release is available.

If the device you use is production material, test before upgrading. Especially the parts which you deem critical for you to function.
That is the ONLY way of avoiding such problems.
If you can not do this, don't upgrade before others have cleared the rubble.

Rox169 · Tue May 03, 2022 9:01 am

Its very sily to say that I have to read forum before upgrade to stable version...when is new firmware distributed by official upgrade from HAP AC3, the firmware must be checked for this device. How anyone could explain how Mikrotik is testing new stable version when it bricks all HAP AC3?????

Hominidae · Tue May 03, 2022 9:11 am

I am really angry, as it took me literally 5-6 hours to setup and test...even with linux and dump switch in between did not work with netinstall
I do not see why all is upset. Yes, its not good that software do breaks the router.

I am not upset that the update did break the router....my decision, my fault.
I am upset about the clumsy, unreliable netinstall method, as this is what consumed my time.
The unit was fully prepared before the update, including backup firmware on 7.2.1 which is proved to run fine with the unit....but which did not work...what is the use of having that, if the procedure involving a simple button-press does not work?

Then, with netinstall, I tried all - in parallel with a wAP-ac (on 6.49.6), to rule out the PC as a cause for unsuccessful netinstall events - available, downloadable options.
Did not work for Windows and not for Linux, with netinstall 7.2.1 and 7.3beta37 - with and without a dumb switch in between...but - fortunately - with netinstall 6.49.6 for win (where the linux netinstall-cli of that version was nowhere to be found anymore).

To me it seems, that MT is not capable to handle the complexity of their own inventions.
Simply put....when there is a reset button with a backup firmware in the device, I expect it to work...flawlessly....nothing more or less.

Being as it is, I am not willing to invest any more time in that procedure - or taking the risk of non-functionality thereof....and that's why I am leaving.

h17 · Tue May 03, 2022 9:22 am

Strange behaviour on RB5009 after upgrading to 7.2.2.
My uplink (ether8) wouldn't work. No ping to gateway, torch was showing kinda normal traffic, but all routing related to ether8 went red.
Port status was UP.

Sorry for not having more time for investigation, but I'm on home office and I needed to downgrade to 7.2.1 asap.
On 7.2.1 with 7.2.2 bootloader I think it was also red and non functional. After downgrading bootloader I can work again.

P.S.
Good I've read this forum before attempt to brick my ac3+ww2. Thx guys. :)

dioeyandika · Tue May 03, 2022 9:42 am

RouterBOARD 750G r3 upgrade went smootly but something weird hapen too me, i have routing rules, it have right route if i traceroute from mikrotik, but on windows and other client the route become mest up, yeah i have mangle routing rule, usualy i override with routing rule i add, but on this version it cant work, i downgrade back to ROS 7.2.1 (stable) and all routing rule work again

Jotne · Tue May 03, 2022 9:58 am

Its very sily to say that I have to read forum before upgrade to stable version...when is new firmware distributed by official upgrade from HAP AC3, the firmware must be checked for this device. How anyone could explain how Mikrotik is testing new stable version when it bricks all HAP AC3?????

Its not silly. After working with Mikrotik for many years, I have seen this several times before.
MT are not the only one with this problem (Have seen several Cisco devices and other breaks as well).
But since RouterOS is a very complex software with very many function (lot more than most other vendors I have used), there will be situation where some combination has not been tested.

Rox169 · Tue May 03, 2022 10:03 am

Why they at least do not try to install the new firmware?????????????The HAP AC3 is the newest router from them and they not even bother to try install stable firmware??????

Jotne · Tue May 03, 2022 10:08 am

You also need WifiWave 2 packets for it briks.

rextended · Tue May 03, 2022 10:21 am

message for some users:

It is completely and perfectly useless to complain like this, when you are the first to do nothing perfect, and never will.
As long as the software is made by humans, there will always be errors.
However, there remains the utter idiocy in updating something "vital" as soon as an update comes out.
If for some reason you don't have another device to test before updating yours,
just go to the forum and wait for the comments, it doesn't take an engineering degree to figure it out.
If you have the craving for instant updates you will not be "screwed" only with MikroTik...
In fact, I've always said that those who launch automatic updates with scripts, as soon as the update comes out, don't have "common sense"...
In summary, with MikroTik it is like that, like with other thousands of companies as well.
Go spend thousands of dollars more on other companies that seem more stable, and you solve...

Znevna · Tue May 03, 2022 10:24 am

Bad words coming from a forum moderator..
Moderate yourself.
Updating to a Testing/Development release, sure, it would require extra testing first.
Updating to "Stable" shouldn't crash devices. Period.
I can provide the post address to receive those testing devices for testing the software before public release.
Me moving to Latvia is out of the question.

rextended · Tue May 03, 2022 10:26 am

I am not a MikroTik employee and i have expressed my opinion, like @Jotne and the others.

Znevna · Tue May 03, 2022 10:29 am

No, you've called some users idiots. That's just bad.
In this case idiots = users that updated to the latest stable v7.
Users that are owners of the few rare devices that are able to run wifiwave2 package.

Rox169 · Tue May 03, 2022 10:34 am

You also need WifiWave 2 packets for it briks.

tell me who is using HAP AC3 without WifiWave 2 ?????

rextended · Tue May 03, 2022 10:36 am

No, you've called some users idiots. That's just bad.
In this case idiots = users that updated to the latest stable v7.

I do not think all users have launched the update with automatic scripts than just upgrade the device when the update is just publishied... or not?

woland · Tue May 03, 2022 10:38 am

Its very sily to say that I have to read forum before upgrade to stable version...when is new firmware distributed by official upgrade from HAP AC3, the firmware must be checked for this device. How anyone could explain how Mikrotik is testing new stable version when it bricks all HAP AC3?????
Its not silly. After working with Mikrotik for many years, I have seen this several times before.
MT are not the only one with this problem (Have seen several Cisco devices and other breaks as well).
But since RouterOS is a very complex software with very many function (lot more than most other vendors I have used), there will be situation where some combination has not been tested.

I agree to Jotne: please, if you don´t have the time for recovery or if you have a critical system (this definitly includes your home router) never ever upgrade immediately after a release.
The upgrade procedure looked mostly like this for me for the expensive vendors I was working with:
1./read and understand the release notes
2./ask your colleagues, friends and your trusted expert, what they are thinking
3./play in your lab > unfortunately this was not always possible, but it is always advisable
4./plan and inform + spend a few hours in meetings discussing details
5./make backups, prepare everything into the smallest detail
6./do it (mostly this is the shortest and easiest step)
7./check and ask your colleagues and stay on standby
8./find some horrible error and either roll back or stay up until 6a.m. with the expert fromt the vendor on the phone trying to fix the issue

:) This step 8. happened more often then I would have wished for.

Still MT should not have communicated ROS 7.x is ready for production ...

W

Tue May 03, 2022 10:41 am

tell me who is using HAP AC3 without WifiWave 2 ?????

Using wifiwave2 requires ROS7, most hAP AC3 might still be on 6.
So I dare to say majority of users are still not using it...

Znevna · Tue May 03, 2022 10:44 am

No, you've called some users idiots. That's just bad.
In this case idiots = users that updated to the latest stable v7.
I do not think all users have launched the update with automatic scripts than just upgrade the device when the update is just publishied... or not?

Updating via script or updating via a manual check makes no difference here.
You see some change that you were expecting in the changelog, you update.
It bricks your device, go to recovery steps => do it again, maybe something else was broken, brick again, give up, downgrade.. bad experience.
It was said many times before, bad releases should be pulled to minimize bad user experience, but they never get pulled, hoping that ALL THE OWNERS are reading the forum
Well, they don't. Maybe after they get mad enough about the update and they start looking for explanations on why the latest stable isn't stable.
.......See where I'm going with this?
@holvoetn: I'm confident that almost everyone that bought hAP ac3 bought it because they can run wifiwave2 on it.
But you're not wrong either, most would still have v6 on it, or v7 without wifiwave2.

rextended · Tue May 03, 2022 10:48 am

@Znevna, if you think I offended you, my apologize, really, sorry...
But I hope you understand my position as user like other ISP.

rextended · Tue May 03, 2022 10:51 am

To everyone:

Your position is clearly understood,
you are angry, dissatisfied or disappointed.
Ok, it is understood.
The MirkTik staff has already officially apologized.
Continue to fill this topic with only complaints,
it does not help those who might want to use this topic for its purpose:
to report a problem not yet reported.
With all this confusion, the MikroTik staff may not notice other important bug reports.

Rox169 · Tue May 03, 2022 10:54 am

Guys thank you for your advices but it would be much easier if Mikrotik did their job. Here you can see, they not even tried to install this STABLE build on their newest router and just roll out the firmaware, so we can imagine how they test old devices. They just release stable version without any testing and wait until sili user install it on their HW. But the worst is that the firmware is still available thorough their update. The HAP AC3 is stil showing the update to 7.2.2.

Znevna · Tue May 03, 2022 10:55 am

ISPs are a different story here, because you're an ISP it doesn't mean all MikroTik users are, ISPs wouldn't have any need for wifiwave2. It doesn't work with CAPsMAN etc.
The ones getting hurt are the ones that gave MikroTik a chance to have a decent wireless performance with the wifiwave2 package, those are normal home users or users that run a device here and there without CAPsMAN.
Users that didn't wanna run a MikroTik router + some TP-Link/other brand AP that delivered better wifi than mikrotik had at the time.
Users that are now happy that MikroTik has some devices that can run wifiwave2 and are able to run RouterOS on the same device too, you know, average Joe that wants an all-in-one device.
Those users were left with bricks.
</drama>
Oh yeah, and v7 netinstall is flaky, I didn't have time to investigate what's broken in it since I don't have spare devices for tests, v6 worked fine. I wrote about it in other topics too.
Here:
viewtopic.php?p=878890#p878890
viewtopic.php?p=878899#p878899
viewtopic.php?p=890726#p890726

For some reason netinstall v7 was always flaky, the device boots, does the tftp transfer but it doesn't show up in netinstall, you have to close netinstall after tftp transfer finishes and reopen netinstall, then the device shows up and you can hit install on it. Smells like a bug.

The tftp transfer can be checked with Wireshark or other similar tool.
Cheers!

Hominidae · Tue May 03, 2022 11:00 am

If you have the craving for instant updates you will not be "screwed" only with MikroTik...

....I am saying this again.....
I am not blaming MT for broken features of ROS itself or for a broken release and myself testing it (early).
I am blaming MT for breaking BOTH levels of recovery methods that I expect to be woven-in and hardened in a hardware device (and are advertised, hence myself buying them for a reason).

Using the reset-button procedure to recover a perfectly fit for use backup firmware DID NOT WORK (it did with my wAP-ac, I tested in parallel, which still has v6 as backup firmware).
Recovery this way is/should be like 5-15mins work.
Instead LED feedback would indicate false positives, leading to many, many unsuccessful attempts (and HW Documentation of how LEDs should behave is false as well, for the hap-ac3)

Using netinstall was not possible for the two recent/available netinstall version of v7 AND only the win version of previous netinstall versions is stored in the software archives, no version of linux netinstall-cli (and we all know - and as stated by many others - that win is not a reliable platform to do these things).
Recovery like this should - with a spare PC (which nedds an ETH NIC, many laptops don't have that any more) in your closet - as well take approx 15-30mins (including gathering your gear).
Instead it was trial and error, with even more unsuccessful attempts

...my 2 cents.

andacb · Tue May 03, 2022 11:00 am

No problems or issues on upgrade from 7.2.1 to 7.2.2 for the following devices/platforms:

- RB4011iGS+
- RB3011UiAS
- CRS125-24G-1S
- RB850Gx2
- RBSXTR
- RBwAPG-5HacT2HnD
- CHR X86
- Dude Server

However, Dude server still shows "needed packages are not available" for the upgrade tries within.

audaihss · Tue May 03, 2022 11:18 am

Hello .... The problem of rebooting the LHG XL 52 ac has not been resolved since version 7.2 The device starts auto restart minutes after the update .. The device works satisfactorily on version 7.1.5 and below

pe1chl · Tue May 03, 2022 11:36 am

Using the reset-button procedure to recover a perfectly fit for use backup firmware DID NOT WORK (it did with my wAP-ac, I tested in parallel, which still has v6 as backup firmware).

I think you have misunderstood this feature. Which is not surprising.
"firmware" of a MikroTik router is not the RouterOS. It is just the bootloader (BIOS) of the hardware.
The "reset button procedure" switches you back to the backup bootloader, which handles the problem of "power lost during netinstall" etc.
This has nothing to do with botched RouterOS upgrades, as both the backup firmware and current firmware will still boot the same RouterOS.

When you want to fall back to a previous RouterOS install, you need to use "partitioning". That is only possible on the older models and the more higher-end models of today, e.g. the RB4011.
Then you can divide the flash memory in two partitions and keep two copies of RouterOS.
When one version fails to boot completely, it will automatically switch to the other version, no reset button magic required.
When it boots successfully as far as RouterOS itselfs views the situation, but you still want to enforce a switchover, you can powercycle the device halfway through the boot sequence.

The latter is also a point of attention: when your power drops, comes back for like 20 seconds and then drops again, to come back later, you need to verify that the router did not inadvertently fall back to a previous RouterOS version.

evbocharov · Tue May 03, 2022 11:38 am

Hello. When add a wave2 on hap ac3 lte?
Thank you.

Znevna · Tue May 03, 2022 11:39 am

Never. 16MB of storage is too little.

pe1chl · Tue May 03, 2022 11:40 am

Everyone - We are very sorry for the issue with ww2 package. We are working on a fix for this problem and will publish it as soon as possible.

Why did you not put a remark in the changelog to notify new users trying the upgrade of this already known problem?
(not only in the changelog shown in the first posting, but also in the one shown to users when they check if a new version is available)

That would be so much more helpful than apologizing afterwards to users who bricked their router...

Znevna · Tue May 03, 2022 11:43 am

They were not aware of what broke the wifiwave2?. beta37 changelog blames beta34 yet the bug was introduced in beta33 it seems.

hecatae · Tue May 03, 2022 11:53 am

Guys thank you for your advices but it would be much easier if Mikrotik did their job. Here you can see, they not even tried to install this STABLE build on their newest router and just roll out the firmaware, so we can imagine how they test old devices. They just release stable version without any testing and wait until sili user install it on their HW. But the worst is that the firmware is still available thorough their update. The HAP AC3 is stil showing the update to 7.2.2.

Agreed, if you use the Mikrotik Pro Android or iOS App, it just states new version available and offers to update now, no changelog, no warning that you could potential end up having to netinstall to bring your device back to active service.

infabo · Tue May 03, 2022 12:17 pm

Patch management can get quite fragile over time as testing/stable/development diverge....

Rox169 · Tue May 03, 2022 1:35 pm

No they just do not care....after one day of knowing this bricking issue the update is still available on the HAP AC3....

msatter · Tue May 03, 2022 1:57 pm

I don't install any new version after first others having a go at it. If more first keep an eye on the comments for a time before taking the step and upgrade then a lot of nasty expierences would be avoided.

Atleast Mikrotik did not release just before the weekend and that is already a possitive.

Paternot · Tue May 03, 2022 2:53 pm

Is the WiFi2 package considered production ready? I was under the impression that it were in the development stage. No, I don't have WiFi2 devices, so I'm not keeping up with this.

rextended · Tue May 03, 2022 2:58 pm

Have at least read some previous post?

Rox169 · Tue May 03, 2022 3:00 pm

7.2.3 is releasing right now, who is going to risk it? :) Did they try to at least install it this time?

emils · Tue May 03, 2022 3:10 pm

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);

emils · Tue May 03, 2022 3:15 pm

Unfortunately, to recover the device, you need to reinstall the device using Netinstall utility.
https://help.mikrotik.com/docs/display/ROS/Netinstall

Tue May 03, 2022 3:25 pm

Please, make sure you are using v7.x netinstall, that there is no other active network interfaces on your devices, and IP address configured on Ethernet card and Netinstall are from the same subnet.
Are you able to reinstall any other device?

w0lt · Tue May 03, 2022 3:30 pm

Please, make sure you are using v7.x netinstall, that there is no other active network interfaces on your devices, and IP address configured on Ethernet card and Netinstall are from the same subnet.
Are you able to reinstall any other device?

Could MikroTik please work on a version of NetInstall that runs native on Mac OSX ? 🥺

-tp

Tue May 03, 2022 3:33 pm

Netinstall works on macos with virtualization and little manual configuration.

hecatae · Tue May 03, 2022 3:34 pm

Is the WiFi2 package considered production ready? I was under the impression that it were in the development stage. No, I don't have WiFi2 devices, so I'm not keeping up with this.

There's no mention on the wiki of it not being Production Ready: https://help.mikrotik.com/docs/display/ROS/WifiWave2
And it's being produced as a Stable package, so if it was not production ready, I'd assume it would only be available for the testing branch?

pe1chl · Tue May 03, 2022 3:57 pm

Unfortunately, to recover the device, you need to reinstall the device using Netinstall utility.
https://help.mikrotik.com/docs/display/ROS/Netinstall
This is exactly what i am doing for last 3 hours. Please, check this post viewtopic.php?t=185628#p930821

Netinstall (on all systems) has problems with systems that have more than one LAN interface. I could not get it to work on my Linux system either.
It has an onboard LAN port that I have connected to a trace port on the switch, and a plugin ethernet card I use in normal operation.
There is no way to tell netinstall it has to use the second LAN card, so it fails in a way like you showed.
Fortunately I have an ancient laptop with Windows XP and a single LAN card, no WiFi, so it is "easy" to do netinstall using that.
But really, netinstall has to be made more flexible and more userfriendly. Usually once people have bricked their device and are forced to make netinstall work, they run into trouble.
People with experience (like the MikroTik employees) can make it work because they know what to do and not to do.

Rox169 · Tue May 03, 2022 4:23 pm

Has already any hero tried to install 7.2.3 on HAP AC3 with wifiwave 2?

Tue May 03, 2022 4:24 pm

I have tried it yesterday

, and it worked fine for me.

anav · Tue May 03, 2022 4:32 pm

on my main home router I am still using vers 6.48 long term firmware.
I cannot imagine anyone in a business using anything less than long term, which to means, proven over time to be stable.
I do it because my family are the most important clients of all.

IntLDaniel · Tue May 03, 2022 4:34 pm

Just give a try to update 750G r3 mmips from 7.2.1 to 7.2.3 (create backop before the upgrade)...after that I cannot access my router from several LAN connectors, cannot even ping the router from some lan, while the PC gets IP from the router DHCP on that lan. So tried
* restore saved configuration before the upgrade - not help
* reset router to defaults on 7.2.3 and resore saved config - not help
* then downgraded to 7.2.1 (config was probably corrupted at all by that..no accees to router from any LAN connector)
* so again reset to defaults on 7.2.1 and restore saved config - everything works like before!

so for me - keep away from v7.2.3 as well :-(

Unintentional · Tue May 03, 2022 4:35 pm

Has already any hero tried to install 7.2.3 on HAP AC3 with wifiwave 2?

Yep, working fine on Audience.

Hominidae · Tue May 03, 2022 4:35 pm

Using the reset-button procedure to recover a perfectly fit for use backup firmware DID NOT WORK (it did with my wAP-ac, I tested in parallel, which still has v6 as backup firmware).
I think you have misunderstood this feature. Which is not surprising.
"firmware" of a MikroTik router is not the RouterOS. It is just the bootloader (BIOS) of the hardware.
The "reset button procedure" switches you back to the backup bootloader, which handles the problem of "power lost during netinstall" etc.
This has nothing to do with botched RouterOS upgrades, as both the backup firmware and current firmware will still boot the same RouterOS.

...ugh...OK, thank you very much for clarifying things (why the hell is the numbering scheme of OS and firmware the same).

Nevertheless...

Please, make sure you are using v7.x netinstall, that there is no other active network interfaces on your devices, and IP address configured on Ethernet card and Netinstall are from the same subnet.

THIS is exactly what did NOT work for me...only - and I tried several combinations of OS and with/without dump switch in the middle - netinstall v6.49.6 worked reliably/reproducable (with a switch in middle).

Unfortunately, to recover the device, you need to reinstall the device using Netinstall utility.
https://help.mikrotik.com/docs/display/ROS/Netinstall
This is exactly what i am doing for last 3 hours. Please, check this post viewtopic.php?t=185628#p930821

see this: viewtopic.php?t=185628#p930699 ...I was only successful with a dump switch in the middle (and using v6,49.6 of netinstall)
What all recent OS (Win + Linux) will do is, that when the ETH link is not physically up and running, it will simply disable that logical IP connection and netinstall will not listen to that connection/port, hence.
I noticed the port on the PC flap, when the hap-ac3 boots...with a switch in the middle, the PC port will stay up, regardless of the state of the link to the MT device.

Tue May 03, 2022 4:36 pm

Just give a try to update 750G r3 mmips from 7.2.1 to 7.2.3 (create backop before the upgrade)...after I cannot access my router from several LAN connectors, cannot even ping the router form some lan, while the PC gets IP from the router DHCP on that lan. So tried
* restore saved configuration before the upgrade - not help
* reset router to defaults on 7.2.3 and resore saved config - not help
* then downgraded do 7.2.1 (config was probably corrupted at all by that..no accees to router from any LAN connector)
* so again reset to defaults on 7.2.1 and restore saved config - everything works like before!

so for me - keep away from v7.2.3 as well

Please send support output file from your router with the configuration, that was upgraded to 7.2.3.

IntLDaniel · Tue May 03, 2022 4:40 pm

Just give a try to update 750G r3 mmips from 7.2.1 to 7.2.3 (create backop before the upgrade)...after I cannot access my router from several LAN connectors, cannot even ping the router form some lan, while the PC gets IP from the router DHCP on that lan. So tried
* restore saved configuration before the upgrade - not help
* reset router to defaults on 7.2.3 and resore saved config - not help
* then downgraded do 7.2.1 (config was probably corrupted at all by that..no accees to router from any LAN connector)
* so again reset to defaults on 7.2.1 and restore saved config - everything works like before!

so for me - keep away from v7.2.3 as well :-(
Please send support output file from your router with the configuration, that was upgraded to 7.2.3.

Sorry, I am back on 7.2.1 in working state now, router is in production. I cannot afford to do all steps again now. What I can do is to send you current working config on 7.2.1 you you can try it by yourself?
Edit: For me it sounds like some firewall rules was not applied OR routing tables problem (?) because I was not able access from one LAN to other LAN segment. But keep in mind that "the backup config" is working on 7.2.1 while the same one NOT on v7.2.3.

Znevna · Tue May 03, 2022 4:44 pm

@Hominidae: Can you try what I wrote here? viewtopic.php?p=890726#p890726 (the 2nd half of that post)
Follow the netinstall procedure, and when the device is supposed to show up but it doesn't (after the initial tftp transfer which you can check with wireshark) close netinstall and start it again.
This way it "worked" for me.

pe1chl · Tue May 03, 2022 5:19 pm

Yes, as I wrote before, it requires some experience and this is usually what people who suddenly are faced with the problem do not have.
Also, it requires a machine with a single network interface or luck that it works on the interface you are using, as netinstall lacks an interface selection list.

Znevna · Tue May 03, 2022 5:42 pm

Having more than one interface shouldn't be a problem on Windows, you can disable the ones you don't need before attempting a netinstall.
It's not rocket science, that part.

Tue May 03, 2022 5:46 pm

Having more than one interface shouldn't be a problem on Windows, you can disable the ones you don't need before attempting a netinstall.
It's not rocket science, that part.

It isn't but it is crucial for success.

rextended · Tue May 03, 2022 5:46 pm

Having more than one interface shouldn't be IS a problem on Windows

you can disable the ones you don't need -> you must disable all the others (bluetooth and wireless included)

Netinstall / Windows is able to use only one interface at time with Layer2 / MAC.
Also Bluetoot create virtual LAN interface.
Usually the interface usable with Layer2 / MAC is the first interface loaded.
Disabling all the other interfaces, move, in the remaining active interface, the ability to directly use, on Netinstall / Windows, the Layer2 / MAC for BootP protocol.
Reactivating later the interface, do not move on what interface is possible to use Layer2 / MAC.
This makes me think that it is clearly a Windows problem that they have introduced since Windows 8

pe1chl · Tue May 03, 2022 6:01 pm

Having more than one interface shouldn't be a problem on Windows, you can disable the ones you don't need before attempting a netinstall.
It's not rocket science, that part.
It isn't but it is crucial for success.

And it is ridiculous. When you are trying to revive your bricked router, the last thing you want is modifying the config of your still working PC.
(it is already bad enough that you need to change the IP address configuration instead of having netinstall add and remove the required static address)
Netinstall should get an interface selection list where you see the interfaces present in your system and select the one you are using.

rextended · Tue May 03, 2022 6:08 pm

@pe1chl is the same also for other vendor$ product$...
Some still require the ultra-obsolete Java Platform Runtime Environment...
And about promises from "450" produc line.... after 40 clients start to have same MikroTik problems...

Tue May 03, 2022 6:12 pm

And it is ridiculous. When you are trying to revive your bricked router, the last thing you want is modifying the config of your still working PC.
(it is already bad enough that you need to change the IP address configuration instead of having netinstall add and remove the required static address)
Netinstall should get an interface selection list where you see the interfaces present in your system and select the one you are using.

I hear you and while I fully agree, it is what it currently is until they change it.
You need to disable all network interfaces expect the one being needed, on Windows.

On Linux not so. I have an old laptop with ethernet and wifi. Last weeks I had "the pleasure" of using it for recovery a couple of times using netinstall.
Didn't have to disable the wifi interface there. It just worked.

PS try to recover a Symbol 7532 AP. You need a bloody serial/usb convertor to get in !
Serial RS232 in 2022 ...

Znevna · Tue May 03, 2022 6:42 pm

[...] the last thing you want is modifying the config of your still working PC [...]

LOL, yeah, it's like doing brain surgery.
win+r, ncpa.cpl, select, right click, disable, select, right click, disable.
b r a i n s u r g e r y
PS: ncpa.cpl still works in Windows 11, for how long, we don't know: https://winaero.com/microsoft-restored- ... indows-11/

Hominidae · Tue May 03, 2022 6:47 pm

@Hominidae: Can you try what I wrote here? viewtopic.php?p=890726#p890726 (the 2nd half of that post)
Follow the netinstall procedure, and when the device is supposed to show up but it doesn't (after the initial tftp transfer which you can check with wireshark) close netinstall and start it again.
This way it "worked" for me.

No, I cannot atm.
But what you describe is another view of what I stated here:

What all recent OS (Win + Linux) will do is, that when the ETH link is not physically up and running, it will simply disable that logical IP connection and netinstall will not listen to that connection/port, hence.
I noticed the port on the PC flap, when the hap-ac3 boots...with a switch in the middle, the PC port will stay up, regardless of the state of the link to the MT device.

It comes down to having a stable IP including interface on the PC...or rather find the point in time when this is the case.
Either by examining traffik or simply force a stable connection (and IP for netinstall to lock-in) with a switch in the middle.
Both win10, win11 and recent linux (tried fedora WS-35 and Debian 10.5) will disable the port (and IP, even it is manually configured) when the physical link is not up.
In the good old days, this wasn't the case...damn environmental friendly solutions ;-)

Larsa · Tue May 03, 2022 6:52 pm

Question: there is probably something I have missed, but can someone who has a little more insight into the release process please explain to me the main reason why a faulty version like 7.2.2 in the "stable" channel wasn't pulled back and deleted immediately when the issue was discovered?

Especially now when there is a working replacement version 7.2.3 and everything was happening during the same day as the release process. I know MT are doing the best they can but one might wonder if there even exist a working rollback plan for situations like this (sorry but I couldn't resist ;- )

pe1chl · Tue May 03, 2022 6:53 pm

I hear you and while I fully agree, it is what it currently is until they change it.
You need to disable all network interfaces expect the one being needed, on Windows.

On Linux not so. I have an old laptop with ethernet and wifi. Last weeks I had "the pleasure" of using it for recovery a couple of times using netinstall.
Didn't have to disable the wifi interface there. It just worked

Yes, but there you just were lucky because your ethernet appears in the interface list before the wifi. As I explained above, with two ethernet it does not work on Linux and you have to plug the cable in "the right port" and know or experiment which one that is. In the old days probably the one that shows up as eth0, but in the current mess caused by mr. Poettering you cannot know which one is the first from looking at the silly "predictable names".

pe1chl · Tue May 03, 2022 6:56 pm

It comes down to having a stable IP including interface on the PC...or rather find the point in time when this is the case.
Either by examining traffik or simply force a stable connection (and IP for netinstall to lock-in) with a switch in the middle.

I remember some time in the past I have succeeded in netinstall only after putting a small dumb desktop switch between the laptop and the device.
But I do not know if that was really necessary or because of my own limited experience. Indeed it is as you described: the interface goes down and it takes 5-10 seconds to come back up and that is too long for some of the methods to start the netinstall.

Larsa · Tue May 03, 2022 7:00 pm

Yeah and regarding recovery, it would be really nice if MT could produce some detailed and working "best practices" for "Netinstall" that is really needed when things fricks up badly...

pe1chl · Tue May 03, 2022 7:04 pm

Yeah and regarding recovery, it would be really nice if MT could produce some detailed and working "best practices" for "Netinstall" that is really needed when things fricks up badly...

https://help.mikrotik.com/docs/display/ROS/Netinstall
https://help.mikrotik.com/docs/pages/vi ... Id=1409054

rextended · Tue May 03, 2022 7:12 pm

Enable NetBIOS over TCP/IP.
Very important, I always forget to suggest it, to activate it instead of leaving it automatic or disabled...

Larsa · Tue May 03, 2022 7:13 pm

Yeah and regarding recovery, it would be really nice if MT could produce some detailed and working "best practices" for "Netinstall" that is really needed when things fricks up badly...
https://help.mikrotik.com/docs/display/ROS/Netinstall
https://help.mikrotik.com/docs/pages/vi ... Id=1409054

Well, there is "basic" instructions and there is "the realty" with all the weird issues and not to speak of the different platforms. That's why there is room for improvements as in "best practice" (ie specification by example) like for example the setting for "NetBIOS" that should be a part of the standard use as Rextended mentioned

I would advise MT to update and fix the installation of Netinstall to automate as many settings as possible. When things go wrong, recovery tools should be helpful as quickly and painlessly as possible.

marlab · Tue May 03, 2022 7:26 pm

Just noticed - MPLS subsystem is removed from RB941-2nD

anav · Tue May 03, 2022 7:31 pm

Well, there is "basic" instructions and there is "the realty" with all the weird issues and not to speak of the different platforms. That's why there is room for improvements as in "best practice" (ie specification by example) like for example the setting for "NetBIOS" that should be a part of the standard use as Rextended mentioned

There is always para H. - viewtopic.php?t=182373

pe1chl · Tue May 03, 2022 7:40 pm

Well, there is "basic" instructions and there is "the realty" with all the weird issues and not to speak of the different platforms.

The instructions are not that bad, but you need to have some experience or else at least follow them to the letter and semicolon.
Usually when people are trying to recover bricked routers, they already are in some state of panic and/or their network is partly down, and patiently reading documentation is difficult. Making the documentation more extensive is probably not going to help better than having netinstalled a device before it became a critical problem.
But some of the problems mentioned are just the result of limitations in netinstall and areas that could be improved.

pe1chl · Tue May 03, 2022 7:41 pm

Just noticed - MPLS subsystem is removed from RB941-2nD

Out of the window goes your plan to use the RB941-2nD as the preferred routing platform for your enterprise!

mkx · Tue May 03, 2022 8:01 pm

As I explained above, with two ethernet it does not work on Linux and you have to plug the cable in "the right port" and know or experiment which one that is. In the old days probably the one that shows up as eth0, but in the current mess caused by mr. Poettering you cannot know which one is the first from looking at the silly "predictable names".

If linux uptime is not long, one can have a look at output of dmesg command (it's a FIFO buffer of log entries, after a while earlier entries get pushed out) ... so far I've always seen traces of renaming to "predictable names" in first few seconds of uptime, together with original name in form of ethX.

Larsa · Tue May 03, 2022 8:04 pm

I've read plenty of opinions when it comes to best practices for different ways of working like for example always check the forum and perform extensive tests before deploying new releases.

This is know by most people who works in the industry and semi-professional private users BUT not the regular end user for home usage which is a total different matter. Also, a regular home user would never cope with Netinstall.

That's why new versions must always be tested rigorously before they are released in the "stable" channel. This is also one of the most important tasks for a release manager.

EDIT: IMHO, a failing release should always be retracted immediately.

Larsa · Tue May 03, 2022 8:10 pm

There is always para H. - viewtopic.php?t=182373

Yeah, that's a good example of information that definitely should be part of the standard documentation. Also, that's what I call best practice (ie specification by example)

hecatae · Tue May 03, 2022 8:33 pm

Just noticed - MPLS subsystem is removed from RB941-2nD
Out of the window goes your plan to use the RB941-2nD as the preferred routing platform for your enterprise!

Strange omission though seeing as MPLS is still available on 7.3beta for the rb941

marlab · Tue May 03, 2022 9:13 pm

Just noticed - MPLS subsystem is removed from RB941-2nD
Out of the window goes your plan to use the RB941-2nD as the preferred routing platform for your enterprise!

Well, that little low-power box is still useful for IoT (sorry, obviously a new term for you).

Paternot · Tue May 03, 2022 9:17 pm

There's no mention on the wiki of it not being Production Ready: https://help.mikrotik.com/docs/display/ROS/WifiWave2
And it's being produced as a Stable package, so if it was not production ready, I'd assume it would only be available for the testing branch?

Yes, looks like it is considered "production ready". Well, at least we have RoS 7.2.3 now.

ZupoLlask · Tue May 03, 2022 10:04 pm

MikroTik,

You removed an important feature (MPLS) from a device in a minor firmware update, without prior warning nor changelog entry.

It's wise to inform and give some explanation if this was an accident or not... before a new rage wave.

the2masters · Tue May 03, 2022 10:08 pm

Hello .... The problem of rebooting the LHG XL 52 ac has not been resolved since version 7.2 The device starts auto restart minutes after the update .. The device works satisfactorily on version 7.1.5 and below

has anyone reported this? I ran into the same problem, connection working for few minutes, then reboot.

laca77 · Tue May 03, 2022 10:31 pm

On RBOmniTik-5HacD if i installed the 7.2.3 and requested a software reset (don't keep anything, so all field was empty and the Run After Reset field is empty too) and rebooted, the device looks like fall into etherboot state and appear for some second in winbox but not able to connect int and disappear from the list after a couple of seconds. With NetInstall i can see it and re-install the 7.2.3 so iit is easy to bring back to the life, but the soft-reset looks like soft-brick the device. I met with this behavior with the 7.2.1 software too on this device. I can reproduce it multiple time.

marlab · Wed May 04, 2022 12:24 am

Strange omission though seeing as MPLS is still available on 7.3beta for the rb941

I've just updated my hAP lite to 7.3beta37 - nope, menus for winbox and webfig indeed exist, just they are not functional, and MPLS is not available via terminal. I somehow like checking new releases on the weakest hardware I have as it's easiest to spot potential problems ;) Maybe it is an omission indeed. And, if intended - an official note should be made.

dominiaz · Wed May 04, 2022 12:38 am

7.2.3

*) vpls - fixed "pw-l2mtu" parameter usage;

Its not working...

VPLS interface over MPLS in L2MTU shows nothing - just actucal MTU.

7.3beta37

*) vpls - fixed "pw-l2mtu" parameter usage;

It works fine. L2MTU looks normal here.

Please fix it in 7.2.3.

Kevo · Wed May 04, 2022 3:58 am

Not sure if this is new to 7.2.3 or not, 7.2.3 is the first version of 7 I've used, but in webfig the ntp servers I specified using winbox show up as blank entries and trying to input them again shows red as if they are invalid. They are working and show up in the config if exported at the terminal. I was just using x.pool.ntp.org addresses. It seems to only like ip numbers.

rextended · Wed May 04, 2022 4:01 am

On v7 sNTP is removed and are added instead NTP Client and Server.
Is not the same menu as before.

zandor · Wed May 04, 2022 6:44 am

Upgrading from 7.1.3 to 7.2.3 does not fix the RB5009UG+S+IN port speed mismatch issues with the 2.5Gb port.

I have a NetGear CM2050V cable modem with Comcast "1.2Gb" service connected to the 2.5Gb port on the RB5009UG+S+IN and a CRS326-24S+2Q-RM connected to the 10Gb port, plus a couple NetGear 1Gb switches connected to the CRS326 through an S-RJ01. I have some computers connected to the CRS326 over 10Gb fiber, and double cabled one of them with 1Gb Cat6 for testing.

Upload seems fine, but Comcast only offers "35Mbps" IIRC, and I'm getting ~40 so I can't really test it. They seem to overprovision by about 20%.
SMB (Windows file sharing) file copies run at the expected speed, about 1.1Gb per second between 10Gb hosts with PCI-e SSDs and 115MB/s over 1Gb through the CRS326 in both directions. I could maybe squeeze a little more out of the 10Gb hosts using a VLAN with jumbo frames enabled.

Downloads:
With the 2.5Gb port on the RB5009 set to 1Gb everything seems to get 950Mbps, so working as expected.
10Gb hosts get about 1430Mbps with the 2.5Gb port on the RB5009 set to 2.5Gb. So 1.2Gb + 20% minus a little. Also working as expected.

Internet download speed on the 1Gb test machine is a mess when the 2.5Gb port on the RB5009 is set to 2.5Gb. 210-250Mbps, and there's a lot more variation than one would expect on a quiet network. Connecting directly to one of the 1Gb ports on the RB5009 is better, 800-900Mbps, but still not working right. I could put up with 1Gb clients only getting 800Mbps, but 250 is just a no-go. A 1Gb host on one of the NetGears connected to the CRS326 via an S-RJ01 or connected directly to an S-RJ01 gets the same speed, about 210-250Mbps.

All of this worked just fine when I had "600Mbit" cable service. It didn't matter if the 2.5Gb port was set for 2.5 or 1Gb. I'd get close to 600Mbps down on a Comcast speed test running on my phone over WiFi. My 10th gen i9 machine would get just under 720Mbps (Comcast overprovisions/understates actual speed to keep people with marginal equipment from calling tech support) on a Comcast speed test. After upgrading today the only things that work properly at "1.2Gbps" down are computers with 10Gb NICs. Those get 1.4Gbps+.

rpingar · Wed May 04, 2022 7:05 am

7.2.2 & 7.2.3 are unable to select the correct ipv4 local address in BGP!!!!
if you leave it automaticly choosed the bgpv4 dosn't do anything and refuses the connection, you have to manuallly write it to let it works!!!

Opened a ticket about it: SUP-81263

regards
Ros

Znevna · Wed May 04, 2022 7:33 am

Upgrading from 7.1.3 to 7.2.3 does not fix the RB5009UG+S+IN port speed mismatch issues with the 2.5Gb port.

Try this viewtopic.php?p=929964#p929782

benlg · Wed May 04, 2022 10:06 am

Still facing issue on CCR2116, when running too many IPs, some of them do not respond at all.
Bringing most of the IPs down make the other coming back online, which is really strange...
SUP-80578 still waiting for support on this.
Thank you again MikroTik team !

IntLDaniel · Wed May 04, 2022 10:12 am

7.2.2 & 7.2.3 are unable to select the correct ipv4 local address in BGP!!!!
if you leave it automaticly choosed the bgpv4 dosn't do anything and refuses the connection, you have to manuallly write it to let it works!!!

Opened a ticket about it: SUP-81263

regards
Ros

I am currious if my issue viewtopic.php?p=930880#p930866 could be related ? (but not using any config in BGP)

thuety · Wed May 04, 2022 10:28 am

on my main home router I am still using vers 6.48 long term firmware.
I cannot imagine anyone in a business using anything less than long term, which to means, proven over time to be stable.
I do it because my family are the most important clients of all.

My main reason for going to v7 was wireguard und udp-openvpn!

th0massin0 · Wed May 04, 2022 10:32 am

SSTP still unusable. #SUP-67642

thuety · Wed May 04, 2022 10:36 am

RB1100 and RB2011 upgraded from 7.2.1 without problems

I had random reboots with RB2011 and 7.2.x, you're ok?
Release 7.1.5 works fine.

marlab · Wed May 04, 2022 12:27 pm

RB1100 and RB2011 upgraded from 7.2.1 without problems
I had random reboots with RB2011 and 7.2.x, you're ok?

Do you use CAPsMAN? If so, the fix for that problem will be available soon (I'm just testing the pre-release version and it's already fixed there).

IntLDaniel · Wed May 04, 2022 1:51 pm

My router is RB5009UG+S+IN, when I upgrade to v7.2.3 from v7.2.1, my router is working but I can't open login page of the router in the browser, the winbox can't connect to the router.
How can I fix this problem, can I downgrade to v 7.2.1 from usb?
Many thanks !

It seems like the same issue like mine viewtopic.php?p=931069#p930866 , did you try to connect WinBox via MAC address?

npeca75 · Wed May 04, 2022 2:24 pm

...This is know by most people who works in the industry and semi-professional private users BUT not the regular end user for home usage which is a total different matter. Also, a regular home user would never cope with Netinstall.

As there is so much off-topic, so, here is my 5c

from my point of view
if MT decide do backport WireGuard to V6 branch, then everything will be OK
why?

1. home users does not need cutting edge technology. WG was missing and many tried (and bricked) with v7 to gain WG. So, low power device, V6, and WG will be sufficient (and safe) to usual home user
2. If you are a hobby tester, then v7 is your way to put your family in background and spend your spare time with PRO BONO work for MT. Netinstall is your own problem. you wantetd, now take it
3. For PRO users who need NASA/JPL technology and ROS v7 , they are already PROs, so no trouble with Netinstall

this way, bitching, cursing, bricking, and hammering router case when you are angry, will be minimal
90% problem is simple home users who once in a life need to netinstall

and then forum get flooded with offtopic

rextended · Wed May 04, 2022 2:26 pm

Well... Nice request!

pe1chl · Wed May 04, 2022 3:40 pm

from my point of view
if MT decide do backport WireGuard to V6 branch, then everything will be OK

Yeah but that is only your point of view. Because you apparently are interested in wireguard (only).
But others are interested in other parts of RouterOS improvements. And so everything would have to be backported.
And in fact that is what was happening for several years: v7 was postponed over and over and promised v7 features were backported into v6.

But for wireguard that isn't going to happen. It requires the new Linux kernel and backporting that is the same as upgrading to v7.

Pl07R3K · Wed May 04, 2022 4:15 pm

ac3 and Audience were updated to version 7.2.3 yesterday, so far so good.

Ullinator · Wed May 04, 2022 4:37 pm

RB5009, RB4011 (with WiFi - CAPsMAN) and 5x CAP (XL) AC (via CAPsMAN) succesfully updated to 7.2.3 from 7.2.1 (ROS and FW).
No issues so far.

npeca75 · Wed May 04, 2022 4:45 pm

Yeah but that is only your point of view. Because you apparently are interested in wireguard (only).

if you be kind to read whole post
HOME users = WG
not me !!!

And about kernel, half of kernel in ROS is patched in house, custom this, custom that ... not a big deal

anyway, back to v7, i looking forward for topics like:
Wife left me and gone with guy who use v6 because he has a time for long walks and garden...

again, focus was on HOME users

andlommy · Wed May 04, 2022 5:28 pm

Audience LTE + WifiWave2 package
Full reset with no default config.
Getting following message at startup:
error while running customized default configuration script: bad command name wireless (line 979 column 25)

Disabling wifiwave2 helps
Rolling back to 7.2.1 helps

rextended · Wed May 04, 2022 6:10 pm

Confirm, installed wifiwave2 on Audience, no other problems than the line in the log

terminal code

jan/02/1970 00:00:33 system,error,critical error while running customized default 
configuration script: bad command name wireless (line 979 column 25)
jan/02/1970 00:00:33 system,error,critical 
[admin@MikroTik] > log pri
 00:00:20 system,info crossfig will upgrade version 6 configuration
 00:00:21 system,info router rebooted
 00:00:28 interface,info ether1 link up (speed 1G, full duplex)
 00:00:33 system,error,critical error while running customized default configuration script: bad command name wireless (line 979 column 25)
 00:00:33 system,error,critical

979  :while ([/interface wireless find default-name="wlan3"] = "") do={
   ------------------------^ 25 unexpected reless, expected fiwave2

This happen because get-custom-defconf is not maded for wifiwave2 only,
and have internal references to /interface wireless that do not exist on wifiwave2 only devices.

The problem happen also if is added later the wifiwave2 extra package.

thadrumr · Wed May 04, 2022 6:29 pm

Demo keys don't seem to work with this version. I had a working demo key from Version 7.1 but this broke it for a level 1 license.

rpingar · Wed May 04, 2022 6:42 pm

using packet sniffer tool on x86 put all the CPUs to 100%, to mitigare the issue you have to limit the filter to just one or two interface maximum.
Seem packet sniffer is not optimized.
regards
Ros

Hominidae · Wed May 04, 2022 9:54 pm

Confirm, installed wifiwave2 on Audience, no other problems than the line in the log
[...]
This happen because get-custom-defconf is not maded for wifiwave2 only,
and have internal references to /interface wireless that do not exist on wifiwave2 only devices.
The problem happen also if is added later the wifiwave2 extra package.

...but this is a bug, that had been introduced and reported for 7.2.1 already
Edit: see viewtopic.php?p=929862#p929862

Guscht · Wed May 04, 2022 10:13 pm

My main reason for going to v7 was wireguard und udp-openvpn!

At home, I run everything v7. No problems so far, but I am not doing fancy stuff as @ work, like PIM-Routing.

@ work, we run everything v6, *except* 1 device with v7 for WireGuard. In my opinion, you could have easily best of both worlds. Run v6 for production and only for the "one" v7 feature you'd like to use, run a dedicated v7 device.

The real problem I see, MT delivers enterprise-grade devices with a pre-installed v7!! For us, such devices are an absolute no-go! We would have to downgrade to v6, which is not recommended by MT (downgrade beyond the factory version). Please MT, stop delivering enterprise-grade CCRs with a preinstalled v7. Such devices are a white brick, because only v6 is production-ready. v7 is far(!!) away from this stage. V7 is nice for home, where you could fiddle hours with NetInstall, but for a production enviroment, ABSOLUTELY NOT! At least if you do more than the abolute basic static DAC-Routing-stuff.

dave864 · Wed May 04, 2022 11:40 pm

Hope everyone learned a lesson?
Don't jump the gun. Chill out. Let some people install and see how it goes. Use a test bench.

I only just upgraded to 7.2.1 the day before these nightmares started. My next jump will be a week tested 7.4.x

Stop jumping on every update that comes out. Give MT time and they'll do you right.

Larsa · Thu May 05, 2022 12:01 am

Hope everyone learned a lesson?

Well, tell that to the regular home user that never visits the forum. I suggest that MT introduce a new "pre-release" channel which acts kind of a production test to capture serious flaws before moving it to "stable".

bda · Thu May 05, 2022 1:15 am

I tried to upgrade x86-64 with ROS 7.1.2 to 7.2.3 and got cycle reboot after ROS booted... Cant stop this cyclic reboot...

pcunite · Thu May 05, 2022 1:21 am

@ work, we run everything v6, except 1 device with v7 for WireGuard.

Same. Needed to provide VPN (WireGuard) for a client so I went with a dedicated device running v7.2.1.

bda · Thu May 05, 2022 3:46 am

I tried to upgrade x86-64 with ROS 7.1.2 to 7.2.3 and got cycle reboot after ROS booted... Cant stop this cyclic reboot...

Bad. And now I have bricked x86-64 box, that cant boot. Netinstall does not work on this PC... Very bad

rextended · Thu May 05, 2022 3:52 am

...but this is a bug, that had been introduced and reported for 7.2.1 already
Edit: see viewtopic.php?p=929862#p929862

No, is not the same bug, previous bug is (if you write it correctly)
no such item
this time is
bad command name wireless (line 979 column 25)

dibatech · Thu May 05, 2022 10:28 am

 vrf - fixed VRF leaking;

Any more info on this specific issue would be appreciated please.

Thu May 05, 2022 10:30 am

Netinstall may also work on a PC with multiple interfaces, but it is tricky. Netinstall broadcasts the initial handshake message to 255.255.255.255, so the packets are usually sent to the interface where the default gateway is located. To use Netinstall on a different interface, you need to (temporarily) redirect global broadcasts there. Here is an example for Linux that allows using Netinstall on eth1 without disabling other interfaces:

sudo ip route add 255.255.255.255 dev eth1

We have plans to rework the Netinstall protocol, allowing users to specify the network interface or/and IP subnet of the client IP. For example, if the client IP is 192.168.1.2/24, broadcasts should be made to 192.168.1.255 instead of 255.255.255.255. Unfortunately, some legacy compatibility issues make it harder to implement than it sounds.

bda · Thu May 05, 2022 10:45 am

Thank you for info on netinstall.

But I`ve got "NBP is too big" error with latest netinstall-7.2.3.zip and netinstall-6.48.6.zip
Earlier i read that is bug in netinstall: viewtopic.php?t=176162
Am I right or am I missing something?

Netinstall may also work on a PC with multiple interfaces, but it is tricky. Netinstall broadcasts the initial handshake message to 255.255.255.255, so the packets are usually sent to the interface where the default gateway is located. To use Netinstall on a different interface, you need to (temporarily) redirect global broadcasts there. Here is an example for Linux that allows using Netinstall on eth1 without disabling other interfaces:
Code: Select all
sudo ip route add 255.255.255.255 dev eth1
We have plans to rework the Netinstall protocol, allowing users to specify the network interface or/and IP subnet of the client IP. For example, if the client IP is 192.168.1.2/24, broadcasts should be made to 192.168.1.255 instead of 255.255.255.255. Unfortunately, some legacy compatibility issues make it harder to implement than it sounds.

pe1chl · Thu May 05, 2022 11:17 am

Netinstall may also work on a PC with multiple interfaces, but it is tricky. Netinstall broadcasts the initial handshake message to 255.255.255.255, so the packets are usually sent to the interface where the default gateway is located. To use Netinstall on a different interface, you need to (temporarily) redirect global broadcasts there.

That part probably works, but it looks like it is going wrong in the next phase, where the netinstall program has to answer an explicit request from the router.
(I forgot the exact details because it is some time ago I was trying it on Linux, but I saw that the router was detected and the next phase started but it was hanging)
When using wireshark I can see the router sending a packet but it never gets a reply because that goes out on another interface.
I guess the netinstall opens a raw network socket without specifying the interface. At least in Linux is is possible to use a socket option to specify the interface, and there is a way to query the list of available interfaces. I don't know if that is possible in Windows as well, but probably it is.
It would maybe help when there was an exact description of the network protocols used for the entire netinstall process. That would not only make it easier to understand how details of the network setup affect the operation, but it would also enable others to make netinstall compatible software for use in environments that MikroTik does not support.

MrBZA · Thu May 05, 2022 11:23 am

SFP link flapping with a standard SM gigabit module in a hEX S (RB760iGS)
Have downgraded back to 7.2.1 for now.

Other RB's not using SFP's have been upgraded OK to 7.2.3

thuety · Thu May 05, 2022 11:56 am

I had random reboots with RB2011 and 7.2.x, you're ok?
Do you use CAPsMAN? If so, the fix for that problem will be available soon (I'm just testing the pre-release version and it's already fixed there).

Oh great, thanks

LightnetBarry · Thu May 05, 2022 1:34 pm

7.2.2 & 7.2.3 are unable to select the correct ipv4 local address in BGP!!!!
if you leave it automaticly choosed the bgpv4 dosn't do anything and refuses the connection, you have to manuallly write it to let it works!!!

Opened a ticket about it: SUP-81263

regards
Ros

I have just had this issue upgrading from 6.48.6 to 7.2.3 however my experience is that the correct local address is set for eBGP but defaults to the connection Router ID for iBGP connections.
It also defaulted to the connection Router ID for a Multi Hop eBGP connection.

Barry

infabo · Thu May 05, 2022 1:47 pm

Of course you can list network interface on windows https://docs.microsoft.com/en-us/window ... start-page

rextended · Thu May 05, 2022 2:42 pm

THANKS!!! @raimondsp

[...]
Netinstall broadcasts the initial handshake message to 255.255.255.255, so the packets are usually sent to the interface where the default gateway is located.
[...]
Code: Select all
sudo ip route add 255.255.255.255 dev eth1
[...]

This solve Netinstall problem without disable anything...
On example Netinstall is on NIC 6, must be disabled 255.255.255.255 for NIC 8 (1 loopback must be ignored)

Windows Terminal code

C:\WINDOWS\system32>route print -4
===========================================================================
Interfacce list
  8...30 85 a9 98 1f 0b ......Realtek PCIe GBE Family Controller
  6...30 85 a9 98 24 51 ......Intel(R) 82579V Gigabit Network Connection
  1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active routes:
          Address             Mask         Gateway         Interface Metric
[...]
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link     192.168.0.195    281
  255.255.255.255  255.255.255.255         On-link      192.168.88.3    281
===========================================================================
Permanent routes:
  Nothing

C:\WINDOWS\system32>route DELETE 255.255.255.255 MASK 255.255.255.255 IF 8
 OK

C:\WINDOWS\system32>route print -4
[...]
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
  255.255.255.255  255.255.255.255         On-link      192.168.88.3    281
[...]

Deleted route is recreated again on interface off/on cycle or reboot Windows.

Hominidae · Thu May 05, 2022 3:29 pm

No, is not the same bug, previous bug is (if you write it correctly)
no such item
this time is
bad command name wireless (line 979 column 25)

...ah, my bad...yes, you are right....thanks for the clarification.

Thu May 05, 2022 3:32 pm

Maybe it's easier to just change metrics for particular interfaces in advanced settings?

rextended · Thu May 05, 2022 3:47 pm

Yes, but... depends on who you explain it to...

Using cmd is not permanent and prevent mess... just reboot the PC for fix errors...

Thu May 05, 2022 4:02 pm

Yes, but... depends on who you explain it to... :roll:

Using cmd is not permanent and prevent mess... just reboot the PC for fix errors...

Excellent solution !

jimmer · Thu May 05, 2022 4:05 pm

Hope everyone learned a lesson?

Well, tell that to the regular home user that never visits the forum. I suggest that MT introduce a new "pre-release" channel which acts kind of a production test to capture serious flaws before moving it to "stable".

I agree on this, there should be no reason code errors like the ones we're seeing should ever make it into a stable tree, regular users should be safe to assume that a 'stable' release wont lunch their router to the point where they need to factory netinstall them back to a working state, if it means we don't see as frequent updates then I'm all for that as long as what gets released as 'stable' is tested thoroughly, otherwise the term stable is meaningless.

I started using Mikrotik with the move from 5.x to 6.x (My very first RB for my home router was a RB2011 back in 2013) and I really dont recall the level of issues I have seen with 7.x tree.

I still maintain that 7.1.5 is the best version currently available, 7.2.x has not been an enjoyable venture, hanging back until things are sorted out.

Jim.

Rox169 · Thu May 05, 2022 4:21 pm

You can stay on 7.1.5 but there are not included two important fixes.... one is filesystem fix to prevent bootloop and the second is fix for loosing configuration after upgrade. So both problems could cause you to drive to HW and manually fix it...

eworm · Thu May 05, 2022 5:06 pm

Let's hope we will see 7.1.6 soon... Any estimate?

rextended · Thu May 05, 2022 5:09 pm

7.1.6? Never, new "stable" branch is 7.2.6

eworm · Thu May 05, 2022 5:13 pm

Version 7.1.6 would be the next in long-term branch...
But this is off topic, we should stop here.

pe1chl · Thu May 05, 2022 5:29 pm

Well, tell that to the regular home user that never visits the forum. I suggest that MT introduce a new "pre-release" channel which acts kind of a production test to capture serious flaws before moving it to "stable".
I agree on this, there should be no reason code errors like the ones we're seeing should ever make it into a stable tree, regular users should be safe to assume that a 'stable' release wont lunch their router to the point where they need to factory netinstall them back to a working state

I don't expect any action from MikroTik in that direction. Look, they repeatedly refused to take down a clearly broken "stable" versions from the download server and even to include warnings in release notes that "normal users" see when they open their "check for upgrades" window.
They clearly do not care if users brick their routers or run into severe trouble, even when it is known beforehand that it is likely to happen...

bda · Thu May 05, 2022 5:41 pm

Excuse me.
Can anybody face an issue with latest netinstall-7.2.3 and netinstall-6.48.6 ?
Two of my x86-boxes gone to infinite bootloop after upgrading to 7.2.3. And now netinstall take my boxes to "NBP is too big" error after getting an IP-address from netinstall application.
So I can`t recover my two x86 boxes in any form now...

Any suggestions on this problem?

Jotne · Thu May 05, 2022 6:39 pm

Version 7.1.6 would be the next in long-term branch...
But this is off topic, we should stop here.

Off topic, but I was very surprised when I did see that 7.1.5 thread was closed in favor for 7.2.1.
So is 7.2.1 same as 7.1.6?
Normal MT keeps a version over a longer periode. When its stable for some time, it changes to long term.
So what would be the next long term release ? 7.8.52?

Larsa · Thu May 05, 2022 8:30 pm

We have plans to rework the Netinstall protocol, allowing users to specify the network interface or/and IP subnet of the client IP. For example, if the client IP is 192.168.1.2/24, broadcasts should be made to 192.168.1.255 instead of 255.255.255.255.

It seems like a sound decision to consolidate any shortcomings to make the Netinstall installation and usage as streamlined as possible. When things gets fricked-up badly you more then ever need a tool that is reliable and doesn't cause additional hassle during the restoration process.

Unfortunately, some legacy compatibility issues make it harder to implement than it sounds.

Yeah, when it comes to legacy code nothing is simple. Regarding compatibility it depends on how far back in time you want to stretch things. If you are dependent on an old third-party win32 network stack, you might have some extra work to do, but if you settle for Winsock 2.0, it will work on all versions from Win95 (1995) onwards.

EDIT: and there might be some other small issues to take care of as well viewtopic.php?t=176162 ;- )

francogp · Thu May 05, 2022 9:20 pm

I upgraded from 7.2.0 to 7.2.3, and now I cannot access via IP, only Mac address. Tested from winbox for Windows and from android, same results

benlg · Thu May 05, 2022 10:10 pm

Sounds like this ?

francogp · Fri May 06, 2022 2:36 am

I upgraded from 7.2.0 to 7.2.3, and now I cannot access via IP, only Mac address. Tested from winbox for Windows and from android, same results

Also, I cannot ping anymore my router. My configs worked just fine for 2 years,.... until this update

ErfanDL · Fri May 06, 2022 9:30 am

after upgrade to 7.2.3 Route rules not working.

Jotne · Fri May 06, 2022 9:53 am

From what version?

ErfanDL · Fri May 06, 2022 10:00 am

From what version?

7.2.1

Fri May 06, 2022 10:05 am

From what version?
7.2.1

And what device ?

ErfanDL · Fri May 06, 2022 10:09 am

7.2.1
And what device ?

RB2011UiAS-2HnD

pe1chl · Fri May 06, 2022 10:34 am

after upgrade to 7.2.3 Route rules not working.

What do they look like now? Again these "lookup in table abc" replaced by "lookup in table *0x4000" or similar?
That has happened to me before on upgrades, twice in fact. It seems they cannot get that under control.