From 0b06c5ea2d8ed2749445ff3a5bf36ef47e301730 Mon Sep 17 00:00:00 2001 From: DoTheEvo Date: Sun, 3 Apr 2022 18:13:26 +0200 Subject: [PATCH] update --- wireguard/readme.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/wireguard/readme.md b/wireguard/readme.md index c1e7755..5e6b3c0 100644 --- a/wireguard/readme.md +++ b/wireguard/readme.md @@ -112,7 +112,7 @@ This configuration when run creates a new `wg0` network interface on the machine * **AllowedIPs** - IP addresses that you want to reach at the other end of the tunnel.
When `wg-quick` is run with these defined, a route is added in to the machines network stack that makes sure that if something wants IP address defined here, - it is send to `wg0`.
+ it is send through the wireguard tunnel and not the default gateway.
Two peers can not have the same IP.
In this case we want to define only single IP of the client as being accessible, allowed through. @@ -166,10 +166,10 @@ Endpoint = 63.123.113.495:51820 * **PublicKey** - public key of the server * **AllowedIPs** - IP addresses that you want to reach at the other end of the tunnel.
When `wg-quick` is run with these defined, a route is added in to the network stack - that makes sure that if something wants IP address defined here, it is send to `wg0`.
+ that makes sure that if something wants IP address defined here, + it is send through the wireguard tunnel and not the default gateway.
Two peers can not have same IP set in there.
- In this client case, we want to be able to communicate with the wireguard server, - so its IP is added, but also the entire local network at the end of the tunnel, + In this client case, we want to be able to communicate with the entire local network at the end of the tunnel, so the entire range is added. * **Endpoint** - public IP at which to find the WireGuard server across the internet