Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
linux_router:wireguard [2023-06-18 Sun wk24 15:41] – [Docker Wireguard Setup] baumkp | linux_router:wireguard [2025-05-24 Sat wk21 21:09] (current) – baumkp | ||
---|---|---|---|
Line 1: | Line 1: | ||
{{tag> | {{tag> | ||
=====Wireguard VPN access from WAN to LAN====== | =====Wireguard VPN access from WAN to LAN====== | ||
+ | <fc # | ||
+ | |||
I use 2 forms of vpn (virtual private network) on my home server. | I use 2 forms of vpn (virtual private network) on my home server. | ||
- VPN to gain remote secure private access to my home LAN from the WAN (internet). //This is the one I am describing here.// | - VPN to gain remote secure private access to my home LAN from the WAN (internet). //This is the one I am describing here.// | ||
Line 29: | Line 31: | ||
===Greatest Difficulties in Setting=== | ===Greatest Difficulties in Setting=== | ||
- | Wireguard is not a chatty. | + | Wireguard is not chatty, this actually is a security feature. It is important that the setup information is done correctly, in particular the private and public keys. Also the allowed ips is important. On the server side it is set to the main VPN ip address. On the client side it needs to be set to include ip addresses that are allowed to be access on the client side. |
Some tools that help fault find: | Some tools that help fault find: | ||
* On the server side: '' | * On the server side: '' |