v7.1beta5 [development] is released!

RouterOS version 7.1beta5 has been released in public “development” channel!

What’s new in 7.1beta5 (2021-Mar-16 14:41):

!) added new “iot” package with initial Bluetooth (KNOT only) and MQTT publisher support;
!) ported features and fixes introduced in v6.48.1;
!) enabled initial MPLS support (CLI only);
*) export - fixed “export” command hanging;
*) wifiwave2 - improved interface stability with multiple WPA3 authenticated clients;
*) other minor fixes and improvements;

All released RouterOS v7 changelogs are available here:
https://mikrotik.com/download/changelogs/development-release-tree

How to report RouterOS v7 bugs:
http://forum.mikrotik.com/t/how-to-report-issues-in-v7-beta/133088/1

I had a test CHR on VMware ESXi 6.7 running 7.1beta4 with a quite simple config (1 interface, fixed address, a BGP session)
I used System->Packages upgrade to load 7.1beta5

It fails to boot now. On the console it says:

Load system

WARN: GPT: skip truncate
ERROR: could not mount disk!
Please attach it somewhere else.

Removed VM and re-created it from .ova template to fix it.

I just uploaded it to EVE-NG and am working through adding some config I used with previous beta versions.

It looks like the routing filters have changed slightly. What string value is expected?

This is what I see in beta5…the only option is “rule=” that I can see, I can’t add match-prfx-value


/routing filter rule add chain=ospf_out rule=

Rule -- string value

This is the syntax shown in help.mikrotik.com

/routing filter rule add chain=ospf_out match-prfx-value="dst<subsumes>182.168.0.0/16" action=accept

Still no wifiwave2 with cAPsMAN support…

The same here, CHR on XenServer 7. And the same was with upgrade to 7.1beta4. Something seems broken with CHR upgrades.

Can any one of you send us a RAW disk image from damaged CHR?

Now routing rule has script-like syntax. Try
routing filter rule add rule={

to see possible parameters.
One basic example:

add rule={ if ([protocol static] || [protocol connected]) then={ num-value distance<assign>100; action accept}}

!) enabled initial MPLS support (CLI only);

Thanks! That a important one

In routing filter, is set-type=blackhole supported? I noticed it wasn’t supported in previous betas.

Like this:

chain=malware-in address-family=ip invert-match=no action=accept set-type=blackhole set-bgp-prepend-path=“”

The “Quick Set” of WebFig always resets to “WISP AP”. I switch it to “LTE AP Dual” and logout. On next login it is “WISP AP” again. That was’nt the case in beta4.

This happens to me in v6 too

I only have a copy of the machine as it was before I attempted the upgrade. I can send it when no others have a copy of the failed one.

I can confirm the issue even when upgrading an completely fresh v7.1beta4 CHR so most likely the problem is not caused by any specific configuration.
I will send the resulting non working file via email directly to mikrotik as it is to big to attach it to this post.

WifiWave2 in 2.4GHz wireless work on RB4011iGS+5HacQ2HnD?

maybe due to:

ported features and fixes introduced in v6.48.1;

:smiley:

Same here, the difference is that I use Proxmox VE, with qcow2 disk, Virtio SCSI interface, simple SeaBIOS / i440fx combination and 3 VirtIO ethernet adapters.

Mine fails to boot too. My message is slightly different though:

Load system

Resizing disk(GPT)...
ERROR: could not mount disk!
Please attach it somewhere else.

Hello everyone, where are the promised BGP filters?
This is the only thing that stops me from moving to v7.

Capsman issue?
Using beta 5 I see packets from/to caps provisioned using slave configuration are not forwarded.
Clients get an IP from dhcp and arp tables looks ok
Upgraded from a working beta 4, using cap ac’s
Anybody else having similar issues using capsman?
KR

Cake reboots seems to be fixed in beta5, will report if any random reboot



Edit: Not fixed. Shitty random reboots with cake still happening. Usable beta in year 2030


RB4011