kiichan/WireGuard-conf
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Update README.md

Browse source
This commit is contained in:
kiichan 2023-11-19 16:44:58 -06:00
parent 6832a08595
commit 1c79dcfdaa
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -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: 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 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