Yes. I had an old experimental setup: in a computer at home one peer, a port directed in the router, and I used to test from my laptop.
Now I transfered my laptop configuration to my mikrotik travel router and it started working instantly.
I am very busy currently but I’m really looking forward to setting up a proper network…
What I mostly love is that it is not chatty at all. Basically the “dial-on-demand” characteristic of the ppp VPNs is built-in (unless you set up keepalive). And the connection is restored in just two one roundtrip.
Do you have the CLI commands used? I tried to replicate the config I have in my Mikrotik in the Peer settings but I don’t see anything in my server, no connection request. Also, checking in the Wireguard Documentation, when connecting to a server, the interface should not have a Listening Port setting. But in order create an interface in Mikrotik I do need to provide a Listening Port which kinda goes against the official Mikrotik documentation.
Lastly, being able to provide a host name instead of an IP address would be crucial…
If some one is interested and finds useful, I put together a quick script that gets a Wireguard interface and updates the endpoint IP address according to the IP address the domain resolves. This is great for who is running their wireguard server behind a Dynamic IP address.
Hopefully we have a cleaner solution in the next beta version with the endpoint being able to be provided as a host name.
:local resolvedIP [:resolve "<domain>"];
:local interface 0;
:local currentIP [/interface/wireguard/peers get $interface endpoint];
:if ([:find $currentIP $resolvedIP] < 0) do={
/log info "IP Changed to $resolvedIP"
/log info ($resolvedIP . ":51820");
/interface/wireguard/peers set $interface endpoint=($resolvedIP . ":51820");
/log info "Wireguard Peer $interface endpoint updated";
/interface/wireguard disable $interface
/interface/wireguard enable $interface
}
