Both remote offices need secure tunnels to local networks behind routers.įirst of all, WireGuard interfaces must be configured on both sites to allow automatic private and public key generation. Two remote office routers are connected to the internet and office workstations are behind NAT. The total amount of bytes transmitted to the peer.Īpplication examples Site to Site WireGuard tunnelĬonsider setup as illustrated below. The total amount of bytes received from the peer. Time in seconds after the last successful handshake. The most recent source IP port of correctly authenticated packets from the peer. The most recent source IP address of correctly authenticated packets from the peer. This option adds an additional layer of symmetric-key cryptography to be mixed into the already existing public-key cryptography, for post-quantum resistance. 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.Ī base64 preshared key. Persistent-keepalive ( integer:0.65535 Default: 0)Ī seconds interval, between 5 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. Name of the WireGuard interface the peer belongs to.

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.Įndpoint-address ( IP/Hostname Default: )Īn endpoint IP or hostname can be left blank to allow remote connection from any address.Įndpoint-port ( integer:0.65535 Default: )Īn endpoint port can be left blank to allow remote connection from any port. 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. Allowed-address ( IP/IPv6 prefix Default: )

Mikrotik wireguard firewall