RouterOS version 7.1beta3 has been released in public “development” channel!
What’s new in 7.1beta3 (2020-Dec-02 15:59):
!) added support for “Cake” and “FQ_Codel” type queues;
!) added new experimental wireless package “wifiwave2” for ARM devices with more than 256 MB of RAM (CLI only);
*) bgp - template parameters are now exposed in connection;
*) chr - added support for SR-IOV
*) routing - added “route”, “routing table”, “route rules” and BGP configuration migration from RouterOS v6 after upgrade;
*) routing - renamed “instance” menu to “id”;
*) other fixes and improvements;
Hope this will also stop the router crashing when you change the MTU of an interface.
Update: I could change de MTU but sadly not the one I wanted to. The PPPoE dropped back to 1480 and manually I could set it to 1492 to a bit be closer to the 1500 that I can use in 6.48.
Routing was changed (expected), routing labels where set main and when I wanted to traceroute there where two routing tables main in the list. Both worked but it is confusing this way. After I corrected all the changed routing marks it still not work and I could only ping/traceroute directly from the router to 8.8.8.8.
My external IP I could not set as preferred source on my PPPoE connection or I had to make my own static routing entry. All my internal routing was also dead so no in fun testing this way.
Looking forward to try 7.1Beta4 somewhere in 2021. For now I am back to 6.48.
Update 2: hanging in there like a pit-bull I tried again. The nexthop in routing displays all unreachable, manually removed the double main next to default dynamic main and the blank one. Exporting to a RSC file does not complete and the last complete section is: /ip service and the next service /system time is not present in the file and also the rest of the export.
I could partly activate the internal routing by setting rules but it still worked only partly.
NAT64 and/or DNS64 for the beta4, please, and you would be the best router software in the world! That would give a huge boost to IPv6-only internal networks and prevent double work for dual-stack management.
Lost lte1 interface after upgrade from v7.1beta2 to v7.1beta3. Sierra Wireless MC7430 in wAP R. Log file reports ‘reply timeout for: AT E0 V1’ (see screenshot).
fq_codel, SR-IOV and 802.11ac Wave2 support are some interesting additions though!
Unfortunately, reducing the size of the driver and its memory usage further was not found to be feasible at this point. Perhaps when RouterOS 7 and the wifiwave2 package come out of beta, further optimizations can be made.
No way this driver would fit without replacing the old driver with the new one. There’s barely any space left on hAP ac2. And if by replacing there’s still not enough space left then that means there’s no point to buy any of the 16MB devices because none of them would get this new driver. Especially if it stays like this and it will be a separate package. Maybe there’s debug symbols still left in. After all this is still an experimental driver. People has been asking for a Wave2 driver for ages and in the end they wouldn’t be able to get it. If I am wrong please correct me.
Almost every device out there based on ipq4018/4019 has atleast 256MB of RAM.
With a few exceptions, like RT-AC58U which struggles to not throw errors because of the very limited memory available out of the 128MB total.
So I wouldn’t keep my hopes up to see it running in the future on lower requirements than the ones posted here today.
This was expected.
That would give a huge boost to IPv6-only internal networks and prevent double work for dual-stack management.