Switching "Contry" to "Russia3" helped me.

960PGS
/system/health/print - nothing print, no temperatures, no voltage..

I've tried to connect like this to a dozen of a servers and everything worked well enough for me. I've been wondering is it possible to generate keys on mikrotik for wireguard peers? The Packet Sniffer on Mikrotik itself does not see any attempts to communicate with the server at all, filters by IP...

follow the instructions from here : https://rickfreyconsulting.com/wireguard-site-to-site-vpn-example/ and: https://www.cyberciti.biz/faq/ubuntu-20-04-set-up-wireguard-vpn-server/ # model = 960PGS # serial number = CB540BCF02D3 /interface wireguard add listen-port=8526 mtu=1420 name=3001 /interface ...

What is a "white IP"?

Without using NAT. Without port forwarding, the interface address is not in the private or gray IP range.
Linux - conditionally server, Mikrotik - peer.

But Wireguard with Mikrotik behind NAT is not a problem for me.

Share a secret )

Wireguard does not connect from Mikrotik behind NAT to a Linux server with a white IP.

It looks like there will be no backport from version 7 to version 6. Support hints at switching to version 7.

I found this topic when it was linked in the 6.47.2 release topic. I am using 2 of these E3372 sticks, one on RB750Gr3 and another on RB962UiGS-... and both of them work OK on RouterOS 6.47.1 Yes, E3372h-153 works fine. But last model - E3372h-320 - very not fine... LTE link up/down every 2-3 sec. ...

I confirm the problem with the new Huawei modems that Mikrotik can't digest. It is still difficult to work with the RouterOS beta - some of the functionality does not work or does not work correctly. Developers - please respond, will there be a backport from 7 beta at least in the test 6.48?