All my updates went fine, but all of them are on 1500 byte MTU internet connections...
My updates went fine, and they are all on PPPoE 1492 connections.
after upgrading CAPsMAN (RB4011) + 2 CAPs (cAP AX, hAP ax3) from 7.23.2 to 7.23.3, some wireless clients (particularly two iPhones and an iPad) were unable to maintain a wireless connection and would constantly connect, then possibly roam, then disconnect. after downgrading CAPsMAN to 7.23.2, behaviour was unchanged. after downgrading both CAPs to 7.23.2, the problem appears to be fixed.
also, very disappointed to hear you're still hiding security fixes, although i think we all knew what "stability improvements" meant historically; still, i won't be buying any more MikroTik products if i can find an alternative.
What actually bothers me about these "improved stability" changelog entries is that you never know what was actually made more stable.
At the same time, the usual advice is to read the changelog and only update if you find a change that is relevant to you.
So, if I do not have any stability problems on my device, I can reasonably assume that "improved stability" does not affect me and skip the update (assumption: no security fix in disguise).
But there are also users who, for various reasons, experience kernel panics or "router rebooted" or "100% cpu" issues. Of course, they will be tempted to update because "improved stability" might fix their problem. Then they may be disappointed to find out that their particular stability issue was not addressed at all.
And in the worst case, they introduce a different problem because they skipped several versions before updating (and probably receive flame comments from users because they did verify in lab first).
That makes these vague changelog entries quite frustrating.
Are we now going to re-run that discussion? Look at the first few replies to this topic (and to most other release topics)...
At least no one can "cancel" the discussion by "you're off-topic", since my comment refers directly to a changelog entry from this version.
It isn't that it is off-topic, the discussion has already been had in this topic and you are not adding any new information or viewpoints in your posting.
After upgrade CAP ac (RBcAPGi-5acD2nD, arm hardware) no more LLDP packets produced by device. RB760iGS (smips hardware) - send LLDP packets.
Hello everyone,
I would like to report a critical issue I encountered with the wireless interfaces on my router after the recent minor update.
Device & Environment details:
Hardware: RouterBOARD hAP ac2 (ARM)
Previous RouterOS: 7.23.2 (Working perfectly)
Target RouterOS: 7.23.3 (Issue occurred)
Issue Description:
Right after upgrading the system from version 7.23.2 to 7.23.3, the Wi-Fi completely stopped working and all clients were disconnected. When I logged into the router via Winbox to investigate, I noticed that under the WiFi -> Radios tab, all wireless interfaces were entirely gone. The list was completely empty, as if the physical radios were not detected by the system.
Workaround:
To restore the network functionality, I had to perform a standard downgrade back to version 7.23.2. As soon as the router booted up on the older release, the interfaces reappeared in the Radios tab, and the Wi-Fi started functioning normally again with my existing configuration.
Has anyone else experienced this regression on the hAP ac2 device with the 7.23.3 release? Should I wait for 7.23.4, or is there an underlying package conflict I should check?
Best regards.
please check if the wireless package was enabled or if there was any error during update.
I had no such issue upgrading a hAP ac2 from 7.23.2 to 7.23.3. Everything worked flawlessly. But, before I upgrade I always clear history to ensure there is enough space.
There are several things that might have gone wrong, but the most likely is that the wireless or WiFi package upgrade didn't work. I assume you always reboot after upgrade to guarantee routerboard firmware matches software?
That is not correct unless /system/routerboard/settings> set auto-upgrade=yes, which is not by default so you must initiate /system/routerboard/upgrade manually and then reboot...
In rare cases a second reboot may resolve the problem, but as you mention the hAP ac2 the most likely problem is lack of space on the flash. Do a netinstall of 7.23.3 keeping configuration.
How is your upgrade procedure? Do you use built-in updater or do you upload pkg files via Winbox? Are there any info/errors in system log on first boot after upgrade?
Version 7.24 has been released:
Hello everyone,
First of all, thank you all so much for your replies, suggestions, and engagement! I really appreciate your help.
To answer the questions regarding my upgrade procedure:
I used the built-in updater by clicking the "Check for updates" button directly in the System -> Packages menu. I did not upload the .npk files manually via Winbox.
Regarding the packages state after the update: I verified the Packages menu and both the routeros and wifi-qcom-ac packages were present and clearly marked as Installed: yes.
Despite this, the router simply could not see the hardware interfaces in the Radios tab.
You guys were absolutely spot on about the storage space being the root cause. My hAP ac2 was down to about 20 KB of free space. Because of this critical lack of storage, the router fell into a loop—I couldn't uninstall any phantom packages, generate a .backup file, or even do a standard downgrade. Every action returned a "not enough storage space available" error.
Here is what I ultimately did to fix it:
Since I couldn't save a backup file, I dumped my configuration to text using the /export command in the terminal and saved it to a notepad on my PC.
I performed a full Netinstall to format the flash memory and directly installed version 7.23.2.
I pasted my configuration back via the terminal.
The Wi-Fi radios are back and working perfectly now.
However, it is worth noting that even after a clean Netinstall on 7.23.2, the system shows only about 180 KiB of free space.
Thanks again for pointing me in the right direction!
Well done!