OpenVPN Bridge
Maintainer
Daniel B. from Firewall Services
Version
Description
OpenVPN is a full-featured open source SSL VPN solution that accommodates a wide range of configurations, including remote access, site-to-site VPNs, Wi-Fi security, and enterprise-scale remote access solutions with load balancing, fail-over, and fine-grained access-controls. Starting with the fundamental premise that complexity is the enemy of security, OpenVPN offers a cost-effective, lightweight alternative to other VPN technologies that is well-targeted for the SME and enterprise markets.
This contrib will help you configuring OpenVPN in bridge mode. With this mode, clients connecting to the VPN from the outside will get an IP in the local subnet, the VPN and the Internal Interface are bridged. There's no routing problem, no additional firewall rules. The downside is that you cannot limit which services VPN clients has access to, they are just treated as locally connected computers.
Requirements
- SME Server 7.X (serveronly or server&gateway works)
- You have to install and enable the bridge-interface contrib
- You may want to install PHPki to manage easily your certificates.
Installation
- install the rpms
yum --enablerepo=smecontribs install smeserver-openvpn-bridge
- Configure the certificates
You can now go in the server-manager, you'll find a new OpenVPN-Bridge menu. Here, you will first have to click on the "configure certificates" link.
Here, you'll need to enter several informations:
- An URL where OpenVPN can update the CRL. If you use PHPki on the same server, you can let the default value.
- A master Certificate (used to verify clients certificates)
- The server certificate (used by clients to verify the server)
- The server private key associated with the certificate
- Diffie-Helman parameters (Used to exchange the session key)
- An optional key generate by openvpn to add TLS authentication
You can use PHPki contrib to manage this easily. PHPki doesn't need to be installed on the same server. You can also manage your PKI by hands, or with your own PKI tool if you already use one (for example, tinyCA)
Once you have enter all the required information, just submit the form.
You should then see the message:
Certificates status Certificates are ready
With "Certificates are ready" in green. If it's not the case, you have a problem with the certificates configuration.
- Configure the service
The second step is to configure the service. In the main page of the panel, click on the "Service configuration" button.
Here you can enable the service, choose the authentication mode you want, and configure the IP address range for the clients
Once you submit this form, the service should start. You can check everything is ok with this command:
tailf /var/log/openvpn-bridge/current
Using PHPki to manage the certificates
With this new release, you can manage the certificates the way you want, but most of you will use PHPki for this.
- Initialize your PKI
This should already be done as you have installed the contrib following this how-to
- Create a certificate for the server
Now you need to create a certificate for OpenVPN on the server. For this, go in PHPki interface, then "create a new certificate". Here, you'll have to enter some informations about the certificate:
- Common Name: this is the name of the certificate. You can enter what you want, for example "openvpn-bridge"
- Email address: the email address of the technical contact (this field is not used, you can enter what you want as long as it's a valid email address), for example admin@domain.tld
- Organization, Department, Locality, State and Country fields should have the values you entered when you have created your PKI. You can let those values.
- Password: This field must be blank. Remember that OpenVPN daemon starts without human intervention when the server boots, so it need to have access to the certificate key without being prompted for a password.
- Certificate life: How-long the certificate will be valid. Enter what you want, but remember, when the certificate expires, you'll have to create another one, and deploy it on each client.
- Key size: you can enter what you want (I use 2048 in general). The bigger, the stronger, but will use a bit more CPU power when the session key is negotiated (at the connection, and once an hour)
- Certificate Use: you should use "VPN Server Only"
- Configure openvpn with the newly created certificates
Now, you can configure OpenVPN with your certificates. Go in the server-manager->OpenVPN-Bridge->certificates configuration.
Here you have some fields to setup:
- URL to update the CRL: you should let the default: http://localhost:940/phpki/index.php?stage=dl_crl_pem
- CA certificate: You should put here the Root certificate in PEM format. You can get it in PHPki, clicking on the link "Display the Root Certificate (PEM Encoded)"
- Server certificate: You should put here the certificate of the server. You can get it in PHPki, manage certificates, click on the download link corresponding to the certificate you have created for the server ("openvpn-bridge" in the example), choose PEM certificate in the drop-down menu, download it. You can open this file with a text editor.
- Server private key: This is the private key associated with the server's certificate. To get it, follow the same steps as above, but choose "PEM Key" in the drop-down menu instead of "PEM Certificate"
- DH Parameters: To get the DH Parameters, click on the "Display the Diffie-Hellman parameters" link in PHPki
- Static Key: This is optional. You can get it using the "Display the static pre-shared key" link in PHPki. Note that if you enter this key on the server, you'll have to deploy it on each client.
You can now submit the request. "Certificates are ready" should be displayed.
Upgrade from smeserver-openvpn-bridge-fws-1.1-2
If you was using the previous version of the contrib, you'll need some additional steps to migrate your configuration.
- Install PHPki
First, you'll have to install PHPki. Be sure to follow the migration step
- Install the new contrib
yum --enablerepo=smecontribs install smeserver-openvpn-bridge
You can configure the bridge-interface contrib now. You can follow this how-to
- Migrate OpenVPN Server certificates
Now, you should install the old certificates in the new location For this, you can use this script:
#!/bin/bash
# Store the actual time in $TIME
TIME=$(date +%d%m%Y%H%M%S)
OPENSSL=/usr/bin/openssl
OLDDIR=/etc/openvpn/easy-rsa/keys/bridge/
OVPNNEWDIR=/etc/openvpn/bridge
convert_cert_to_rule_entries(){
DBNAME='openvpn-bridge'
# The new openvpn contrib doesn't use cert entries but rules ones
# So we need to convert it
if [ -e /home/e-smith/db/$DBNAME ]; then
mv /home/e-smith/db/$DBNAME /home/e-smith/db/$DBNAME.$TIME
for CERT in $(/sbin/e-smith/db $DBNAME.$TIME keys); do
# If the entry is a cert and cert-type=client
if [ $(/sbin/e-smith/db $DBNAME.$TIME gettype $CERT) == 'cert' ]&&[ $(/sbin/e-smith/db $DBNAME.$TIME getprop $CERT cert-type) == 'client' ]; then
COM=$(/sbin/e-smith/db $DBNAME.$TIME getprop $CERT comment)
REDIR=$(/sbin/e-smith/db $DBNAME.$TIME getprop $CERT redirectGW)
IP=$(/sbin/e-smith/db $DBNAME.$TIME getprop $CERT ip)
# Blank out the IP if fefined as 'undef'
if [ $IP == 'undef' ]; then
IP=
fi
/sbin/e-smith/db $DBNAME set $CERT rule comment "$COM" redirectGW "$REDIR" ip "$IP"
fi
done
fi
}
install_cert_in_new_dir(){
# Here, we install the old certificates used by openvpn daemon to the new location
mkdir -p $OVPNNEWDIR/{priv,pub}
cat $OLDDIR/$SRVCN.crt > $OVPNNEWDIR/pub/cert.pem
cat $OLDDIR/$SRVCN.key > $OVPNNEWDIR/priv/key.pem
cat $OLDDIR/dh.pem > $OVPNNEWDIR/pub/dh.pem
cat $OLDDIR/ca.crt > $OVPNNEWDIR/pub/cacert.pem
cat $OLDDIR/ta.key > $OVPNNEWDIR/priv/takey.pem
cat $OLDDIR/crl.pem > $OVPNNEWDIR/pub/cacrl.pem
}
perms(){
# Restrict access
chown -R root:root $OVPNNEWDIR
chmod -R o-rwx $OVPNNEWDIR
}
convert_cert_to_rule_entries
install_cert_in_new_dir
perms
Save this script and run it as root.
Configuration rules
The configuration is the new way to apply specific configuration to a client. As now the certificates are managed separately, you have to create rules separately. It's still quite simple, just add a new rule, enter the common name to match, a comment, choose an optional fixed IP, choose to enable/disable the gateway redirection, or even block a specific client. Then save, and you're done.
Configuration file
On the main page of the panel, you can display a sample configuration file. This file is dynamically generated according to server-side configuration. Here, you'll just need to change the line
pkcs12 user.p12
or uncomment and change the lines
#ca cacert.pem #cert user.pem #key user-key.pem
to match the certificate name of the client
Advanced configuration
Some advanced options are not presented in the panel. The goal was to keep the panel as simple as possible as most installations won't need to change advanced settings. But advanced options are still available with some DB keys:
- ConfigRequired: (enabled|disabled). If set to enable, clients will be rejected un less a configuration rule match the common name of their certificate. This can be useful if you use just one CA to sign a lot of different certificates, but only want a limited number of certificates to connect to the VPN
- UDPPort: (number) Change the port the server listen to when running in UDP mode
- TCPPort: (number) Change the port the server listen to when running in TCP mode
- access: (private|public) you should let this to public as running a VPN server just for the local network make no sens
- cipher: (valid cipher name) You can force the cipher to use. If you put auto, or delete this key, client and server will negociate the stronger cipher both side support. To have the list of the supported cipher, issue the command
openvpn --show-ciphers
- clientToClient: (enabled|disabled) If you want to prevent two clients to communicate, you should enable this option
- compLzo: (enabled|disabled) This option control the usage of real time LZO compression. Enabling it usually improve the performance at no cost. It uses an adaptive algorithm, if data sent over the tunnel are uncompress-able, the compression will automatically be disabled. You may want to disable it on small hardware.
- management: (<ip to bind to>:<port>:password) this key control the management interface of openvpn. The default is to listen only on the loopback interface. It's used to display connected clients. You can allow the access on the local network to get some more statistics using for example: http://www.mertech.com.au/mertech-products-openvpnusermanager.aspx
- maxClients: (number) maximum number of clients connected at a time
- mtuTest: (enabled|disabled) When using UDP as transport protocol, mtu-test will measure the best MTU for the virtual interface. You should let it enabled unless you know what you're doing
- protocol: (udp|tcp) The transport protocol to use. UDP is recommended for both security and performance, but there are situations where you'll need to use TCP. If you use TCP, you should set TCPPort directive to set the port the daemon will listen on (instead of UDPPort)
- redirectGW: (perClient|always) The default is to enable the gateway redirection on a per client basis. But if you want the redirection to be always enabled, you can set this key to "always". This way, you won't have to create a new rule for each client.
- tapIf: (tap interface) use this tap interface. You should use a free tap interface enslaved in the bridge interface (configured with the bridge-interface contrib). Do not change this setting unless you know what you're doing
Once you have configured the service like you want, just run the command
signal-event openvpn-bridge-update
Uninstall
To remove the contrib, just run:
yum remove smeserver-openvpn-bridge
You may also want to remove some other dependencies if you don't use them anymore
yum remove smeserver-phpki phpki smeserver-bridge-interface perl-Net-OpenVPN-Manage perl-Net-Telnet
Bugs
Please raise bugs under the SME-Contribs section in bugzilla and select the smeserver-openvpn-bridge component or use this link
