RouterOS version 7.1beta6 has been released in public “development” channel!
What’s new in 7.1beta6 (2021-May-18 14:49):
!) added support for Let’s Encrypt certificate generation;
!) added L3 HW support for all CRS3xx devices;
!) added MLAG support for CRS3xx devices (CLI only);
!) ported features and fixes introduced in v6.49;
*) other minor fixes and improvements;
All released RouterOS v7 changelogs are available here:
https://mikrotik.com/download/changelogs/development-release-tree
Here is the user guide on Layer 3 Hardware Offloading for CRRS3xx devices:
https://help.mikrotik.com/docs/display/ROS/L3+Hardware+Offloading
no way!!!
!) added support for Let’s Encrypt certificate generation;
Documentation pleaseeeee.
I’m a bit disappointed, would like to see more focus on stability and features that not in V7 but are available in V6 instead of brand new features.
no needed found it:
certificate/enable-ssl-certificate dns-name=
Are there known stability issues? AFAIK they are just waiting for routing protocols to be finished to move out of beta.
running a lot of beta5 at non-essential places, can’t say that i’m having stability issues.
Hey Mikrotik,
What a fantastic job on lets encrypt, well done.
very easy to generate, just need few more tweaks, can you please add a name during the setup as each time its generate new file. something like:
certificate/enable-ssl-certificate dns-name=vpn.abcd.xyz name=Certificate
also it will be good if we can add multi dns like:
certificate/enable-ssl-certificate dns-name=vpn.abcd.xyz,MT01.abcd.xyz,sstp.abcd.xyz name=Certificate
they you can just use certificate in where ever you need it and it will automatically renew the same file name.
right now if you rename it it will generate new names the below:
0 KT Certificate vpn.abcd.xyz DNS:vpn.abcd.xyz 86d5977540a550d6b92d7777777777777777777
1 KT letsencrypt-autogen_2021-05-19T09:06:49Z vpn.abcd.xyz DNS:vpn.abcd.xyz af46ae12b3025900d6b94a444b948adc5418888888888888
Well Cake QoS crashes routeros but other than that it has been flawless for me. Well that and the CCR2004 has problems with mixed speeds SFPs but that’s part of the 6.49 fixes 
Now I’m only missing 4 addresses bridging mode on WifiWave2 to be perfectly happy
I don’t know of any specific instabilities but have heard rumors in the past about some instabilities.
Personally I’m waiting for IGMP-Proxy to be implemented because without that ROS is useless for me, like it is for millions of other users in for instance the Netherlands like me that need this to be able to watch TV on a fiber connection.
From newly added part about L3 HW offloading on Marvell DX3000/2000 Series chips: https://help.mikrotik.com/docs/display/ROS/L3+Hardware+Offloading
*1 Since total amount of routes that can be offloaded is very limited, prefixes with higher netmask are preferred to be forwarded by hardware (e.g /32 /30 /29 etc, > last route is 0.0.0.0/0 always processed by CPU> ), any other prefix that does not fit in the HW table will be processed by the CPU.
Does this mean that even if there is only a limited amount of connected/static routes present, the default route will still be processed by CPU?
Or does it apply only for a situation when the total routes number exceeds the maximum?
MLAG support for CRS3xx devices (CLI only); - how to test it ?
Does it crashes this beta (beta6) as well?
Hi there,
The fallback to CPU applies only to a situation when the total number of routes exceeds the maximum. Otherwise, everything can be routed by the hardware, including the default gateway(-s).
I know it was said that there are no plans for AR9300 to be supported in WiFiWave2 package. However are there any plans of supporting running both wifiwave2 and the normal wireless package alongside?
While 2.4Ghz is far from amazing having to pick between good 5Ghz and no 2.4 at all vs 5Ghz limited by the driver and 2.4 is rather bad. There are a plethora of devices which don’t support 5Ghz (e.g. almost every IoT). Lack of support for 2.4 during 7 beta period is imho perfectly fine but leaving it like that is slightly worrisome.
How are IP cloud names handled as wireguard endpoints? Are they like Firewall addresses that are resolved (dynamically) and checked/updated every xx seconds??
Great, thanks! That makes the huge new field of how to use the mentioned switches.
Probably you should rephrase the text in the wiki, so that this “always processed by CPU” don’t raise any questions.
why openwrt supported WPA3 on very old devices and WPA3 not supported in mikrotik devices ? like hAP lite, 951Ui,… why ???
I installed openwrt 21.01 on tp-link W8970 ( 2013 Product ) and it’s supporting WPA3, but in mikrotik… LMAO :))
Because RouterOS is made for all devices, but your example with OpenWRT is compiled specifically for one product only.
Until RouterOS doesn’t have NPK file for each model separately, it will always be bigger, as it has more drivers inside.
The documentation has been updated.
Thanks for the feedback!