From Fedora Project Wiki

Revision as of 22:12, 17 February 2011 by Ricky (talk | contribs) (Use umask instead of chmodding.)

Infrastructure InfrastructureTeamN1.png

OpenVPN is our server->server VPN solution. It is deployed in a routeless manner and uses puppet managed keys for authentication. All hosts should be given static IP's and a DNS address.

Contact Information

Owner: Fedora Infrastructure Team

Contact: #fedora-admin, sysadmin-main

Location: Phoenix

Servers: bastion (

Purpose: Provides vpn solution for our infrastructure.

Add a new host

Create/sign the keys

From puppet01 check out the private repo:

# This is to ensure that the clone of the is not world-readable.
RESTORE_UMASK=$(umask -p)
umask 0077
git clone /git/private
cd private/vpn/openvpn

Next prepare your environment and run the build-key script. This example is for host ""

. ./vars
./build-key $FQDN # ./revoke-full $FQDN to revoke keys that are no longer used.
git add .
git commit -a
git push

Create Static IP

Giving static IP's out in openvpn is mostly painless. Take a look at other examples but each host gets a file and 2 IP's. Also make sure to restart puppet on bastion *before* pushing changes out to hour new node.

git clone /git/puppet
vi puppet/modules/openvpn/files/ccd/$FQDN

The file format should look like this:


Basically the first IP is the IP that is contactable over the vpn and should always take the format "192.168.1.x" and the PtPIP is the same ip on a different network: "192.168.0.x"

Commit and install:

git add .
git commit -m "What have you done?"
git push

Create DNS entry

After you have your static IP ready, just add the entry to DNS:

From your puppet checkout, run:

vi modules/bind/files/master/
git commit -m "What have you done?"
git push

Wait for bastion and ns01/02 to get updated, then restart /sbin/service openvpn on the new machine.

Update resolv.conf on the client

To make sure traffic actually goes over the VPN, make sure the search line in /etc/resolv.conf looks like:


for external hosts and


for PHX2 hosts.


Deploy an additional VPN server outside of PHX. OpenVPN does support failover automatically so if configured properly, when the primary VPN server goes down all hosts should connect to the next host in the list.