7.26beta [development] is released!

this is only for CMR server.

CMR client (the device you manage) will work on MIPS too, see CMR client manual section separately CMR-Client | RouterOS Manual

Ah, ok...!!!!

:person_facepalming:

@normis To dispel any doubts, I would recommend including a table...

arm arm64 x86 CHR mipsbe mmips tile ppc smips mipsle SwOS v6
server :white_check_mark: :white_check_mark: :white_check_mark: :white_check_mark: :cross_mark: :cross_mark: :cross_mark: :cross_mark: :cross_mark: :cross_mark: :cross_mark: :cross_mark:
client :white_check_mark: :white_check_mark: :white_check_mark: :white_check_mark: :white_check_mark: :white_check_mark: :white_check_mark: :cross_mark: :cross_mark: :cross_mark: :cross_mark: :cross_mark:

What would be size of CMR module as 16MB devices "live on the free space edge"?

CMR client does not take up extra space and is built into RouterOS. it works on many architectures.

CMR server should only be installed on powerful ARM64 routers with enough space (see Rextended diagram)

I'm facing an issue with my HAP AX S where the Wi-Fi download speed (TX rate on router) gets completely stuck at exactly 6 Mbps. AC and AX client.

The device connects normally and the signal strength is fine, but the download speed is locked at this legacy minimum and refuses to scale up.

@normis

New funcionality always takes some programm space as code has "size" > 0.
But let's assume that it would be only a bit of a bit of free space on these 16MB devices.

We emptied the trash bin and found space

I wonder which TCP (hopefully) ports are used by CMR server, if we are to use it over NAT as manual suggests I presume it would be necessary information...

Come on...
they’ve spent the last few months cutting out the parts that were only needed for Winbox 3,
just to make room for the "Cloud Manager Router"...

Probably... 8291...

No matter what our prayers were answered and there is no external Ubi-like piece of software.
One ROS rules them all :slight_smile:

Looking at terminal output in documentation there's a lot of IPv4 addreses. I hope the CMR will work on IPv6-only networks.

So lets establish 05.10.2026 as a "ROS Cleaning Day" :slight_smile:

I can't forget it... It's my wife's birthday today...

This interests me most. Can any details be shared?

Yeah, and as a result we lost Winbox3 :face_vomiting:

Based on my testing, CMR appears to require TCP 54321 in the input firewall chain. Could you confirm this? If so, it would be helpful to include this in the documentation.

One thing that made me happy is seeing that they listened to the suggestions regarding the use of Release Chains, aligning them with what is actually expected based on the terms they represent.

  • Testing -> RC
  • Development -> Beta
  • l3hw - add VRRP hardware offloading support

In all of the talk about CMR, this seems to have been overlooked. I’ve been waiting for this one for a while now.