WireGuard® is an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. It aims to be faster, simpler, leaner, and more useful than IPsec, while avoiding the massive headache. It intends to be considerably more performant than OpenVPN. WireGuard is designed as a general purpose VPN for running on embedded interfaces and super computers alike, fit for many different circumstances. Initially released for the Linux kernel, it is now cross-platform (Windows, macOS, BSD, iOS, Android) and widely deployable.
|comment (string; Default: )||Short description of the tunnel.|
|disabled (yes | no; Default: no)||Enables/disables the tunnel.|
|listen-port (integer; Default: 13231)||Port for WireGuard service to listen on for incoming sessions.|
|mtu (integer [0..65536]; Default: 1420)||Layer3 Maximum transmission unit.|
|name (string; Default: )||Name of the tunnel.|
|private-key (string; Default: )||A base64 private key. If not specified, it will be automatically generated upon interface creation.|
|public-key (string)||A base64 public key calculated from the private key.|
|running (yes | no)|
Whether interface is running.
|allowed-address (IP/IPv6 prefix; Default: )||List of IP (v4 or v6) addresses with CIDR masks from which incoming traffic for this peer is allowed and to which outgoing traffic for this peer is directed. The catch-all 0.0.0.0/0 may be specified for matching all IPv4 addresses, and ::/0 may be specified for matching all IPv6 addresses.|
|comment (string; Default: )||Short description of the peer.|
|disabled (yes | no; Default: no)||Enables/disables the peer.|
|endpoint-address (IP/Hostname; Default: )||An endpoint IP or hostname, can be left blank to allow remote connection from any address.|
|endpoint-port (integer:0..65535; Default: )||An endpoint port, can be left blank to allow remote connection from any port.|
|interface (string; Default: )||Name of the WireGuard interface the peer belongs to.|
|persistent-keepalive (integer:0..65535; Default: 0)||A seconds interval, between 1 and 65535 inclusive, of how often to send an authenticated empty packet to the peer for the purpose of keeping a stateful firewall or NAT mapping valid persistently. For example, if the interface very rarely sends traffic, but it might at anytime receive traffic from a peer, and it is behind NAT, the interface might benefit from having a persistent keepalive interval of 25 seconds.|
|preshared-key (string; Default: )||A base64 preshared key. Optional, and may be omitted. This option adds an additional layer of symmetric-key cryptography to be mixed into the already existing public-key cryptography, for post-quantum resistance.|
|public-key (string; Default: )||The remote peer's calculated public key.|
|current-endpoint-address (IP/IPv6)||The most recent source IP address of correctly authenticated packets from the peer.|
|current-endpoint-port (integer)||The most recent source IP port of correctly authenticated packets from the peer.|
|last-handshake (integer)||Time in seconds after the last successful handshake.|
|rx (integer)||Total amount of bytes received from the peer.|
|tx (integer)||Total amount of bytes transmitted to the peer.|
Consider setup as illustrated below. Two remote office routers are connected to the internet and office workstations are behind NAT. Each office has its own local subnet, 10.1.202.0/24 for Office1 and 10.1.101.0/24 for Office2. Both remote offices need secure tunnels to local networks behind routers.
First of all, WireGuard interfaces must be configured on both sites to allow automatic private and public key generation. The command is the same for both routers:
Now when printing the interface details, both private and public keys should be visible to allow exchange.
Any private key will never be needed on the remote side device - hence the name private.
Peer configuration defines who can use the WireGuard interface and what kind of traffic can be sent over it. To identify the remote peer, its public key must be specified together with the created WireGuard interface.
Lastly, IP and routing information must be configured to allow traffic to be sent over the tunnel.
The default RouterOS firewall will block the tunnel from establishing properly. The traffic should be accepted in "input" chain before any drop rules on both sites.
Additionally, it is possible that "forward" chain restricts the communication between the subnets as well, so such traffic should be accepted before any drop rules as well.