v7.1rc7 [development] is released!

RouterOS RouterOS beta
1

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

What’s new in 7.1rc7 (2021-Nov-25 16:35):

!) device-mode - added feature locking mechanism;
*) arp - limit total ARP table size based on installed RAM size;
*) bgp - fixed “nexthop-choice” selection;
*) bgp - fixed peer handling on point-to-point addresses;
*) bgp - ignore empty filter names on upgrade;
*) bgp - implemented BGP VPN configuration upgrade and other configuration upgrade fixes;
*) conntrack - limit total connection tracking table size based on installed RAM size;
*) crs3xx - fixed interface linking for some optical QSFP+ modules on CRS354 devices;
*) health - improved temperature reporting;
*) ipsec - fixed hardware acceleration support for ARM and ARM64 devices;
*) ipsec - fixed software fallback mode for AES-192 on IPQ4018/IPQ4019;
*) led - added “dark-mode” functionality control with Mode button for cAP XL ac;
*) lte - added “cell-monitor” support for Chateau 5G;
*) lte - improved LTE setting reporting to supout file;
*) ospf - fixed MD5 authentication with large packets;
*) ospf - fixed OSPFv3 interface configuration;
*) ospf - improved DB exchange speeds;
*) ospf - improved stability with large LS update packets;
*) route - fixed “Route Target” byte order;
*) route - fixed unreachable routed networks on VRFs;
*) route - fixed route rule upgrade;
*) route - fixed situation when routes with unequal distances got treated as ECMP routes;
*) route - improvements on VRF isolation;
*) route-filters - added “as-path” regexp testing tool;
*) route-filters - added “as-path-slow-legacy” to dsupport old style “as-path” filtering;
*) route-filters - fixed “as-path” bracket parsing and 4byte ASN usage;
*) routerboard - fixed “mode-button” functionality on devices that have such feature;
*) upgrade - improved major version upgrade process on hAP ac2 and cAP ac;
*) wifiwave2 - fixed enforcement of access list rules which only checks client signal strength for new connections;
*) wifiwave2 - removed non-functioning VLAN configuration parameters from access list;

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

2

Is container package available?

3

Not yet. Still working on improvements.

4

*) route - fixed route rule upgrade;

Does that include the /routing table section generation? Will existing badly converted config be auto-fixed?

5

If config was converted once then no. If you have a backup from ROS v6 which was generated on the router that was never upgraded to v7. Then you can load backup and crossfig will perform new config upgrade.

6

I hope you understand that when users have been helping you for a while by testing some rcs (rc5, rc6, now rc7) it is not really an option for them anymore to load a backup from v6, as that was made too long ago, and also a lot of work went into fine-tuning the configuration to run v7 in daily use.
The only thing I can realistically do now to cleanup config mistakes is export the config, edit it manually, and then reset the router and import that config.

So I presume that when I next do that (I intend to try it anyway to see if it fixes another issue) I can delete these lines?

/routing table
add fib name=main
add fib name=""
7

Device-mode: https://help.mikrotik.com/docs/display/ROS/Device-mode

8

Could you please update https://help.mikrotik.com/docs/display/ROS/v7+Routing+Protocol+Status.

Thanks

9

What if Crossfig allowed to import a v6 RSC and write a v7 RSC file in files. Using backup files would require a passwod to be provided.

10

please fix socks 5 problem
http://forum.mikrotik.com/t/socks5-not-working-in-routeros7/153414/1

11

I don’t suppose you can give us a rough estimate on when the container package will once again be available?

12

Unfortunately, we still can’t define one of the parameters of a Cake queue when creating it: direction. Right now if we don’t specify it, it defaults to egress.

It is clearly a bug since the parameter Autorate ingress is broken if ingress is not specifed.

See my post here: http://forum.mikrotik.com/t/v7-1rc3-development-is-released/151711/1

See the available parameters here (last parameter): https://www.man7.org/linux/man-pages/man8/tc-cake.8.html#SYNOPSIS

13

Hi,

I´m also waiting eagerly for the container feature for the brand new RB5009 I will receive next week. :slight_smile:
In the meantime: update of my HAP AC3 worked well from 6.49.
Thanks & regards!
Peter
Ps. we have the first snow in Vienna today so I grabbed 2 Socks this morning. 5 SOCKs would be an overkill!

14

Is proxy-arp on a bridge working back again?
What about IPSec/L2TP Road Warrior connection - does connection attempts stil reboots the CCR2004?

15

Thank you very much for your posts. We see them :slight_smile:
Currently we are polishing v6 features into v7. Once v7 will be released, we will look closely into features and improvements for functions, that were introduced in v7.x

16

Hopefully you will give priority to routing (e.g. BGP and also OSPF) in this, because there you removed the v6 features and introduced the v7 variant, but that is far from finished.
Lots of places are USING those routing features, and now have them in very unpolished state. I can sort of live with it on my home router but I certainly cannot update other routers in the network.

I fully understand those that want to have their CAKE and see it improved, but that is just a luxury food item compared to the core functionality of a router, routing and routing protocols.
And as it is now in v7.1rc7, BGP still logs silly things like:
12:36:25 route,bgp,info Connection closed
12:36:25 route,bgp,info Session *=0x3004c640

We need that improved. It should log WHICH session is closed, not a pointer value.
(this is only one example)

17

Still the same: http://forum.mikrotik.com/t/v7-1rc6-development-is-released/153185/1
Obviously that changelog doesn’t contain these fixes but I hoped it was fixed.

18

Radius not working still error “Radius Server not responding”

19

On ugprade RB760iGS from 6.49 to 7.1 my ipv6 stop working connection, i keep receiving valid ipv6 on router and on machines but traffic don’t flow.. don’t show any error log too, firewall it’s ok too.

When i roolback to 6.49 ipv6 back to work again.

What i can do?

20

You didn’t check the routes: http://forum.mikrotik.com/t/v7-1rc1-development-is-released/151250/1