(Don't mention the old outdated Windows client) |
|||
Line 95: | Line 95: | ||
On the client: | On the client: | ||
# Install the [http://openvpn. | # Install the the [http://openvpn.net/index.php/open-source/downloads.html OpenVPN Windows client]. | ||
# Copy ''username''.crt, ''username''.key, and ca.crt to <code>C:\Program Files\OpenVPN\config\</code> on the client. | # Copy ''username''.crt, ''username''.key, and ca.crt to <code>C:\Program Files\OpenVPN\config\</code> on the client. | ||
# Drop roadwarrior-client.conf into <code>C:\Program Files\OpenVPN\config\</code> as ''whatever''.ovpn and edit appropriately. | # Drop roadwarrior-client.conf into <code>C:\Program Files\OpenVPN\config\</code> as ''whatever''.ovpn and edit appropriately. |
Revision as of 13:51, 4 September 2014
OpenVPN
For more information, see https://community.openvpn.net/.
Working with systemd
With the transition to systemd, OpenVPN no longer has a single monolithic init script, where every connection with a configuration file in /etc/openvpn/
is started automatically. Instead, individual connections can be started and stopped with systemctl
.
For example, to start a connection, run systemctl start openvpn@
foo.service
, where the connection is defined in /etc/openvpn/
foo.conf
.
For more information, see Systemd#How_do_I_start.2Fstop_or_enable.2Fdisable_services.3F.
Setting up an OpenVPN server
yum install openvpn easy-rsa
- Copy
/usr/share/easy-rsa/2.0
somewhere (like root's home directory withcp -ai /usr/share/easy-rsa/2.0 ~/easy-rsa
). cd ~/easy-rsa
- Edit
vars
appropriately. . vars
./clean-all
- Before continuing, make sure the system time is correct. Preferably, set up NTP .
./build-ca
./build-key-server $( hostname | cut -d. -f1 )
./build-dh
mkdir /etc/openvpn/keys
cp -ai keys/$( hostname | cut -d. -f1 ).{crt,key} keys/ca.crt keys/dh*.pem /etc/openvpn/keys/
cp -ai /usr/share/doc/openvpn*/sample/sample-config-files/roadwarrior-server.conf /etc/openvpn/server.conf
- Edit
/etc/openvpn/server.conf
appropriately to set your configuration and key paths, which are found in /etc/openvpn/keys/. - Fix selinux context of files:
restorecon -Rv /etc/openvpn
ln -s /lib/systemd/system/openvpn\@.service /etc/systemd/system/multi-user.target.wants/openvpn\@server.service
(Note that 'server' corresponds with the configuration name in /etc/openvpn/ such as server.conf)systemctl -f enable openvpn@server.service
systemctl start openvpn@server.service
- Verify that firewall rules allow traffic in from
tun+
, out from the LAN totun+
, and in from the outside on UDP port 1194.
The following should work (assuming an outside interface is eth1 and an inside interface is eth0):
iptables -A INPUT -i eth1 -p udp --dport 1194 -j ACCEPT iptables -A INPUT -i tun+ -j ACCEPT iptables -A FORWARD -i tun+ -j ACCEPT iptables -A FORWARD -i eth0 -o tun+ -j ACCEPT iptables -A FORWARD -i eth1 -o tun+ -m state --state ESTABLISHED,RELATED -j ACCEPT
Or for genfw (my firewall-generation script, not currently available in Fedora), this in /etc/sysconfig/genfw/rules
:
append INPUT -i eth1 -p udp --dport 1194 -j ACCEPT append INPUT -i tun+ -j ACCEPT append FORWARD -i tun+ -j ACCEPT append FORWARD -i eth0 -o tun+ -j ACCEPT append FORWARD -i eth1 -o tun+ -j established
Or for system-config-firewall, you can add these custom rules:
-A INPUT -i eth1 -p udp --dport 1194 -j ACCEPT -A INPUT -i tun+ -j ACCEPT -A FORWARD -i tun+ -j ACCEPT -A FORWARD -i eth0 -o tun+ -j ACCEPT -A FORWARD -i eth1 -o tun+ -m state --state ESTABLISHED,RELATED -j ACCEPT
Create a file iptables-rules in /etc/sysconfig and add the above contents, then in system-config-firewall, choose the "Custom Rules" choice, click "Add", choose IPV4 for the protocol type, and filter for the firewall table. Then select /etc/sysconfig/iptables-rules for the File: choice. Then Apply the changes.
Setting up a Linux OpenVPN client
You need to generate new keys (or use existing other client/username keys) for the new client/username
On the server:
cd easy-rsa
. vars
./build-key
username
On the client:
- In the following, replace MyClient with a descriptive vpn connection name.
- Copy username.key, username.crt and ca.crt from server to
/etc/openvpn/keys/
. cp -ai /usr/share/doc/openvpn-*/sample-config-files/client.conf /etc/openvpn/MyClient.conf
- Edit
/etc/openvpn/MyClient.conf
appropriately to set your configuration (just like server configuration, port, compression,..) and key paths. cd /lib/systemd/system
ln openvpn@.service openvpn@MyClient.service
systemctl enable openvpn@MyClient.service
systemctl start openvpn@MyClient.service
check /var/log/messages
if things didn't work as expected
Alternatively, on the client, after copying the keys onto the client machine, you can use NetworkManager to add a vpn connection. Make sure you have the NetworkManager-openvpn package installed. Then just add a new VPN connection.
Should also test automatic starting at boot up, with password protected key files and maybe even --auth-user-pass. OpenVPN supports systemd's password passing if build with --enable-systemd via ./configure
Setting up a Windows OpenVPN client
On the server:
cd easy-rsa
. vars
./build-key
username
On the client:
- Install the the OpenVPN Windows client.
- Copy username.crt, username.key, and ca.crt to
C:\Program Files\OpenVPN\config\
on the client. - Drop roadwarrior-client.conf into
C:\Program Files\OpenVPN\config\
as whatever.ovpn and edit appropriately. - Either use the GUI to start the connection, start the OpenVPN service manually, or set the OpenVPN service to start automatically.
Ideally the client should do some verification on the server key with tls-remote
in the whatever.ovpn configuration file.