Remember to make backup/export files before an upgrade and save them on another storage device;
Make sure the device will not lose power during upgrade process;
Device has enough free storage space for all RouterOS packages to be downloaded.
What's new in 7.1 (2021-Dec-01 16:07):
MAJOR CHANGES
!) updated Linux Kernel based on version 5.6.3;
!) completely new NTP client and server implementation;
!) completely new User Manager implementation;
!) merged individual packages, only bundle and a few extra packages remain;
!) new Command Line Interface (CLI) style (RouterOS v6 commands are still supported);
!) support for Let's Encrypt certificate generation;
!) support for REST API;
!) support for UEFI boot mode on x86;
NETWORKING
!) CHR FastPath support for "vmxnet3" and "virtio-net" drivers;
!) support for "Cake" and "FQ_Codel" type queues;
!) support for IPv6 NAT;
!) support for Layer 3 hardware acceleration on all CRS3xx devices;
!) support for MBIM driver with basic functionality support for all modems with MBIM mode;
!) support for MLAG on CRS3xx devices;
!) support for VRRP grouping and connection tracking data synchronization between nodes;
!) support for Virtual eXtensible Local Area Network (VXLAN);
ROUTING
!) completely new BGP implementation with performance improvements;
!) completely new IPv6 stack;
!) completely new MPLS implementation with interface lists, multipath and LDPv6 support;
!) completely new OSPF implementation with performance improvements;
!) completely new routing filtering with script-like rule syntax, RPKI support and large and extended community filtering;
!) support for IPv6 ECMP and VRF (including VRF-lite);
!) support for IPv6 recursive routing and policy routing;
VPN
!) support for L2TPv3;
!) support for OpenVPN UDP transport protocol;
!) support for WireGuard;
!) support for ZeroTier on ARM and ARM64 devices;
WIRELESS
!) completely new alternative wireless package "wifiwave2" with 802.11ac Wave2, WPA3 and 802.11w management frame protection support (requires ARM CPU and 256MB RAM);
!) completely new alternative wireless package “wifiwave2” with 802.11ac Wave2, WPA3 and 802.11w management frame protection support (> requires ARM CPU and > 256MB RAM> );
[quote=strods post_id=894500 time=1638446386 user_id=72415]
Due to the fact that we have made a huge progress in RouterOS v7 stability, we have decided to release it in the testing channel.
[/quote]
Ok so this is basically 7.1rc7 with a new version number? No need to install it when you already have 7.1rc7?
[quote]Please test it where you can and report your feedback on this forum page[/quote]
Did you read all feedback on the previous v7.1rc forum pages and at least put the remarks about lacking or nonworking sub-features on a work-to-do list? [quote]ROUTING
----------------------
!) completely new BGP implementation with performance improvements;[/quote]
that looks exciting but unfortunately there are some critical omissions in the current status that make it unfit for production use.
and we all know that until it is fit for production use, it cannot really be tested either.
I have a RB4011 which fulfills the requirements for wifiwave2 but still I cannot use it because it doesn’t co-exist with the normal package that is required to support 2.4 GHz WiFi.
Or did that change?
CAPsMAN does not support WW2 at the moment.
Note that WW2 is planned for future devices, that’s why there are additional requirements in terms of hardware.
What I said on the 7.1rc7 topic (http://forum.mikrotik.com/t/v7-1rc7-development-is-released/153617/1), still valid, the RB4011 switch is still useless.
I’m wondering if the wireguard peer IPv6 bug is still present, probably yes, as Mikrotik even did not acknowledged it …
Please give us more detailed changelogs, even if it only says briefly like you wrote now, if we have related issue, we than know to flash new version and check if issue is resolved..
Also allowed-address “::/0” cannot be set from WinBox, it doesn’t get saved. It works from CLI only.
I know I’ve written all this in the support ticket regarding WireGuard, but others might wanna know about the issue.
And yes @soheilsh, socks5 is still broken.
I think that everyone would be happy to have, somewhere the full changelog, because sometimes, there is some “edge-case” that may affect someone and that person could see if this was solved…
Long story short, L3 Fastpath (FastTrack) support for vlan-filtered bridges is in development. It is a new feature, not a bug. While we understand your frustration, please consider that new features cannot be added during the stabilization phase of the project. We are hoping to deliver this feature in the upcoming v7 versions.
