Skip to content

Step By Step Guide On How To Create A Site To Site VPN With PFsense Using OpenVPN With A Pre Shared Key

PFsense is one of the the greatest Open Source packages out there. It is an extremely reliable enterprise grade routing platform. For me, it has been incredibly useful in virtualized scenarios. A common usage scenario for me goes like this. Someone wants to deploy a single ESXi host to a datacenter for backup, as a web server, mail server, spam filter, and/or various other tasks. One network interface on the server connects directly to the datacenter network. This NIC is assigned to a network on the ESXi host named “WAN.” Another network (vswitch) is created on the ESXi host called “Internal Network.” A pfsense virtual machine is created with two NICs. One assigned to WAN, and one assigned to Internal Network. This pfsense virtual machine takes care of all routing and firewall functions for each virtual machine set up on the ESXi host. PFsense can handle multiple WAN IP addresses, firewall functionality and NAT capability. It provides all needed mechanisms to give access and lock down all virtual machines on the ESXi host. This is just an example.

This step by step how to will help you create a site to site VPN on any virtual machine or physical machine running pfsense. The steps are the same for both. This assumes you have pfsense running on each end of the VPN. My particular scenario has pfsense running on a virtual machine at a datacenter, and another running on my home network. My goal is to allow access to the private network at the datacenter from my home network. So lets get started.

How To Setup A Site To Site VPN On PFsense

First thing’s first. Here is the addressing scheme of both of my pfsense routers and their subnets. I have substituted my public WAN ip addresses for security.

Router A, (setup as OpenVPN server, located at datacenter)

  • WAN IP Address:
  • LAN IP Address:
  • LAN Subnet:

Router B (setup as OpenVPN client, located at home)

  • WAN IP Address:
  • LAN IP Address:
  • LAN Subnet:

One side will be configured as a client, and the other as a server. It doesn’t really matter which is which, but if you are connecting more than two sites, it would probably be a good idea to put the “server” on the fastest, most reliable connection. In my scenario, that would be the system at the datacenter. The pfsense documentation recommends shared key mode for site to site VPNs, unless there are more than 6 sites.

A firewall rule is required on the server node to allow traffic through to the interface and port where the server is running. If not, the traffic will be block and the VPN will never connect. If you need to filter certain traffic within the VPN connection, you can do this by adding rules under the OpenVPN tab, located at Firewall > Rules.

First connect to the web interface on Router A, the server. Go to the VPN > OpenVPN Servers tab, and then click + to create a new server.

Screen Shot 2015-05-18 at 2.30.11 PM

After clicking + you should see this page.

Screen Shot 2015-05-18 at 2.31.33 PM

The configuration is separated into four categories.

  • General Information
  • Cryptographic Settings
  • Tunnel Settings
  • Advanced Configuration

We will start with General Configuration.

General Configuration

  • Server Mode: Peer to Peer ( Shared Key )
  • Protocol: UDP
  • Device Mode: tun
  • Interface: The interface the VPN will be coming in from. Most likely WAN
  • Local Port: 1194
  • Description: Put in any description name for the VPN connection.

Here is a screenshot of my General information section after filling in required information.

Screen Shot 2015-05-18 at 2.37.55 PM

Router A (Server) Configuration

Make sure you are logged into Router A, the router acting as your OpenVPN Server, before proceeding.

Cryptographic Settings

  • Shared Key: Check the “Automatically generate a shared key” box.
  • Encryption algorithm: AES-128-CBC (128-bit) Feel free to select another encryption algorithm, it just has to match on both sides (server/client).
  • Hardware Crypto: No Hardware Crypto Acceleration.

Here is what mine looks like.

Screen Shot 2015-05-18 at 2.41.53 PM

Tunnel Settings

  • IPv4 Tunnel Network: (any unused network is fine, this is only used for communication between the client and server)
  • IPv4 Local Network: (this is the local network on the server side).
  • IPv4 Remote Network: (this is the local network on the client side. If there are multiple clients/networks, separate them with a comma).

This is what mine looks like. You can enable compression if you like, but it’s not necessary. If only passing traffic that’s already compressed, such as http or ssh, it might add unnecessary overhead.

Screen Shot 2015-05-18 at 2.51.12 PM

Advanced Configuration

There are no changes needed in the Advanced Configuration section. If needed, you can add additional route tables and OpenVPN commands here.

Click Save.

Now, click the “e” beside the connection you just created, and scroll down to Shared Key. A key will now be generated and show in that box. Highlight it, and copy it. You will need to paste it in the client shared key box in a minute.

Firewall Configuration (Router A, Server)

There are two rules we need to create in order for the VPN to work.

  • WAN Rule: Allow incoming connections to port 1194, to the router itself. This allows incoming VPN connections.
  • OpenVPN Rule: Allow all VPN traffic, so one side can communicate with the other.

First, we will create the WAN rule. Go to Firewall > Rules, then select the WAN tab.

Now, click on the + to add a rule.

  • Action: Pass
  • Interface: WAN
  • Protocol: UDP
  • Destination Port Range: From: 1194, To: 1194

Click Save

It should look like this.

Screen Shot 2015-05-18 at 4.55.54 PM

Next, click on the OpenVPN tab, under Firewall: Rules. Then click + to add a new rule.

  • Action: Pass
  • Interface: OpenVPN
  • Protocol: Any

Go ahead and click Save.

It should look like this.

Screen Shot 2015-05-18 at 4.58.44 PM

The server is now configured and ready to go.

Router B (Client) Configuration

Make sure you are now logged into Router B, the router you will be configuring as the OpenVPN Client. Navigate to VPN > OpenVPN, then select the Clients tab.

Screen Shot 2015-05-18 at 2.57.28 PM

Under the Clients tab, select the + to add a new client.

General Information

  • Server Mode: Peer to Peer ( Shared Key )
  • Protocol: UDP
  • Device Mode: tun
  • Server host or address: (this is the IP address of your WAN connection on Router A, the Server)
  • Server Port: 1194
  • Description: VPN Connection to Datacenter (Descriptive name of the VPN connection).

My General Information section looks like this.

Screen Shot 2015-05-18 at 3.00.28 PM

Cryptographic Settings

  • Shared Key: Uncheck this box, and Paste the key generated by your server. This can be found if you edit the OpenVPN server connection we created earlier (on Router A, Server), under the shared key section.
  • Encryption Algorithm: AES-128-CBC (128-bit) (unless you selected a different encryption algorithm earlier. If so, select it.)
  • Hardware Crypto: No Hardware Crypto Acceleration

My client Cryptographic Settings looks like this. (Shared Key has been changed for security)

Screen Shot 2015-05-18 at 3.11.27 PM

Tunnel Settings

  • Tunnel Network: (this is the tunnel network that was entered on the server. If different, make sure it matches here.)
  • Remote Network: (this is the local network (LAN) of your OpenVPN server)
  • Compression: Only enable this if you did so on the server configuration.

My Tunnel Settings looks like this.

Screen Shot 2015-05-18 at 3.15.18 PM

Advanced Configuration

Just like on the server’s advanced configuration, the client’s should be left blank as well.

Click Save.

Now, we need to configure the firewall on the client side (Router B, Client).

Go to Firewall > Rules, then select the OpenVPN tab. Then click + to add a new rule.

  • Action: Pass
  • Interface: OpenVPN
  • Protocol: Any

Go ahead and click Save.

It should look like this.

Screen Shot 2015-05-18 at 4.58.44 PM

At this point, everything is set up and your VPN should be connected. The connection activates very quickly once the settings are correct. To see if the link is up, navigate to Status > OpenVPN. You want to look in the status column. It should be “up.”

It looks like this.


On the Router B (Client) local network, you should now be able to ping the LAN IP address of the Router A (server) LAN interface. In my case,

Screen Shot 2015-05-18 at 5.08.18 PM

This will work the other way around as well.


If you are having problems pinging one direction or the other, go through these steps:

  • Verify firewall settings on both the client and server side, using the information above.
  • Try pinging both VPN tunnel addresses assigned to the client and the server. This will be the 172.16.0.x addresses. For some reason, i’ve seen the routing table not propagate correctly until these IP addresses are pinged. Weird, I know.
  • Check the routing table on each PFsense router and make sure the VPN tunnel network is listed in the routing table. If not, start over and recreate the tunnel.

I’ve used this method many times to set up point to point VPN connections and it has never failed me. Occasionally I’ll forget a firewall rule and will run into problems, but after double checking my work I usually find the culprit. Most of the time it’s firewall related. If you have any problems, please feel free to post in the comments below and I’ll try to lend a hand. Thanks!

5 thoughts on “Step By Step Guide On How To Create A Site To Site VPN With PFsense Using OpenVPN With A Pre Shared Key

  1. Rajkumar says:

    check your screen shorts , thats goes to Page not found

    • Mike Smith says:

      Yes, we had a catastrophic server failure last night and we are in the process of restoring everything right now. Sorry about that! I’ll have it fixed as soon as possible.

  2. Mike Smith says:

    It really depends on how your multi-wan is configured and deployed. Are you running BGP or some other method so the WAN IP address will route to whichever WAN connection is up or do they each of their own IP address regardless? If so, are the static or DHCP, etc.. ?


  3. oe go says:

    hi …
    how many sites of vpn site to site can i get

  4. oe go says:

    site server …….site remote 1 ….site remote 2….site remote….3……how many


Leave a Reply