{"id":19979,"date":"2020-04-02T16:01:10","date_gmt":"2020-04-02T16:01:10","guid":{"rendered":"http:\/\/www.firewallhardware.it\/pfsense-e-opnvpn-guida-alla-creazione-e-configurazione-di-un-server-vpn-road-warrior\/"},"modified":"2023-06-05T17:26:35","modified_gmt":"2023-06-05T15:26:35","slug":"pfsense-and-openvpn-guide-to-creating-and-configuring-a-road-warrior-vpn-server","status":"publish","type":"post","link":"https:\/\/blog.miniserver.it\/en\/pfsense\/pfsense-and-openvpn-guide-to-creating-and-configuring-a-road-warrior-vpn-server\/","title":{"rendered":"pfSense and OpenVPN: guide to creating and configuring a Road Warrior VPN server"},"content":{"rendered":"

Objective of this guide:<\/h3>\n

In this guide we see how to configure a RW<\/strong> (Road Warrior) VPN server via OpenVPN on pfSense<\/strong>\u00ae. The aim is to create a basic configuration to allow a correct functioning of our VPN.<\/p>\n

Used Hardware:<\/h3>\n

This guide can be applied to all the hardware certified by us of the firewall line that you can find here: https:\/\/www.miniserver.it\/firewall<\/a><\/p>\n

Software environment:<\/h3>\n

pfSense\u00ae 2.4.x<\/strong><\/p>\n

Let’s configure OpenVPN:<\/h3>\n

First of all, from our top menu, go to VPN<\/strong>\/OpenVPN<\/strong>\/Servers<\/strong>.<\/p>\n

We also proceed from the convenient Wizard that will allow us to easily create our CA (Certification Authority), the Server Certificate and the configuration of the RW VPN<\/strong> Server; these components can also be created individually.<\/p>\n

Let’s start by selecting Local User Access<\/p>\n

\"VPN<\/p>\n

At this point it is time to create our CA, as a necessary parameter we must enter a “Descriptive name” that will allow us to identify it, while all the other parameters can be left by default.<\/p>\n

\"VPN<\/p>\n

Let’s move on to creating the Server Certificate to be associated with our VPN<\/strong> server, as perl the CA will require a “Descriptive name” and leave the other default parameters.<\/p>\n

\"VPN<\/p>\n

Now the actual VPN<\/strong> server configuration.<\/p>\n

In the “Interface” item we select the interface on which we want our service to listen, if we have more than one WAN interface we choose the one we want to dedicate to the service, if we want later we can select multiple interfaces for greater redundancy.<\/p>\n

It is appropriate to consider that the port that we will choose for the VPN<\/strong> must be open on the listening interface, therefore if we are behind a Router of some ISP it will be necessary to be able to open the door to the interface of our Firewall, if instead we have the possibility of having a Public IP address directly configured on the Firewall interface will be sufficient to create an associated rule (as we will see later).<\/p>\n

We choose the protocol to be used and the port dedicated to the service (default for OpenVPN<\/strong> is UDP 1194).<\/p>\n

In the “Description” item we choose the name with which we want to identify the server.<\/p>\n

In the “Cryptographic Settings” section we can leave everything by default.<\/p>\n

\"VPN<\/p>\n

In the “Tunnel Settings” section it will be necessary to indicate a “Tunnel Network” that we could choose at random, making sure that it is not the same as other known networks or public networks, in fact it is the virtual network that will use the VPN<\/strong>.<\/p>\n

In “Local Network” instead we will indicate the LAN network to which you want to give remote access, if there are multiple LAN networks to which we want to give access, you can enter them by separating them with a comma.<\/p>\n

\"VPN<\/p>\n

\"VPN<\/p>\n

At this point the wizard asks us if we want to insert the Firewall Rule associated with the WAN interface and the one with the OpenVPN virtual interface, by ticking both will automatically create.<\/p>\n

\"VPN<\/p>\n

Let’s now see in detail the completed server configuration, as anticipated it is a basic configuration but we can always restrict security, for example by setting the maximum number of client accesses in “Concurrent connections”, or increase the level of encryption. These adjustments can affect the performance of the equipment and the connection.<\/p>\n

\"VPN<\/p>\n

\"VPN<\/p>\n

\"VPN<\/p>\n

\"VPN<\/p>\n

Below is the detail of the Firewall Rules created:<\/p>\n

    \n
  • For the WAN interface<\/li>\n<\/ul>\n

    \"VPN<\/p>\n

    \"VPN<\/p>\n

      \n
    • For the OpenVPN<\/strong> interface<\/li>\n<\/ul>\n

      \"VPN<\/p>\n

      \"VPN<\/p>\n

      The CA.<\/strong><\/p>\n

      \"VPN<\/p>\n

      Now let’s see how to create the users we want to connect to in VPN<\/strong>.<\/p>\n

      Position ourselves under System \/ User Manager \/ Users and create the username and password and User Certificate associated with the user by checking the “Certificate” “Click to create a user certificate”, you must enter a “descriptive name” to the created certificate. In this way we will have created both the user and the associated certificate in a single operation<\/p>\n

      \"VPN<\/p>\n

      \"VPN<\/p>\n

      In the “Certificate Manager” section we will see the certificate associated with the VPN<\/strong> server and all those associated with the users created.<\/p>\n

      \"VPN<\/p>\n

      At this point we can export the configuration files and certificates for individual users who will use the VPN clients to connect.<\/p>\n

      First of all it is necessary to install the package “openvpn-client-export”, to do this we can search for it by going to System\/Package Manager\/Available Packages.<\/p>\n

      \"VPN<\/p>\n

      Once installed we will see the option added under OpenVPN \/ Client Export.<\/p>\n

      Under “Remote Access Server” we select our created VPN server.<\/p>\n

      In the Client Connection Behavior section we will enter the parameters with which the .ovpn configuration file will be generated for the user, in particular we recommend configuring as follows:<\/p>\n

        \n
      • “Host Name Resolution” on “Other”<\/li>\n
      • “Host Name” we will have to enter the Public IP address of our network<\/li>\n
      • “Verify Server CN” we can leave it by default on “Automatic” or if we have problems set it on “Do not verifythe CN server”.<\/li>\n<\/ul>\n

        \"VPN<\/p>\n

        Once the parameters are configured, we can export our users configuration file to be installed on the clients.
        \nTo do this we have various choices, the most recommended below:<\/p>\n

          \n
        • “Most Clients”: genera un file .ovpn contenete sia la configurazione che i certificati e le chiavi facilmente importabile, compatibile con i client: OpenVPN per Windows, Tunnelblick per OS X<\/li>\n
        • “OpenVPN Connect”: generates an .ovpn file compatible with OpenVPN Connect Apps for Android and iOS<\/li>\n
        • “Archive”: compatible with Windows, generates an archive containing, in 3 separate files, the configuration (.ovpn), certificates (.p12) and the key (.key)<\/li>\n
        • Under the “Current Windows Installer” section we can generate self-installing and preconfigured files for Windows clients<\/li>\n<\/ul>\n

          \"VPN<\/p>\n<\/div><\/div><\/div><\/div><\/div>\n","protected":false},"excerpt":{"rendered":"

          In this guide we see how to configure a RW (Road Warrior) VPN server via OpenVPN on pfSense\u00ae.<\/p>\n","protected":false},"author":11,"featured_media":22851,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[124],"tags":[270,138],"class_list":["post-19979","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pfsense","tag-openvpn-e-pfsense-en","tag-pfsense-en"],"_links":{"self":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/19979","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/users\/11"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/comments?post=19979"}],"version-history":[{"count":6,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/19979\/revisions"}],"predecessor-version":[{"id":28699,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/posts\/19979\/revisions\/28699"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/media\/22851"}],"wp:attachment":[{"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/media?parent=19979"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/categories?post=19979"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.miniserver.it\/en\/wp-json\/wp\/v2\/tags?post=19979"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}