From 1c79dcfdaaf319a44261b14278b80106414c211a Mon Sep 17 00:00:00 2001 From: kiichan Date: Sun, 19 Nov 2023 16:44:58 -0600 Subject: [PATCH] Update README.md --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index 904c04c..92e8af9 100644 --- a/README.md +++ b/README.md @@ -83,3 +83,9 @@ Congratulations, your network traffic should now be encrypted between your devic You will likely want to set WireGuard to start on server startup. For `systemd`-based systems, run the following: sudo systemctl enable wg-quick@wg0.service + +## Troubleshooting + +If the client connection gets routed through the server, but there is no access to the remote LAN, then what's likely happening is that there is another rule on the client system that is interfereing with the `0.0.0.0/0` declaration. To get around this, add another entry to the `AllowedIPs` in the client's configuration. For example, if the remote LAN uses the 192.168.1.0/24 address space, then the following would allow access to that LAN: + + AllowedIPs = 192.168.1.0/24, 0.0.0.0/0