RouterOS version 7.1rc4 has been released in public “development” channel!
What’s new in 7.1rc4 (2021-Sep-20 13:18):
*) improved filesystem and configuration storage stability;
*) show “expired password” prompt for users with blank password;
*) other fixes and improvements;
All released RouterOS v7 changelogs are available here:
https://mikrotik.com/download/changelogs/development-release-tree
Any specific improvements to MPLS or BGP?
Changelog couldn’t be more vague even if you tried…
Installed and running okay on RB2011 - would love some detail on the improvements to test.
My chr test system can no longer start the container that worked on rc3. No debug log output at all.
Upgraded to 7.1rc4, IPSec hardware acceleration for aes-256 gcm is still not working on x86_64 CHR and worked just fine with the same config on 6.48.4, same virtualization environment.
no changelog in
How to explore and get files from container mounts now that they are stored as “container store” and not as directories/files as before?
Fastest and easiest way is via FTP.
ReSize of terminal destroy MikroTik logo/code/output
Still slow paste of code.
Removing and re-adding the veth interface and container allowed it to start again. Containers should be able to start properly after an OS upgrade.
mAPLite (7.1rc3 downgraded to rc2, now upgraded to rc4):
Still no IPv6 prefix via DHCPv6 if PPPoE interface is VLAN tagged on RB5009:
/interface vlan
add interface=ether1 name=FTTH vlan-id=7
/interface pppoe-client
add add-default-route=yes interface=FTTH name=TELEKOM user=xxx#0001@t-online.de
/ipv6 dhcp-client
add interface=TELEKOM pool-name=GUA-pool6 request=prefix use-peer-dns=no
Export creates code, that import can not read (starting with 7.1rc3):
Export:
/ip dhcp-client
add add-default-route=no disabled=yes interface=FFNK script=":if (\$bound = \"\
Import:
[admin@router] > import file-name=export.rsc verbose=yes
#line 1
/ip dhcp-client
#line 2
add add-default-route=no disabled=yes interface=FFNK script=":if (\$bound = \"\
expected end of command (line 1 column 75)
[admin@router] >
Still not able to specify the direction (ingress/egress) for the Cake queue. Defaults to egress. So every Cake queue we create, however it is used as (ingress/egress), its internal algorithm thinks it is used as egress…
EDIT: grammar
I am not playing the c3,c4 game but if I was, I would not be upgrading based on the improvement or changes which are frugal to almost none.
So for all the people complaining it still doesnt do X and Y, why do you ? They didnt state it was fixed?
Something needs to change, and that clearly is a detailed list of actual changes to existing functionality.
I can understand not noting clean up code or spelling fixes, stuff either to benign or not visible to the users…
In that way people can make rational decisions on whether or not to try the next c upgrade.
Am I missing some logic here?
Even better communication, and a standard that needs to be reached is the following.
RC -X REPORT
ISSUES/FUNCTIONALITY FIXED
ISSUES/FUNCTIONALLY IMPROVED
ISSUES UNDER WORK FOR NEXT C release
ISSUES TO BE FIXED BEFORE FINAL RELEASE
ISSUES FOR IMPLEMENTATION AFTER FINAL RELEASE
ISSUES WILL NOT BE ADDRESSED IN SHORT OR LONG TERM ( without serious cash donations 
)
Have you tried to attach the vlan interface to the bridge and use the vlan filtering to allow only this vlan on that particular port?
I’ve seen the opposite quite often.. “hey this quite major thing is fixed, but it wasn’t in the changelog”!
The LEDs now working as the user said above, is another example that wasn’t in the changelogs.
So I now shoot everything to the wall and see what sticks.
I am a software engineer and I don’t approve of Mikrotik practices regarding the software cycle, but they make good hardware. It would benefit them first, having a good change log.
On RC7 my IKEv2 connection to my VPN providers keeps working and it look that I can stay for a while on v7 now.
On two routes a automatic ECMP is created while that is not intention and finding the off switch for that is unknown to me. It seems that everything a /24 range is seen as so.
Scripting is still tricky because some parts are not working as before and checking a syntax by pasting into Terminal is taking AGES. For the rest I am a happy bunny and Unbound say hi also an no more pull-overs knitted till now.
Update: still running and smoother than before. On the PPPoE not able to use MTU 1500, I switch all MTU fields in PPPoE off and it now connects at 1492. That is better than the 1480 I got before on v7.