From 53b0d2f901b5e36b600a82f753a0f165dcbf40dd Mon Sep 17 00:00:00 2001 From: Jake Howard Date: Thu, 5 Mar 2020 17:58:31 +0000 Subject: [PATCH] Fix wireguard config --- content/posts/wireguard-getting-started.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/posts/wireguard-getting-started.md b/content/posts/wireguard-getting-started.md index dff32e7..3e42f88 100644 --- a/content/posts/wireguard-getting-started.md +++ b/content/posts/wireguard-getting-started.md @@ -58,7 +58,7 @@ ListenPort = 51820 # The port for wireguard to listen on (51820 is the standard # Specify 1 "Peer" block for each connecting device [Peer] PublicKey = # The clients public key -AllowedIPs = 10.1.10.0/24 # The IP and mask the client should be assigned +AllowedIPs = 10.1.10.2/32 # The IP and mask the client should be assigned ``` Yes, that's really it! This isn't just a simple config, Wireguard just has a super simple configuration! @@ -73,7 +73,7 @@ PrivateKey = # The clients private key [Peer] PublicKey = # The servers public key Endpoint = :51820 # The IP (or hostname) of the server, along with the port wireguard is listening on -AllowedIPs = 10.1.10.2/32 # The IPs and masks the client should route through the tunnel +AllowedIPs = 10.1.10.2/24 # The IPs and masks the client should route through the tunnel PersistentKeepalive = 25 # Ensure connections remain active, especially useful over NAT ```