There are many guides for how to build one on DigitalOcean, Linode, AWS or any other cloud hosting provider. This can be any computer with a public IP address running Wireguard. One MikroTik router configured as a WireGuard peer.One WireGuard peer on the public network serving as a gateway for the rest of the peers.This article assumes the following network elements: Accessing peers behind NATed connections such as mobile phones and most home internet connections isn’t possible without connecting through a peer on the public internet unless you want to attempt some kind of UDP hole punching. That is why most WireGuard networks require at least one “peer” with a real public IP address that is accessible on the public internet to serve as a gateway. This is called Network address translation or NAT. Only when your device initiates a connection to a remote service such as (a TCP connection), do all of the routers on the way establish a connection path back to your device. In practice, most consumer devices today are on some kind of private ISP network and can’t be addressed from the public internet which is good for security reasons. With WireGuard everything is a “peer” which often causes confusion about how to configure each device on the network.

Mikrotik added official support for WireGuard in version 7 of RouterOS. All other setups are outside the scope of this document and can be designed by following this awesome WireGuard documentation. This post focuses on enabling remote access to Mikrotik routers and the attached networks. Connecting several networks over the public internet.Connecting to your home network while on the road for home automation and safe internet access.Managing router configuration remotely behind NATed networks such as mobile connections.WireGuard can be used for a lot of things:

Raspberry pi 4 routeros