-
-
Save lanceliao/5d2977f417f34dda0e3d63ac7e217fd6 to your computer and use it in GitHub Desktop.
| [Interface] | |
| Address = 10.200.200.3/32 | |
| PrivateKey = [Client's private key] | |
| DNS = 8.8.8.8 | |
| [Peer] | |
| PublicKey = [Server's public key] | |
| PresharedKey = [Pre-shared key, same for server and client] | |
| Endpoint = [Server Addr:Server Port] | |
| AllowedIPs = 0.0.0.0/0 | |
| PersistentKeepalive = 21 |
| [Interface] | |
| Address = 10.200.200.1/24 | |
| #SaveConfig = true | |
| PostUp = iptables -I FORWARD 1 -i wg0 -j ACCEPT; iptables -I FORWARD 1 -o wg0 -j ACCEPT; iptables -t nat -I POSTROUTING 1 -s 10.200.200.0/24 -o eth0 -j MASQUERADE | |
| PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -D FORWARD -o wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -s 10.200.200.0/24 -o eth0 -j MASQUERADE | |
| ListenPort = 10086 | |
| PrivateKey = [Server's private key] | |
| [Peer] | |
| # Client 1 | |
| PublicKey = [Client's public key] | |
| AllowedIPs = 10.200.200.2/32 | |
| PresharedKey = [Pre-shared key, same for server and client] | |
| [Peer] | |
| # Client 2 | |
| PublicKey = [Client's public key] | |
| AllowedIPs = 10.200.200.2/32 | |
| PresharedKey = [Pre-shared key, same for server and client] |
How can get a CL ID
$ wg genkey | tee privatekey | wg pubkey > publickey
Wireguard doesn't have a server-client model. Terminology is incorrect
Wireguard doesn't have a server-client model. Terminology is incorrect
for some users purposes (such as mine), its good enough.
Oh, and its the terminology used by Red Hat, so again, its good enough.
On the wg-server.conf, should the [Interface] Address property match that of say, eth0? Such that it's using the connection on eth0 to receive and send wireguard packets?
On the
wg-server.conf, should the[Interface]Addressproperty match that of say,eth0? Such that it's using the connection on eth0 to receive and send wireguard packets?
No, Interface.Adress is always any ip in your wireguard subnet (10.200.200.0/24, in this case 10.200.200.1/24). These configs are hardware connection agnostic, except for endpoints.
Wireguard file
For anyone else who found these while in the process of learning about wireguard, these config examples are meant to be ingested by wg-quick, not directly by wg. Per wg-quick(8), it supports more directives the configuration file than wg does. If you are a newb, you almost certainly want to start with wg-quick.
How can get a CL ID