Problem configuring Wireguard between RouterOS and Linux/OpenBSD

Hi, (Sorry, posting twice learning the forum)
Summary of my experience on Mikrotik router: I did receive an RB5009UPr+S+IN 3 days ago. I did configure Wireguard, OSPF, Radius, tons off VLAN and more… but I make a fatal mistake when “hardening” the configuration. I forgot about protocol 89, drop my OSPF routing and I needed to reset the router to factory setting. I was thinking, no-problem, it only took me 6 hours the first time to test everything… But no… now I am stuck at defining the Wireguard interface

Downloaded CHR and install it on a virtual X86 machine – Exact Same problem with WireGuard. (The RB5009UPr+S+IN is 2500 km from my location, not very convenient for testing)

Problems description : I define a WireGuard interface to establish a tunnel with an Internet server (linux). On the RouterOS, I define a “Persitent Keepalive” since the mikrotik products are behind NATed gateway. According to the Linux Server (and an instance of OpenBSD running on the same KVM Server), the WG tunnel get established.

The WG Interfaces are define with IP address LINUX-10.256.16.66/30(wg64) when the RouterOS-10.256.16.65/30 (wiregard2)… I can’t ping the remote end of the tunnel.
→ Ping from Linux to Router OS : The packet reach routerOS and is visible(but encrypted) with /tool/sniffer/quick interface=ether1… but never show up with /tool/sniffer/quick interface=wireguard2
→ ping from Router OS to Linux : /tool/sniffer/quick interface=wireguard2 see the packet… but /tool/sniffer/quick interface=ether1. never see it.
RouterOSConfiguration.txt (3.37 KB)

Was missing the Peer-> allowed address 0.0.0.0/0