The Ubiquiti UniFi Security Gateway (USG) Pro makes a great VPN terminator and is ideal firewall for small and medium business. Occasionally, I am configuring the USG Pro for my clients to protect their networks, be the gateway of their network, and also provide VPN capability.
In this guide, I will show you how to configure a Remote Access VPN on the Ubiquiti USG Pro using L2TP. In this setup, I am using the Cloud Key G2 to manage a Ubiquiti USG Pro.
What is L2TP?
Layer 2 Tunneling Protocol (L2TP) is a tunneling protocol used in VPNs. It needs an encryption protocol to protect the traffic being sent through the L2TP tunnel. Read more here.
There are a few components needed to make this work
- RADIUS Server (on the USG)
- RADIUS User
- VPN Network (on the USG)
- Firewall Rules (allowing L2TP VPN)
- Device configuration
RADIUS User Configuration
To log in remotely via VPN, you need an account. The first step is to log into your USG or your UniFi management.
Go to Settings and then click on Services
Under RADIUS and Users, click on Create New User.
Type out the account name for this user and give it a strong password. (Make sure you keep that in your password manager). Leave the VLAN section blank.
For Tunnel Type, select 3 – Layer Two Tunneling Protocol (L2TP)
For Medium Type, select 1 – IPv4
Click Save
RADIUS Server Configuration
We will need to configure a RADIUS Server on the Ubiquiti USG in order to accept remote VPN connections from various users that we can set up for remote access.
Under RADIUS and Server enable RADIUS Server. Below that, type in a strong Secret and make sure you document that in your password manager.
Leave the defaults for the rest of the options. Then click on Apply.
Configure a Remote Access VPN Network
When users VPN into the network, we need to place them on their own subnet. On the left side navigation, under Settings, click on Networks.
Click on Create a New Network.
Give the network a descriptive name such as Remote User VPN
For purpose, select Remote User VPN. This will allow us to select a VPN Type.
For VPN Type, select L2TP Server.
Create a strong Pre-Shared Key (You’ll need this key later when configuring your device for remote VPN)
Give the Remote User VPN network a Gateway/Subnet (Do not overlap this with any preconfigured networks. This is a new network.
For Name Server, select auto or manual. Under Manual you will specify the name servers.
Under RADIUS, select the Default RADIUS profile
Click Save
When you selected Remote User VPN and saved the network, it creates the necessary Firewall rules to allow L2TP VPN. View it under Routing & Firewall > Firewall > Rules IPv4 > WAN LOCAL
Create VPN Profile on Computer
I use macOS so these instructions are specific. Once I get a hold of my Windows Laptop and update it I’ll add a section for Windows.
In macOS we will use the built-in L2TP VPN capabilities.
Open Network Preferences
Click on the + icon on the bottom left to add a new VPN interface
Under Interface, select VPN
For VPN Type, select L2TP over IPsec
Create a descriptive name under Service Name
Click Create
In the configuration of the VPN profile, keep Configuration at Default.
For the Server Address, set the IP address of your USG’s WAN interface
For account name, set it to the RADIUS user you created earlier
Click on Authentication Settings button
For Password, enter the password of the RADIUS user
Under Machine Authentication, select Shared Secret enter the Shared Secret of the RADIUS Server.
Click OK
Back at the VPN Profile configuration window, click Advanced
Under Options, enable “Send all traffic over VPN connection” if you’d like to make this a Full VPN Tunnel.
Click OK and then click on Apply
Test Remote Access VPN
Click on Connect
If successful, status will change to Connected, you’ll see how long you’ve been connected, and you’ll have an IP address from when you configured it on the Remote Access VPN network.
Now try accessing your local resources.
At the time of this writing, Ubiquiti doesn’t offer any way to easily see the status of remote access VPN users on the GUI dashboard.
The closest thing is an Event where my laptop shows that it has connected to the LAN, but you would assume that’s a local Ethernet connection.
The only way to tell the status is through the CLI of the USG using show vpn remote-access and show vpn ipsec sa
$ show vpn remote-accessActive remote access VPN sessions:User Time Proto Iface Remote IP TX pkt/byte RX pkt/byte---------- --------- ----- ----- --------------- ------ ------ ------ ------rowell 00h00m14s L2TP l2tp0 192.168.3.1 326 105.5K 425 62.0KThe Remote IP is the Remote VPN network that I created earlier.
$ show vpn ipsec saremote-access: #6, ESTABLISHED, IKEv1, 5df87ceee4a88d30:ba926ce41288578c local ‘x.x.x.x’ @ x.x.x.x remote '172.20.3.6' @ 12.9.250.183 AES_CBC-256/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_2048 established 330s ago remote-access: #7, INSTALLED, TRANSPORT-in-UDP, ESP:AES_CBC-128/HMAC_SHA1_96 installed 330 ago in c7a3bef9, 1458020 bytes, 9236 packets, 0s ago out 0e0bf674, 9496201 bytes, 10136 packets, 29s ago local x.x.x.x/32[udp/l2f] remote 12.9.250.183/32[udp/51184]I’ve sanitized the local IP address. The local address is the WAN of the USG.
The remote IP address is my private IP and what my WAN IP is at the hotel I’m at.
For troubleshooting purposes, you could issue show vpn log tail to see the last 10 VPN log messages. tail is optional, it will continue to update the last 10 log messages and you can use that for troubleshooting someones connection.
$ show vpn log tailMar 7 07:10:12 12[IKE] <remote-access|6> closing CHILD_SA remote-access{7} with SPIs c7a3bef9_i (1548107 bytes) 0e0bf674_o (9631239 bytes) and TS x.x.x.x/32[udp/l2f] === 12.9.250.183/32[udp/51184]Mar 7 07:10:12 04[IKE] <remote-access|6> deleting IKE_SA remote-access[6] between x.x.x.x[x.x.x.x]...12.9.250.183[172.20.3.6]Mar 7 07:10:15 08[KNL] interface l2tp0 deletedMar 7 07:10:56 07[IKE] <7> 12.9.250.183 is initiating a Main Mode IKE_SAMar 7 07:10:57 04[IKE] <remote-access|7> IKE_SA remote-access[7] established between x.x.x.x[x.x.x.x]...12.9.250.183[172.20.3.6]Mar 7 07:10:57 02[IKE] <remote-access|7> CHILD_SA remote-access{8} established with SPIs cb2f14f2_i 02e5c731_o and TS x.x.x.x/32[udp/l2f] === 12.9.250.183/32[udp/64282]Mar 7 07:11:00 16[KNL] 10.255.255.0 appeared on ppp0Mar 7 07:11:00 06[KNL] 10.255.255.0 disappeared from ppp0Mar 7 07:11:00 05[KNL] 10.255.255.0 appeared on ppp0Mar 7 07:11:00 02[KNL] interface l2tp0 activatedThoughts
Overall, it was simple to configure remote access VPN if you are familiar with configuring it on other network devices. Ubiquiti could help others with a more simplified wizard to eliminate the number of sections you need to jump through to complete remote access VPN.
Additionally, Ubiquiti needs to add a status of remote VPN users in their dashboard to avoid having to use the CLI.
