v7.1rc2 [development] is released!

FastPath is a PMD hook into a userspace forwarding plane.

OpenVPN and ZeroTier are already userspace based, WireGuard is using the kernel module I believe.

Mikrotik could technically add FastPath support to any of these as long as they use the Userspace version rather than the Kernel module.

Will they? I have no idea… The developer time would be better spent on an IPv6 FastPath module, FastPath FIFO shaper and improving performance of the existing FastPath modules.

On hAP ac^2 if I set “strong-crypto=yes” in IP/SSH/ and try to export config of entire device, it takes a very long time and finally in file is error about SSH and this section is not exported:

......
set api disabled=yes
set winbox port=8291
set api-ssl disabled=yes
#error exporting /ip/ssh
/system clock
set time-zone-name=Europe/Warsaw
/system identity
.......

Config view from console :

[admin@Testv7] /ip/ssh> pr
           forwarding-enabled: no
  always-allow-password-login: no
                strong-crypto: yes
            allow-none-crypto: no
                host-key-size: 4096
[admin@Testv7] /ip/ssh>

I can not set a private pre-shared key in wireless access list. This command does not change anything:

/interface/wireless/access-list/set private-pre-shared-key=testing123 [ find ]

i’m also on hapac2, i can export config just fine with enabling strong-crypto, the only caveats is I should backup the config without password otherwise the backup file won’t be restored successfully, already filed a ticket on this weird bug

Interesting, I also have discovered how to reproduce. It happens if you set key size to 4096 and try to export config. In my case it caused to take ~2mins and 40% CPU load(and error line in exported file).
Setting key size to 2048 and export work fast and fine, then if you set again 4096 after that it also works.

I just upgraded Winbox to 3.29 and ROS to v7.1rc2 (tile). Winbox no longer has capsman in its highest level categories, but I still had a capsman window open from before the upgrades.
Additional info: I restored winbox 3.28 from a backup but it will not run with v7.1. I downgraded back to 6.49b54 and winbox 3.29 has capsman so the problem is 7.1rc2. I also did not see dude in 7.1rc2 but do not know if it is supposed to be there. I will wait for v71rc3 and try again.



if you enabled default route in the PPPoE login, do not set it in dhcpv6-client.

That seems to have cured it.

So I was having the same issue as some others where the reboot cleared the configuration and also prevented backups from working.

I had a disabled package named wifiwave2.

I removed that package and everything works as expected.

Reboots and backups are working for me now.

CRS328 series router.

I hope the information helps.

I agree, that would be super.

MTU >1500 is still unsupported on RB4011 on sfp+ port.

This was reported back in the RC1 thread (another user opened a SUP). Even with a netinstall it is not possible to upgrade past beta 6.

I did not noticed that. That is maybe the cause the PPPoE dropped back to 1480 after connecting at 1500.

When will you turn on bfd in ros7?

Yes, that is important for us too! Or when BFD is considered to be deprecated, some replacement for it to quickly signal loss of a link used for BGP.

BFD is currently work in progress.

Are there any plans to bump the kernel version up to a currently supported one (say 5.10 LTS)? 5.6 seems like an odd choice to me.

My Hap ac^3 just reset itself after about 2 days of operation with cake and wifiwave2. Seems like this version still have some bugs to iron out.

Does wifi V2 support VLAN tagging?

Please add an option to /import, or make it the default behavior, to print the imported line when an error occurs (in addition to the error message), and to continue the import.
As it is now, it is very difficult to import rsc files as even with the slightest difference in features the import stops and prints only the error message (like “item already exists”) without context.
The “verbose” option can be used, but it prints everything and it still does not continue after the error so repeated attempts with from-line option are required :frowning:

i agree fully