yeah OSFP routing stopped working correctly with 7.13rc2 :/
The routing table is populated as usual, but packets are not routed (tested on ax3)
ovpn - added "tls-auth" option support for imported .ovpn profiles
If the remote server I'm connecting to had used Wireguard, I would surely use it. But it is about MT connecting as a client to a remote OpenVPN server, and I do not have any alternative methods available.However I recommend you to use wireguard which is natively supported
Why it was removed? I'm looking for something similar as Mikrotik OpenVPN as a client still does not support TLS auth<REMOVED>
Would this finally solve problem with client authentication via static key?*) ovpn - added support for OVPN server configuration export and client configuration import from .ovpn file;
Enabled of course. That's why I mentioned this problem in 7.5 thread, I've been using Capsman for a while..With local forwarding activated or disabled? If you want speed you need to use local forwarding in Capsman.
VPLS has been broken for a long time in ROS7, I've disabled it and switched to VxLAN which has been working well so far (and it's easier to use too).Mikrotik this morning sent me an internal test version and it has fixed my issue - no more VPLS crash.
Do you use CAPsMAN? If so, the fix for that problem will be available soon (I'm just testing the pre-release version and it's already fixed there).I had random reboots with RB2011 and 7.2.x, you're ok?RB1100 and RB2011 upgraded from 7.2.1 without problems
Well, that little low-power box is still useful for IoT (sorry, obviously a new term for you).Out of the window goes your plan to use the RB941-2nD as the preferred routing platform for your enterprise!Just noticed - MPLS subsystem is removed from RB941-2nD
I do not mind testing it, just the description is too vague to understand what was broken exactly. Could you describe a scenario that would break the router with 7.2?7.2.1 is in testing to test this one change only. You can keep using 7.2 it did not disappear.
Well, that's not clear. According to Wiki the spanning tree protocol applies to CSR models, which is not my case. Are you saying every router would get that change?Did you read the release notes? Noticed anything about spanning tree? Did you try to disable spanning tree on the bridge?