You'll first want to install WireGuard.
A new interface can be added via
ip-link(8), which should automatically handle module loading:
# ip link add dev wg0 type wireguard
An IP address and peer can be assigned with
# ip address add dev wg0 192.168.2.1 peer 192.168.2.2
The interface can be configured with keys and peer endpoints with the included
# wg setconf wg0 myconfig.conf
# wg set wg0 listen-port 51820 private-key /path/to/private-key peer ABCDEF... allowed-ips 192.168.88.0/24 endpoint 220.127.116.11:8172
Finally, the interface can then be activated with
# ip link set up dev wg0
There are also the
wg show and
wg showconf commands, for viewing the current configuration. Calling
wg with no arguments defaults to calling
wg show on all WireGuard interfaces.
WireGuard requires base64-encoded public and private keys. These can be generated using the
$ umask 077 $ wg genkey > privatekey
This will create
privatekey on stdout containing a new private key.
You can then derive your public key from your private key:
$ wg pubkey < privatekey > publickey
This will read
privatekey from stdin and write the corresponding public key to
publickey on stdout.
Of course, you can do this all at once:
$ wg genkey | tee privatekey | wg pubkey > publickey
Side by Side Video
It may be extremely instructive to watch two peers be configured side by side:
NAT and Firewall Traversal Persistence
By default, WireGuard tries to be as silent as possible when not being used; it is not a chatty protocol. For the most part, it only transmits data when a peer wishes to send packets. When it's not being asked to send packets, it stops sending packets until it is asked again. In the majority of configurations, this works well. However, when a peer is behind NAT or a firewall, it might wish to be able to receive incoming packets even when it is not sending any packets. Because NAT and stateful firewalls keep track of "connections", if a peer behind NAT or a firewall wishes to receive incoming packets, he must keep the NAT/firewall mapping valid, by periodically sending keepalive packets. This is called persistent keepalives. When this option is enabled, a keepalive packet is sent to the server endpoint once every interval seconds. A sensible interval that works with a wide variety of firewalls is 25 seconds. Setting it to 0 turns the feature off, which is the default, since most users will not need this, and it makes WireGuard slightly more chatty. This feature may be specified by adding the
PersistentKeepalive = field to a peer in the configuration file, or setting
persistent-keepalive at the command line. If you don't need this feature, don't enable it. But if you're behind NAT or a firewall and you want to receive incoming connections long after network traffic has gone silent, this option will keep the "connection" open in the eyes of NAT.
$ sudo contrib/examples/ncat-client-server/client.sh
This will automatically setup interface
wg0, through a very insecure transport that is only suitable for demonstration purposes. You can then try loading the hidden website or sending pings:
$ chromium http://192.168.4.1 $ ping 192.168.4.1
If you'd like to redirect your internet traffic, you can run it like this:
$ sudo contrib/examples/ncat-client-server/client.sh default-route $ curl zx2c4.com/ip 18.104.22.168 demo.wireguard.io curl/7.49.1
You may not use this server for any abusive or illegal purposes.