Sadly not. Not sure if my configuration was incorrect or if my ISP was doing something non-standard.

At this moment in time, it's a matter of convenience - a nice to have. In time, who knows how long, it will be necessary to add new key types. I think ROS should be keeping up with these new key types, and the ROS7 beta would be a good opportunity for them to do so. It's good to get ahead of the cur...

I have another WG interface set up for road-warrior purposes and that's working great btw (except it doesn't process allowed-address properly on Webfig, but I think you're aware of that)

A thread was posted a few years back here: https://forum.mikrotik.com/viewtopic.php?p=628350 It would be great if ed25519, and perhaps other related key types such as nistp256 and so on were supported. None of my current keys were recognized on import, and thus I have no choice but to create a new k...

v7beta3 here. Just a minor usability improvement. Haven't confirmed if behavior exists in stable.

In the log viewer in WebFig, the 'Time' column is sortable, however the '#' column should also respond to sorting but it does not.

I would like to see this implemented natively at some point in the near future, along with more general improvements to IPv6. It seems to be adopted in Germany and Japan at the moment, but I expect it will continue to gain traction as more ISPs begin to make their moves to an IPv6-first network. In ...

The peer config for Wireguard in beta 3 appears to accept IPv6 addresses for the endpoint-address var, but the resulting peer object's endpoint-address content is empty. This occurs in CLI and Web. IPv6 addresses either need to be prevented from being entered, or parsed properly to the Wireguard too...