|Est. reading time||15m|
Our sample setup to configure PFSense Site-to-Site IPSec vpn tunnelAbove is a very simple site-to-site VPN, with a security gateway (SOHO and Remote IDC) linking two remote private networks 192.168.1.0/24 and 10.10.29.64/26. Remote IDC VPN powered by either a Cisco/OpenBSD based system and local SOHO VPN (PFSense) gateways already configured. From the above, you can see the IPSec config on is as follows:
VPN config provided by a CISCO/OpenBSD gateway located in remote IDC
|Phase 1 config||Savings|
|Your peer IPv4 address||22.214.171.124|
|Cisco/OpenBSD gateway IPv4 address||126.96.36.199|
|Phase 2 config||Values|
|Perfect Forward Secrecy (PFS)||Yes|
|Remote Subnets||10.10.29.64/26 and 10.12.249.192/26|
Howto Configure PFSense Site-to-Site IPSec VPN Tunnel
Let us get started with the configuration.
PFSense appliance VPN IPSec configuration
pfSense must be set up and be working correctly for the existing local network environment. Both locations must be using non-overlapping LAN IP subnets. For demo purpose my PFSense appliance located at https://192.168.1.254/.
Step #1: Login to admin webui
Fire a browser and type the following url:
Step #2: Setup the VPN Tunnel
Click on VPN > IPSec:
Step #3: Configure a new tunnel
Click on + button (see fig.04) to add a new IPsec tunnel Phase 1 configuration. Make sure Interface set to “WAN”, Remote Gateway to “188.8.131.52”, Authentication Method to Pre-Shared key to “YOUR-super-secret-password-key”, Encryption to “3DES”, Authentication to “MD5”, Diffie-Hellman Group to “2”, Keylife to “14400”, and finally press the Save button.
The IPsec tunnel configuration has been changed. You must apply the changes in order for them to take effect.
Click on the Apply changes button:
Step #4: Create a new Phase 2 config
To create a new Phase 2, click the large + inside the Phase 1 entry in the list, on the left-hand side. This expands the list to display all Phase 2 entries for this Phase 1. Click the + button on the right to add a new entry:
You must set remote network as “10.10.29.64/26”, Protcol to “ESP”, Encrption algorithmes to “3DES”, Hash algothrithms to “MD5”, PFS key group to “2”, lifetime to “3600” and finally click on the Save button and Apply changes button to activate the tunnel.
Step #5: Add IPSec firewall rules
By default firewall rules are automatically added to the WAN to allow the tunnel to connect, but if the option to disable automatic VPN rules is checked, then manual rules may be required. The following rules added by the firewall (you can see them by typing the pfctl -sr | grep -i ipsec command at PFSense console)
anchor "ipsec/*" all pass out on enc0 all flags S/SA keep state label "IPsec internal host to host" pass out route-to (rl0 192.168.0.1) inet proto udp from any to 184.108.40.206 port = isakmp keep state label "IPsec: SL IPsec - outbound isakmp" pass in on rl0 reply-to (rl0 192.168.0.1) inet proto udp from 220.127.116.11 to any port = isakmp keep state label "IPsec: SL IPsec - inbound isakmp" pass out route-to (rl0 192.168.0.1) inet proto udp from any to 18.104.22.168 port = sae-urn keep state label "IPsec: SL IPsec - outbound nat-t" pass in on rl0 reply-to (rl0 192.168.0.1) inet proto udp from 22.214.171.124 to any port = sae-urn keep state label "IPsec: SL IPsec - inbound nat-t" pass out route-to (rl0 192.168.0.1) inet proto esp from any to 126.96.36.199 keep state label "IPsec: SL IPsec - outbound esp proto" pass in on rl0 reply-to (rl0 192.168.0.1) inet proto esp from 188.8.131.52 to any keep state label "IPsec: SL IPsec - inbound esp proto"
To setup IPSec firewall rules as per your needs, click on the Firewall > Rules and IPsec tab. Setup rules as per your needs.
How do I see the current status of the IPSec vpn?
Click on the Status > IPSec:
Give it a few seconds to connect to the remote side. Once connected you will see the status as follows:
How do I test my vpn setup?
Try to ping or ssh into one of the remote server:
$ ping -c2 10.10.29.68 PING 10.10.29.68 (10.10.29.68): 56 data bytes 64 bytes from 10.10.29.68: icmp_seq=0 ttl=60 time=267.420 ms 64 bytes from 10.10.29.68: icmp_seq=1 ttl=60 time=271.900 ms --- 10.10.29.68 ping statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 267.420/269.660/271.900/2.240 ms ## try ssh now ## $ ssh email@example.com
And, there you have it, VPN up and running from your SOHO. For more info see the official doc here.
🐧 15 comments so far... add one ↓
|Category||List of Unix and Linux commands|
|Disk space analyzers||df • ncdu • pydf|
|File Management||cat • cp • mkdir • tree|
|Firewall||Alpine Awall • CentOS 8 • OpenSUSE • RHEL 8 • Ubuntu 16.04 • Ubuntu 18.04 • Ubuntu 20.04|
|Network Utilities||NetHogs • dig • host • ip • nmap|
|OpenVPN||CentOS 7 • CentOS 8 • Debian 10 • Debian 8/9 • Ubuntu 18.04 • Ubuntu 20.04|
|Package Manager||apk • apt|
|Processes Management||bg • chroot • cron • disown • fg • jobs • killall • kill • pidof • pstree • pwdx • time|
|Searching||grep • whereis • which|
|User Information||groups • id • lastcomm • last • lid/libuser-lid • logname • members • users • whoami • who • w|
|WireGuard VPN||Alpine • CentOS 8 • Debian 10 • Firewall • Ubuntu 20.04|