7.25 [stable] is released!

Rgarding the poe-out status: controller_error on the CRS354

  • Downgrade 7.24.5 (incl. Firmware) -> fixed issue
  • Upgrade (again) to 7.25 (incl. Firmware) -> stuck at "Controller resetting" in red (dont remember the exact wording)
  • Reboot
  • stuck at "Controller_init" in red (dont remember the exact wording)
  • Reboot
  • multiple ports stuck in "poe short detected" in red (dont remember the exact wording)
  • Reboot
  • no warning -> works apparently

Has a bit a bitter taste tbo, all other devices upgraded without incident.

How it should be (example for 7.26 stable):

What's new in 7.26 [stable] (2026-mm-dd):

  1. fixed everything reported as broken in 7.25 stable up to 7.26 beta n
  2. NOT added ANY new feature

I’ve seen this discussion before.
Beta or RC material shouldn’t even be mentioned.
The list should starting from the latest standard version 7.24

I've long posted some stats on a new stable. But MikroTik added the new Version Compare to manual.mikrotik.com so we have "official" stats on the #cmds and #attributes...

Now... I'm not sure if it's 7.24.5 (not 7.24) nor 7.25 (not 7.25beta), or if that's updated upon a release... I'll still share my "CLI diff" from 7.24.5 to 7.25: RouterOS Schema — Side-by-Side Diff

which shows:
image
(some of the difference in counts is the I count attributes by verbs, include standard verbs; mikrotik ignores "standard verbs" like get/set/remove/print, and uses one set of attributes in their diff counts)

After updating my hAP Be Lite no devices can't connect anymore to any wireless! trying to downgrade now.

It is wonderful .

I also updated my hap be lite. And the wifi stopped working. In mld mode and without mld. No way.

Lemme just say my be3 media's wifi hasnt been exactly stable since 7.25beta3:

I got wifi working on hap be lite. I did the following to get it successfully enabled:

  1. Update routerOS and firmware to 7.25
  2. Disable channel reselect time/interval
  3. Disable MLO
  4. Reboot the device

Afterwards, wifi started working for me. The reboot is important, just changing settings is not sufficient. Wifi speed is around 500-700mbit/s download, 1gbps upload on 5GHz with a wifi7 client, measured with iperf3 in local network.

Me too.. CAPsMAN on AX^3 and affected are AC and AX wifi devices.

Tons of logs - starting+stopping interface on CAPsMAN:

Oct 23 19:45:37 router wireless,debug 2G-AC-wifi: starting AP
Oct 23 19:45:37 router wireless,debug 2G-AC-wifi: stopping AP, disabling
Oct 23 19:45:37 router wireless,debug 2G-AX-wifi: starting AP
Oct 23 19:45:37 router wireless,debug 2G-AX-wifi: stopping AP, disabling

Exactly the same issue on release 7.25 - cAP ax x2 using WiFi configuration on a CRS326-25G-2S+ reproduced as mentioned in this post.

I've downgraded to 7.24.5 and everything is ok again. You need to load both routerOS and your wi-fi module package to files, then go in system/packages and selection routerOS -> downgrade

Local ax3 and ax2 updated without issues.

Updated a remote ac2 from 7.23.8 LT and free HDD space, after console clear-history command:

7.23.8 Long Term: 152Kb Free HDD

7.25: 532Kb Free HDD

So far so good

CCR2004-16G-2S+PC and 3x hAP-ax2 without issues.

Should I familiarise myself with the new wifi/network menu and consider migrating my old configuration (configuration, channel, security, etc.) to the new system? Is that expected to work with CAPsMAN right now?

Thanks,
Patrick

It is working with capsman out of the box. You disable the old wifi config and capsman provisioning, set up new config in network, keep capsman enabled (without provisioning settings) and it will distribute the network settings to the caps. I find this pretty comfortable for simpler wifi setups. If you want to set all details manually (channels per radio etc), I think the old method could probably be more appropriate.

my Addresses.cdb will not load in Winbox 4.

please fix. i have 700 devices saved in it. i am NOT doing that myself again.

image

I use a smol BananaPi M4 Zero (https://www.banana-pi.org/en/banana-pi-sbcs/171.html) with Armbian for my AI-programmed "Word and Moon Clock display" (like https://www.qlocktwo.com/). I start this simply via a cronjob, which opens a browser and this connects to my internal Apache2 with the clocks. Worked for years now :raising_hands:

After the 7.25 update, the BananaPi did not see any of my WLAN-networks. Simply not in the list of available networks (my networks are not hidden). And the one it had already did not connect. I updated Armbian via mobile-hotspot from phone -> nothing.

Now I removed the following suspicious options in my CAPsMAN (suspicious beacuse everything manually enabled is suspicious to me in CAPsMAN if something does not work):

grafik

grafik

grafik

Went to Radios -> Action -> Provision

BANG -> BananaPi sees the WLAN-networks!!

Now I went back and enabled the 3 options exactly the way they were before.

Again: Radios -> Action -> Provision

Rebooted the BananaPi -> still sees the networks.

Strange but in a certain Mikrotik-way familiar :upside_down_face:
All other devices I checked, saw the networks everytime (Shelly Plugs, Nixie-Tubes... all that chepo stuff).

After this update IPv6 on the router fails. The router gets a prefix via dhcp client, adds a dynamic pool, addresses are added from this pool to the interfaces. Even IPv6 routing works reliably, but the router itself can not access any IPv6 resources after some time. Releasing the prefix (/ipv6/dhcp-client/release [ find ]) makes the client bind a new one, and things works for some time - until it fails again.

As I use netwatch extensively this is an issue for me...

After updating an RB3011UiAS to RouterOS 7.25, access via WinBox 4.4 gets stuck on the loading screen with the message "Downloading logged-in user information...". Authentication appears to complete, but the administration interface doesn't fully open, preventing normal device management. Has anyone else experienced a similar problem?

Yes, I also went back to version 7.24.5 on hap be lite. Everything is working correctly now.

I also have a hap be3 device. It was updated without any problems.