1 z 5 01.10.2012 08:16 FreeBSD OpenVPN Server/Routed From Secure Computing Wiki OpenVPN Topics GENERAL: Routing RIP Routing Bridging FAQ Firewall VPN Chaining Troubleshooting Donations IRC meetings Developer Docs Tester Docs OS RELATED: FreeBSD Routed FreeBSD Bridged Many people feel overwhelmed by the installation and configuration of OpenVPN. Here, I'll try to write an easy to understand installation guide. Contents 1 Install OpenVPN 2 Setup SSL Certificates/Keys 2.1 Install 2.2 Tuning ssl-admin.conf 2.3 Executing ssl-admin.pl 2.4 First Run 2.5 Known Bugs 3 OpenVPN Configuration 3.1 Start OpenVPN Install OpenVPN The first step toward a running OpenVPN installation is to install OpenVPN. On FreeBSD, we can do so from the ports tree: cd /usr/ports/security/openvpn && make install clean Once the installation is complete, we need to setup our directories for storing our SSL keys, CRL, etc. I keep all this information in /usr/local/etc/openvpn. mkdir /usr/local/etc/openvpn In order for OpenVPN to start, we need to add the following lines to /etc/rc.conf: openvpn_enable="yes" openvpn_configfile="/usr/local/etc/openvpn/server.conf"
2 z 5 01.10.2012 08:16 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. Install On FreeBSD systems with recent ports trees, simply do the following: # cd /usr/ports/security/ssl-admin && make install Tuning ssl-admin.conf 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: ## Set default values here. # # The following values can be changed without affecting # your CA key. $ENV{'KEY_SIZE'} = "1024"; $ENV{'KEY_DAYS'} = "3650"; $ENV{'KEY_CN'} = ""; $ENV{'KEY_CRL_LOC'} = "URI:http://CRL_URI"; ## WARNING!!! ## # # Changing the following values has vast consequences. # These values must match what's in your root CA certificate. $ENV{'KEY_COUNTRY'} = "COUNTRY"; $ENV{'KEY_PROVINCE'} = "STATE/PROVINCE"; $ENV{'KEY_CITY'} = "CITY"; $ENV{'KEY_ORG'} = "ORGANIZATION"; $ENV{'KEY_EMAIL'} = 'EMAIL_ADDRESS'; 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. Executing ssl-admin.pl ssl-admin
3 z 5 01.10.2012 08:16 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: This program will walk you through requesting, signing, organizing and revoking SSL certificates. ssl-admin installed Tue Dec 16 09:39:57 CST 2008 I can't find your OpenVPN client config. Please copy your config to /usr/local/etc/ssl-admin/packages/client.ovpn ===================================================== # SSL-ADMIN # ===================================================== Please enter the menu option from the following list: 1) Update run-time options: Common Name: 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. dh) Generate Diffie Hellman parameters. CA) Create new Self-Signed CA certificate. S) Create new Signed Server certificate. q) Quit ssl-admin Menu Item: 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 ecrist@secure-computing.net (mailto:ecrist@secure-computing.net) 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.
4 z 5 01.10.2012 08:16 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. This can now be done with option dh in ssl-admin. Finally, we can create our OpenVPN configuration file. I will show you the file I use, and explain the entries as best I can: daemon port 1194 proto udp dev tun ca cert key dh /usr/local/etc/ssl-admin/active/ca.crt /usr/local/etc/ssl-admin/active/server.crt /usr/local/etc/ssl-admin/active/server.key /usr/local/etc/ssl-admin/active/dh1024.pem server 172.30.0.0 255.255.255.0 # this is necessary for clients to reach # clients behind the openvpn gateways client-to-client keepalive 10 120 ## allow multiple access from the same client duplicate-cn user vpn group vpn persist-key persist-tun status log-append /var/openvpn/openvpn-status.log /var/log/openvpn.log verb 4 crl-verify /usr/local/etc/ssl-admin/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.
5 z 5 01.10.2012 08:16 dev tun - What device to use. Use tun for routed OpenVPN. ca/cert/key/dh - If you're using my ssl-admin.pl 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. 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 http://openvpn.net/howto.html#config. 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 Retrieved from "http://www.secure-computing.net /wiki/index.php?title=freebsd_openvpn_server/routed&oldid=1795" Categories: OpenVPN FreeBSD HowTo This page was last modified on 26 January 2011, at 09:23. This page has been accessed 31,273 times.