Set Up WireGuard VPN on Ubuntu
Updated by Linode Contributed by Sunit Nandi
WireGuard is a simple, fast, and secure VPN that utilizes state-of-the-art cryptography. With a small source code footprint, it aims to be faster and leaner than other VPN protocols such as OpenVPN and IPSec. WireGuard is still under development, but even in its unoptimized state it is faster than the popular OpenVPN protocol.
The WireGuard configuration is as simple as setting up SSH. A connection is established by an exchange of public keys between server and client. Only a client that has its public key in its corresponding server configuration file is allowed to connect. WireGuard sets up standard network interfaces (such as
wg1), which behave much like the commonly found
eth0 interface. This makes it possible to configure and manage WireGuard interfaces using standard tools such as
This guide will configure a simple peer connection between a Linode running Ubuntu 18.04, and a client. The client can be either your local computer or another Linode.
CautionDo not use WireGuard for critical applications. The project is still undergoing security testing and is likely to receive frequent critical updates in the future.
Before You Begin
- You will need root access to your Linode, or a user account with
- Set your system’s hostname.
GRUB 2kernel is required for this guide. All distributions for all new Linodes now boot with the
GRUB 2kernel by default. However, if you are running an older distribution, you will need to check to see which kernel you are running. You can use the Update Kernel Guide to check your kernel version and change it using the Cloud Manager. Select
GRUB 2from the Boot Settings: Select a Kernel dropdown menu in Step 4 of Update Your Linode Kernel with Linode’s Cloud Manager.
Add the Wireguard repository to your sources list. Apt will then automatically update the package cache.
sudo add-apt-repository ppa:wireguard/wireguard
Install Wireguard. The
wireguardpackage will install all necessary dependencies.
sudo apt install wireguard
DKMS will then build the Wireguard kernel module. If successful, you’ll see the following output:
wireguard: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-43-generic/updates/dkms/ depmod................... DKMS: install completed. Setting up wireguard (0.0.20181218-wg1~bionic) ... Processing triggers for libc-bin (2.27-3ubuntu1) ...
NoteIf the installation completes but the output does not appear, your kernel is most likely not configured correctly. To double check, issue the
lsmod | grep wireguardcommand. Its output should not be blank. Refer to the previous section to troubleshoot.
Configure WireGuard Server
Generate a private and public key pair for the WireGuard server:
umask 077 wg genkey | tee privatekey | wg pubkey > publickey
This will save both the private and public keys to your home directory; they can be viewed with
Create the file
/etc/wireguard/wg0.confand add the contents indicated below. You’ll need to enter your server’s private key in the
PrivateKeyfield, and its IP addresses in the
1 2 3 4 5 6 7
[Interface] PrivateKey = <Private Key> Address = 10.0.0.1/24, fd86:ea04:1115::1/64 ListenPort = 51820 PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE; ip6tables -A FORWARD -i wg0 -j ACCEPT; ip6tables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE; ip6tables -D FORWARD -i wg0 -j ACCEPT; ip6tables -t nat -D POSTROUTING -o eth0 -j MASQUERADE SaveConfig = true
Address defines the private IPv4 and IPv6 addresses for the WireGuard server. Each peer in the VPN network should have a unique value for this field.
ListenPort specifies which port WireGuard will use for incoming connections.
PostUp and PostDown defines steps to be run after the interface is turned on or off, respectively. In this case,
iptablesis used to set Linux IP masquerade rules to allow all the clients to share the server’s IPv4 and IPv6 address. The rules will then be cleared once the tunnel is down.
SaveConfig tells the configuration file to automatically update whenever a new peer is added while the service is running.
Set Up Firewall Rules
Allow SSH connections and WireGuard’s VPN port:
sudo ufw allow 22/tcp sudo ufw allow 51820/udp sudo ufw enable
Verify the settings:
sudo ufw status verbose
Start the Wireguard Service
wg-quick up wg0
wg-quickis a convenient wrapper for many of the common functions in
wg. You can turn off the wg0 interface with
wg-quick down wg0
Enable the Wireguard service to automatically restart on boot:
sudo systemctl enable [email protected]
Check if the VPN tunnel is running with the following two commands:
sudo wg show
You should see a similar output:
[email protected]:~$ sudo wg show interface: wg0 public key: vD2blmqeKsV0OU0GCsGk7NmVth/+FLhLD1xdMX5Yu0I= private key: (hidden) listening port: 51820
Your output should resemble the following:
[email protected]:~$ ifconfig wg0 wg0: flags=209
mtu 1420 inet 10.0.0.1 netmask 255.255.255.0 destination 10.0.0.1 inet6 fd86:ea04:1115::1 prefixlen 64 scopeid 0x0 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
The process for setting up a client is similar to setting up the server. When using Ubuntu as your client’s operating system, the only difference between the client and the server is the contents of the configuration file. If your client uses Ubuntu, follow the steps provided in the above sections and in this section. For installation instructions on other operating systems, see the WireGuard docs.
Generate a key pair for the client if you have not already:
umask 077 wg genkey | tee privatekey | wg pubkey > publickey
The main difference between the client and the server’s configuration file,
wg0.conf, is it must contain its own IP addresses and does not contain the
1 2 3
[Interface] PrivateKey = <Output of privatekey file that contains your private key> Address = 10.0.0.2/24, fd86:ea04:1115::5/64
Connect the Client and Server
There are two ways to add peer information to WireGuard; this guide will demonstrate both methods.
NoteStop the interface with
sudo wg-quick down wg0on both the client and the server.
The first method is to directly edit the client’s
wg0.conffile with the server’s public key, public IP address, and port:
1 2 3 4
[Peer] PublicKey = <Server Public key> Endpoint = <Server Public IP>:51820 AllowedIPs = 10.0.0.2/24, fd86:ea04:1115::5/64
wgservice on both the client and server:
wg-quick up wg0 systemctl enable [email protected]
The second way of adding peer information is using the command line. This information will be added to the config file automatically because of the
SaveConfigoption specified in the Wireguard server’s configuration file.
Run the following command from the server. Replace the example IP addresses with those of the client:
sudo wg set wg0 peer <Client Public Key> endpoint <Client IP address>:51820 allowed-ips 203.0.113.12/24,fd86:ea04:1115::5/64
Verify the connection. This command can be run from the client or the server:
Regardless of which method you choose to add peer information to WireGuard, there should be a Peer section in the output of the
sudo wgcommand if the setup was successful.
[email protected]:~$ sudo wg interface: wg0 public key: vD2blmqeKsV0OU0GCsGk7NmVth/+FLhLD1xdMX5Yu0I= private key: (hidden) listening port: 51820 peer: iMT0RTu77sDVrX4RbXUgUBjaOqVeLYuQhwDSU+UI3G4= endpoint: 10.0.0.2:51820 allowed ips: 10.0.0.2/24, fd86:ea04:1115::/64
This Peer section will be automatically added to
wg0.confwhen the service is restarted. If you would like to add this information immediately to the config file, you can run:
wg-quick save wg0
Additional clients can be added using the same procedure.
Test the Connection
Return to the client and ping the server:
ping 10.0.0.1 sudo wg
The last two lines of the output from running the
wgcommand should be similar to:
latest handshake: 1 minute, 17 seconds ago transfer: 98.86 KiB received, 43.08 KiB sent
This indicates that you now have a private connection between the server and client. You can also ping the client from the server to verify that the connection works both ways.
The process used in this guide can be extended to configure network topologies. As mentioned previously, Wireguard is an evolving technology. If you use WireGuard, you should monitor the official documentation and todo list for critical updates and new/upcoming features.
Join our Community
This guide is published under a CC BY-ND 4.0 license.