Difference between revisions of "Wireguard"
From Briki
(→Notes) |
|||
| Line 20: | Line 20: | ||
=== Notes === | === Notes === | ||
| − | + | ==== Interface ==== | |
| − | ; | + | ;Address |
| − | : the address of the server and the subnet that will be used for the private network | + | :the address of the server and the subnet that will be used for the private network |
| − | ; | + | ;ListenPort |
| − | : the port on which the server will listen for connections (51820 is generally used) | + | :the port on which the server will listen for connections (51820 is generally used) |
;PrivateKey | ;PrivateKey | ||
:the private key for the server (used to authenticate traffic going back to the peer) | :the private key for the server (used to authenticate traffic going back to the peer) | ||
| − | + | ==== Peer ==== | |
Revision as of 06:07, 15 May 2024
Follow these guides:
- https://www.freecodecamp.org/news/build-your-own-wireguard-vpn-in-five-minutes/
- https://www.wireguardconfig.com/
But note that `AllowedIPs` on the client should be `AllowedIPs = 0.0.0.0/0, ::/0` to use as a VPN for everything (more detail here: https://docs.pi-hole.net/guides/vpn/wireguard/route-everything/)
Example Server Config
[Interface] Address = 192.168.130.1/24 ListenPort = 51820 PrivateKey = PRIV123 [Peer] PublicKey = PUB456 AllowedIPs = 192.168.130.2/32
Notes
Interface
- Address
- the address of the server and the subnet that will be used for the private network
- ListenPort
- the port on which the server will listen for connections (51820 is generally used)
- PrivateKey
- the private key for the server (used to authenticate traffic going back to the peer)
