Hello,

Yesterday I was configure Wireguard for the first time on my RB5009 running the latest version of RouterOS 7.14.3 (I also attempted on 7.14.2, same bug) and I noticed that the private key when being autogenerated on a peer is always the same.

Here is a quick video (I cannot attach video files to the topic):
https://cdn.karbust.com/BedO8/dIROhUtO55.mp4/raw

As you can see from it, the private key is always "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEA=", but it always generates a different public key, thus making connections from clients fail when handshaking.

I generated key pairs from this website and then I could establish handshake, as intended. https://wg.orz.tools

This doesn't happen on the server's key pair generation, only on the peer from what I can tell.

This appears to be a bug to me, not sure if this is the best place to report it or not.

not sure if this is the best place to report it or not.

If you have a reproducible bug like this, file a support request at https://help.mikrotik.com/servicedesk/servicedesk .This is a forum of fellow users that can help you with configuration questions or issues but cannot fix bugs, and Mikrotik staff does keep an eye on the forum but there is no guarantee they would spot everything.

The first thing they will ask for will be the supout.rif file showing the issue so attach it already when opening the ticket.

not sure if this is the best place to report it or not.

If you have a reproducible bug like this, file a support request at https://help.mikrotik.com/servicedesk/servicedesk .This is a forum of fellow users that can help you with configuration questions or issues but cannot fix bugs, and Mikrotik staff does keep an eye on the forum but there is no guarantee they would spot everything.

The first thing they will ask for will be the supout.rif file showing the issue so attach it already when opening the ticket.

Thank you for the tip. I filed the support request. It is reproduceable through the GUI (as shown in the video), no idea about the CLI commands to reproduce it as I didn't test it through there.

Hello

Same problem on ROS 7.14.3

Best regards

As I'm not comfortable installing a non-production final release, I'm unable to test if it is working. Here is the message I got from support:

I've also been running into this issue. I spent a couple hours trying to get it to work.

I'm new to wireguard so I'm glad I found this and it wasn't just a knowledge issue.