FreeBSD OpenVPN Server/Routed

From Secure Computing Wiki
Jump to navigation Jump to search

Many people feel overwhelmed by the installation and configuration of OpenVPN. Here, I'll try to write an easy to understand installation guide.

i'm fine good work

Setup SSL Certificates/Keys

I think setting up SSL is the toughest part of OpenVPN for most people, including myself. I've written a script to help manage my network OpenSSL certificates. You can download this file here. Extract the tgz in your home directory (for now). You should see two files,, and openssl.cnf.


You must edit the perl script to work correctly on your network. When initially downloaded, the script with exit, reminding you to setup all the variables at the top of the file. By default, the top of the file looks like this:

### Comment out the line with a # when you edit this file.
die("\n\n\n\nPlease edit variables and comment out this line.\n\n\n\n");
### SSL CERT Variables here ###
$ENV{'KEY_SIZE'} = "1024";
$ENV{'KEY_DIR'} = "/usr/local/etc/openvpn/ssl"; 
$ENV{'KEY_DAYS'} = "3650";
$ENV{'KEY_CN'} = "";
$ENV{'KEY_CRL_LOC'} = "URI:http://CRL_URI";

We need to change each of these values. The top of my file, with all the variables set, looks like this:

### Comment out the line with a # when you edit this file.
#die("\n\n\n\nPlease edit variables and comment out this line.\n\n\n\n");
### SSL CERT Variables here ###
$ENV{'KEY_CITY'} = "Minneapolis";
$ENV{'KEY_ORG'} = "Secure Computing Networks";
$ENV{'KEY_EMAIL'} = '';
$ENV{'KEY_SIZE'} = "1024";
$ENV{'KEY_DIR'} = "/usr/local/etc/openvpn/ssl";
$ENV{'KEY_DAYS'} = "3650";
$ENV{'KEY_CN'} = "";

There are a couple points to note. First, make sure you comment out the die("... line. Failure to do so will result in the script failing to run. Second, the KEY_CRL_LOC is an optional variable, for use if you want to make your certificate revocation list available to the public. This script will not upload the CRL to your URI location. This must be manually done.

For OpenVPN purposes, I would not recommend making a key smaller than 1024. The KEY_DAYS variable determines how long your certificates are good for. Essentially, this is how often you'll have to reissue ssl certificates to your users. You can always revoke a certificate, so there's little worry about lost/stolen/fired/etc users.

Lastly, your KEY_DIR directory must already exist, or the script will error out. In our test installation here, we need to create this directory:

mkdir /usr/local/etc/openvpn/ssl

I keep my script in /usr/local/etc/openvpn. This script will keep all of the files it needs to run in its own directory, which helps keep this my openvpn directory clean.


We should now be ready to run for the first time. Please note, you will need to have perl 5.8.8 or later installed for this script to run. At this time, there are no other dependencies. To run the script, simply use the following command:


Replace KEY_DIR with the directory where the script resides. If you're CWD is that directory, use the following command:


First Run

The first time (after you've set your variables), you're going to be prompted to either create a new CA root certificate, or point the script to your existing one. For the purpose of this document, we're going to create a new certificate.

  • For the certificate owner's name, I used vpn. Note, you cannot have spaces, capitol letters, or special characters.
  • ALWAYS protect your CA certificate with a password. Otherwise, why have a VPN if you're going to give keys to the world?
  • You'll note that most questions are answered automatically for you, based on the variables at the head of our script.

Once the CA certificate has been created (or pointed to), you should get a menu that appears as follows:

#                  SSL-ADMIN                        #
Please enter the menu option from the following list:
1) Update run-time options:
     Common Name: vpn
     Key Duration (days): 3650
     Current Serial #: 01
     Key Size (bits): 1024
     Intermediate CA Signing: NO
2) Create new Certificate Request
3) Sign a Certificate Request
4) Perform a one-step request/sign
5) Revoke a Certificate
6) Renew/Re-sign a past Certificate Request
7) View current Certificate Revokation List
8) View index information for certificate.
z) Zip files for end user.
CA) Create new Self-Signed CA certificate.
q) Quit ssl-admin

I'll cover the full operation of my script in another document, but you should be able to figure out most of the functions on your own. Please feel free to email me at with specific questions or bugs. Also, please, please, please, feel free to help me and add to/modify this script. Send me your updates!

Known Bugs

  • There isn't a blank CRL generated on intial install. This causes OpenVPN to die if it's checking for CRL.
  • There isn't any way to view the entire index.
  • File permissions aren't being set correctly on new install.

OpenVPN Configuration

Now that we've got our SSL setup complete, we can move on to setting up the remainder of OpenVPN. To begin, we need a Diffie Hellman key. Create this with the following command:

openssl dhparam -out KEY_DIR/active/dh1024.pem 1024

Replace KEY_DIR with your OpenVPN directory.

Finally, we can create our OpenVPN configuration file. I will show you the file I use, and explain the entries as best I can:

port 1194

proto udp

dev tun

ca      /usr/local/etc/openvpn/ssl/active/ca.crt
cert    /usr/local/etc/openvpn/ssl/active/server.crt
key     /usr/local/etc/openvpn/ssl/active/server.key
dh      /usr/local/etc/openvpn/ssl/active/dh1024.pem


push "route"

# this is necessary for clients to reach 
# clients behind the openvpn gateways

keepalive 10 120

## allow multiple access from the same client

user vpn
group vpn


status                  /var/openvpn/openvpn-status.log

log-append              /var/log/openvpn.log

verb 4

crl-verify              /usr/local/etc/openvpn/ssl/prog/crl.pem

daemon - This tells OpenVPN that we want to run a server. On client machines, you'll use client.
port 1194 - The tells OpenVPN to run on port 1194.
proto udp - Run with UDP protocol. I don't know why this is better than TCP, if it is.
dev tun - What device to use. Use tun for routed OpenVPN.
ca/cert/key/dh - If you're using my script, your keys/certficates will be in KEY_DIR/active/.
server - The IP address and subnet the virtual interface should have. Your clients will get addresses on this network.
push - We're pushing our LAN network route across to the VPN clients. Note, the 192.168/16 network is not advised, as most home networks run on this network, and routing will break for your client.
client-to-client - This is necessary for clients to reach other clients behind the OpenVPN gateway.
keepalive 10 120 -
duplicate-cn - Allow clients to connect more than once.
user/group - The user and group openvpn should run as.
persist-key/tun - Try to avoid accessing certain resources after perms have downgraded.
status - Keep a log of openvpn status.
log-append - Log file for messages, append rather than truncate.
verb 4' - Log file verbosity. 4 is 'reasonable.' Max of 9.
crl-verify - IMPORTANT This tells openvpn to verify ssl certificates against our Certificate Revocation List.

More options and documentation is available at

Put this file in your openvpn directory. I named mine server.conf. We pointed to this file in /etc/rc.conf.

Start OpenVPN

Once all of the configuration has been completed, you're ready to start the server.

/usr/local/etc/rc.d/openvpn start