====== OpenVPN - How to Set Up a Slackware Server and a Slackware Client ======

====== OpenVPN - How to Set Up a Slackware Server and a Slackware Client ======

Line 19:

Line 20:

===== 3. Installation =====

===== 3. Installation =====

-

Openvpn is already installed on Slackware if a default installation was followed. If this was not the case, then the package is available from the “n” directory of the Slackware DVD. Refer to other Slackware specific documents on how to go about this installation.

+

Openvpn is already installed on Slackware if a default installation was followed. If this was not the case, then the package is available from the "n" ​directory of the Slackware DVD. Refer to other Slackware specific documents on how to go about this installation.

If you want to confirm that Openvpn is indeed installed, you can check it by listing the /​var/​log/​packages/​ directory:

If you want to confirm that Openvpn is indeed installed, you can check it by listing the /​var/​log/​packages/​ directory:

Line 33:

Line 34:

==== 4.1. Server DNS ====

==== 4.1. Server DNS ====

-

A URL is normally used to address the Server. This is not mandatory and instead you may use only the Internet IP. However it is recommended to use a URL to access the Server from the Internet, especially if it is connected to a dynamic IP, which is typical for domestic Internet connections. The author is using noip2(4) as it is free upon subscription. ​Noip2 is available from http://​slackbuilds.org.

+

A URL is normally used to address the Server. This is not mandatory and instead you may use only the Internet IP. However it is recommended to use a URL to access the Server from the Internet, especially if it is connected to a dynamic IP, which is typical for domestic Internet connections. The author is using noip2(4) as it is free upon subscription. ​A noip2 slackbuild ​is available from http://​slackbuilds.org.

==== 4.2. Server details ====

==== 4.2. Server details ====

Line 54:

Line 55:

==== 4.3 Administrator Rights ====

==== 4.3 Administrator Rights ====

-

You will need to have administrator rights to set up the Openvpn. This applies to both the Server and the Client. For simplicity, in this tutorial, it will be assumed that all actions will be performed by the root user. Naturally advanced users might be more discerning.

+

You will need to have administrator rights to set up OpenVPN. This applies to both the Server and the Client. For simplicity, in this tutorial, it will be assumed that all actions will be performed by the root user. Naturally advanced users might be more discerning.

Confirm the request by entering ​“yes”, then enter original ca PEM passphrase.

+

Confirm the request by entering ​"yes", then enter the original ca PEM passphrase.

Now create two additional key files:

Now create two additional key files:

Line 123:

Line 124:

Follow these steps on the Client to create the needed keys and certificates:​

Follow these steps on the Client to create the needed keys and certificates:​

-

You will need the easy-rsa scripts, so you can copy easy-rsa tarball from the Server to the Client and extract it:

+

You will need the easy-rsa scripts, so you can copy the easy-rsa tarball from the Server to the Client and extract it:

<​code>​

<​code>​

Line 138:

Line 139:

</​code>​

</​code>​

-

You will be prompted for another PEM pass phrase, to re-verify it and to confirm that the name of the entity is indeed client1. In this article I am using the hostnames for clarity (in this case: cleint1), but you may choose any name.

+

You will be prompted for another PEM pass phrase, to re-verify it and to confirm that the name of the entity is indeed client1. In this article I am using the hostnames for clarity (in this case: client1), but you may choose any name.

If you want to run the server as a daemon on system boot, it's necessary to remove the pass-phrase from the server1.key file first. ​ Don't forget to set permissions on the key to avoid it being world-readable.

+

Copy the sample server.conf from the OpenVPN ​source onto the OpenVPN's configuration directory. The source of OpenVPN ​may be obtained from Slackware'​s source DVD or your favourite Slackware mirror or from http://​openvpn.net. In the following example, I am downloading the source from ftp.slackware.com

-

+

-

<​code>​

+

-

# cd /​etc/​openvpn/​keys

+

-

# openssl rsa -in server1.key -out tmp.key

+

-

# mv tmp.key server1.key

+

-

# chmod 600 server1.key

+

-

</​code>​

+

-

+

-

Copy the sample server.conf from the openvpn ​source onto the openvpn's configuration directory. The source of openvpn ​may be obtained from Slackware'​s source DVD or your favourite Slackware mirror or from http://​openvpn.net. In the following example I am downloading the source from ftp.slackware.com

+

<​code>​

<​code>​

Line 189:

Line 181:

</​code>​

</​code>​

-

Copy the file server.conf contained in the source to the openvpn ​configuration directory:

+

Copy the file server.conf contained in the source to the OpenVPN ​configuration directory:

<​code>​

<​code>​

Line 235:

Line 227:

<​code>​

<​code>​

+

# Select a cryptographic cipher.

+

# This config item must be copied to

+

# the client config file as well.

+

cipher AES-256-CBC

# If you want to use OpenVPN as a daemon, uncomment this line.

# If you want to use OpenVPN as a daemon, uncomment this line.

# Generally speaking, servers should run OpenVPN as a daemon

# Generally speaking, servers should run OpenVPN as a daemon

-

daemon

+

;daemon

</​code>​

</​code>​

-

<​note>​It may be useful ​to leave off the '​daemon'​ option ​while getting things up and running so you can see useful messages in the foreground.</​note>​

+

<​note>​An attentive reader ​may be tempted ​to uncomment ​the '​daemon'​ option. This would not allow the user to enter the pass phrase, therefore it would not work until the pass phrase is defined in server.conf as described in Chapter 10.</​note>​

-

+

-

My full server.conf is the following:

+

<​code>​

<​code>​

-

#################################################​

+

# cat /​var/​log/​openvpn.log

-

# Sample OpenVPN 2.0 config file for #

+

-

# multi-client server. ​ #

+

-

# #

+

-

# This file is for the server side #

+

-

# of a many-clients <-> one-server ​ #

+

-

# OpenVPN configuration. ​ #

+

-

# #

+

-

# OpenVPN also supports ​ #

+

-

# single-machine <-> single-machine ​ #

+

-

# configurations (See the Examples page #

+

-

# on the web site for more info). ​ #

+

-

# #

+

-

# This config should work on Windows ​ #

+

-

# or Linux/BSD systems. ​ Remember on #

+

-

# Windows to quote pathnames and use #

+

-

# double backslashes,​ e.g.: #

+

-

# "​C:​\\Program Files\\OpenVPN\\config\\foo.key"​ #

+

-

# #

+

-

# Comments are preceded with '#'​ or ';' ​ #

+

-

#################################################​

+

-

+

-

# Which local IP address should OpenVPN

+

-

# listen on? (optional)

+

-

;local a.b.c.d

+

-

+

-

# Which TCP/UDP port should OpenVPN listen on?

+

-

# If you want to run multiple OpenVPN instances

+

-

# on the same machine, use a different port

+

-

# number for each one. You will need to

+

-

# open up this port on your firewall.

+

-

port 1194

+

-

+

-

# TCP or UDP server?

+

-

;proto tcp

+

-

proto udp

+

-

+

-

# "dev tun" will create a routed IP tunnel,

+

-

# "dev tap" will create an ethernet tunnel.

+

-

# Use "dev tap0" if you are ethernet bridging

+

-

# and have precreated a tap0 virtual interface

+

-

# and bridged it with your ethernet interface.

+

-

# If you want to control access policies

+

-

# over the VPN, you must create firewall

+

-

# rules for the the TUN/TAP interface.

+

-

# On non-Windows systems, you can give

+

-

# an explicit unit number, such as tun0.

+

-

# On Windows, use "​dev-node"​ for this.

+

-

# On most systems, the VPN will not function

+

-

# unless you partially or fully disable

+

-

# the firewall for the TUN/TAP interface.

+

-

;dev tap

+

-

dev tun

+

-

+

-

# Windows needs the TAP-Win32 adapter name

+

-

# from the Network Connections panel if you

+

-

# have more than one. On XP SP2 or higher,

+

-

# you may need to selectively disable the

+

-

# Windows firewall for the TAP adapter.

+

-

# Non-Windows systems usually don't need this.

+

-

;dev-node MyTap

+

-

+

-

# SSL/TLS root certificate (ca), certificate

+

-

# (cert), and private key (key). ​ Each client

+

-

# and the server must have their own cert and

+

-

# key file. The server and all clients will

+

-

# use the same ca file.

+

-

#

+

-

# See the "​easy-rsa"​ directory for a series

+

-

# of scripts for generating RSA certificates

+

-

# and private keys. Remember to use

+

-

# a unique Common Name for the server

+

-

# and each of the client certificates.

+

-

#

+

-

# Any X509 key management system can be used.

+

-

# OpenVPN can also use a PKCS #12 formatted key file

+

-

# (see "​pkcs12"​ directive in man page).

+

-

ca /​etc/​openvpn/​certs/​ca.crt

+

-

cert /​etc/​openvpn/​certs/​server1.crt

+

-

key /​etc/​openvpn/​keys/​server1.key ​ # This file should be kept secret

+

-

+

-

# Diffie hellman parameters.

+

-

# Generate your own with:

+

-

# ​openssl dhparam -out dh1024.pem 1024

+

-

# Substitute 2048 for 1024 if you are using

+

-

# 2048 bit keys.

+

-

dh /​etc/​openvpn/​certs/​dh2048.pem

+

-

+

-

# Configure server mode and supply a VPN subnet

+

-

# for OpenVPN to draw client addresses from.

+

-

# The server will take 10.8.0.1 for itself,

+

-

# the rest will be made available to clients.

+

-

# Each client will be able to reach the server

+

-

# on 10.8.0.1. Comment this line out if you are

+

-

# ethernet bridging. See the man page for more info.

+

-

server 10.8.0.0 255.255.255.0

+

-

+

-

# Maintain a record of client <-> virtual IP address

+

-

# associations in this file. If OpenVPN goes down or

+

-

# is restarted, reconnecting clients can be assigned

+

-

# the same virtual IP address from the pool that was

+

-

# previously assigned.

+

-

ifconfig-pool-persist ipp.txt

+

-

+

-

# Configure server mode for ethernet bridging.

+

-

# You must first use your OS's bridging capability

+

-

# to bridge the TAP interface with the ethernet

+

-

# NIC interface. ​ Then you must manually set the

+

-

# IP/netmask on the bridge interface, here we

+

-

# assume 10.8.0.4/​255.255.255.0. ​ Finally we

+

-

# must set aside an IP range in this subnet

+

-

# (start=10.8.0.50 end=10.8.0.100) to allocate

+

-

# to connecting clients. ​ Leave this line commented

+

-

# out unless you are ethernet bridging.

+

-

;​server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

+

-

+

-

# Configure server mode for ethernet bridging

+

-

# using a DHCP-proxy, where clients talk

+

-

# to the OpenVPN server-side DHCP server

+

-

# to receive their IP address allocation

+

-

# and DNS server addresses. ​ You must first use

+

-

# your OS's bridging capability to bridge the TAP

+

-

# interface with the ethernet NIC interface.

+

-

# Note: this mode only works on clients (such as

+

-

# Windows), where the client-side TAP adapter is

+

-

# bound to a DHCP client.

+

-

;​server-bridge

+

-

+

-

# Push routes to the client to allow it

+

-

# to reach other private subnets behind

+

-

# the server. ​ Remember that these

+

-

# private subnets will also need

+

-

# to know to route the OpenVPN client

+

-

# address pool (10.8.0.0/​255.255.255.0)

+

-

# back to the OpenVPN server.

+

-

;push "route 192.168.10.0 255.255.255.0"​

+

-

;push "route 192.168.20.0 255.255.255.0"​

+

-

+

-

# To assign specific IP addresses to specific

+

-

# clients or if a connecting client has a private

+

-

# subnet behind it that should also have VPN access,

+

-

# use the subdirectory "​ccd"​ for client-specific

+

-

# configuration files (see man page for more info).

+

-

+

-

# EXAMPLE: Suppose the client

+

-

# having the certificate common name "​Thelonious"​

+

-

# also has a small subnet behind his connecting

+

-

# machine, such as 192.168.40.128/​255.255.255.248.

+

-

# First, uncomment out these lines:

+

-

;​client-config-dir ccd

+

-

;route 192.168.40.128 255.255.255.248

+

-

# Then create a file ccd/​Thelonious with this line:

+

-

# ​iroute 192.168.40.128 255.255.255.248

+

-

# This will allow Thelonious'​ private subnet to

+

-

# access the VPN. This example will only work

+

-

# if you are routing, not bridging, i.e. you are

+

-

# using "dev tun" and "​server"​ directives.

+

-

+

-

# EXAMPLE: Suppose you want to give

+

-

# Thelonious a fixed VPN IP address of 10.9.0.1.

+

-

# First uncomment out these lines:

+

-

;​client-config-dir ccd

+

-

;route 10.9.0.0 255.255.255.252

+

-

# Then add this line to ccd/​Thelonious:​

+

-

# ​ifconfig-push 10.9.0.1 10.9.0.2

+

-

+

-

# Suppose that you want to enable different

+

-

# firewall access policies for different groups

+

-

# of clients. ​ There are two methods:

+

-

# (1) Run multiple OpenVPN daemons, one for each

+

-

# ​group,​ and firewall the TUN/TAP interface

+

-

# for each group/​daemon appropriately.

+

-

# (2) (Advanced) Create a script to dynamically

+

-

# ​modify the firewall in response to access

+

-

# from different clients. ​ See man

+

-

# page for more info on learn-address script.

+

-

;​learn-address ./script

+

-

+

-

# If enabled, this directive will configure

+

-

# all clients to redirect their default

+

-

# network gateway through the VPN, causing

+

-

# all IP traffic such as web browsing and

+

-

# and DNS lookups to go through the VPN

+

-

# (The OpenVPN server machine may need to NAT

+

-

# or bridge the TUN/TAP interface to the internet

+

-

# in order for this to work properly).

+

-

;push "​redirect-gateway def1 bypass-dhcp"​

+

-

+

-

# Certain Windows-specific network settings

+

-

# can be pushed to clients, such as DNS

+

-

# or WINS server addresses. ​ CAVEAT:

+

-

# http://​openvpn.net/​faq.html#​dhcpcaveats

+

-

# The addresses below refer to the public

+

-

# DNS servers provided by opendns.com.

+

-

;push "​dhcp-option DNS 208.67.222.222"​

+

-

;push "​dhcp-option DNS 208.67.220.220"​

+

-

+

-

# Uncomment this directive to allow different

+

-

# clients to be able to "​see"​ each other.

+

-

# By default, clients will only see the server.

+

-

# To force clients to only see the server, you

+

-

# will also need to appropriately firewall the

+

-

# server'​s TUN/TAP interface.

+

-

;​client-to-client

+

-

+

-

# Uncomment this directive if multiple clients

+

-

# might connect with the same certificate/​key

+

-

# files or common names. ​ This is recommended

+

-

# only for testing purposes. ​ For production use,

+

-

# each client should have its own certificate/​key

+

-

# pair.

+

-

#

+

-

# IF YOU HAVE NOT GENERATED INDIVIDUAL

+

-

# CERTIFICATE/​KEY PAIRS FOR EACH CLIENT,

+

-

# EACH HAVING ITS OWN UNIQUE "​COMMON NAME",​

+

-

# UNCOMMENT THIS LINE OUT.

+

-

;​duplicate-cn

+

-

+

-

# The keepalive directive causes ping-like

+

-

# messages to be sent back and forth over

+

-

# the link so that each side knows when

+

-

# the other side has gone down.

+

-

# Ping every 10 seconds, assume that remote

+

-

# peer is down if no ping received during

+

-

# a 120 second time period.

+

-

keepalive 10 120

+

-

+

-

# For extra security beyond that provided

+

-

# by SSL/TLS, create an "HMAC firewall"​

+

-

# to help block DoS attacks and UDP port flooding.

+

-

#

+

-

# Generate with:

+

-

# ​openvpn --genkey --secret ta.key

+

-

#

+

-

# The server and each client must have

+

-

# a copy of this key.

+

-

# The second parameter should be '​0'​

+

-

# on the server and '​1'​ on the clients.

+

-

tls-auth /​etc/​openvpn/​keys/​ta.key 0 # This file is secret

+

-

+

-

# Select a cryptographic cipher.

+

-

# This config item must be copied to

+

-

# the client config file as well.

+

-

;cipher BF-CBC ​ # Blowfish (default)

+

-

;cipher AES-128-CBC ​ # AES

+

-

;cipher DES-EDE3-CBC ​ # Triple-DES

+

-

+

-

# Enable compression on the VPN link.

+

-

# If you enable it here, you must also

+

-

# enable it in the client config file.

+

-

comp-lzo

+

-

+

-

# The maximum number of concurrently connected

+

-

# clients we want to allow.

+

-

;​max-clients 100

+

-

+

-

# It's a good idea to reduce the OpenVPN

+

-

# daemon'​s privileges after initialization.

+

-

#

+

-

# You can uncomment this out on

+

-

# non-Windows systems.

+

-

user nobody

+

-

group nobody

+

-

+

-

# The persist options will try to avoid

+

-

# accessing certain resources on restart

+

-

# that may no longer be accessible because

+

-

# of the privilege downgrade.

+

-

persist-key

+

-

persist-tun

+

-

+

-

# Output a short status file showing

+

-

# current connections,​ truncated

+

-

# and rewritten every minute.

+

-

status openvpn-status.log

+

-

+

-

# By default, log messages will go to the syslog (or

+

-

# on Windows, if running as a service, they will go to

+

-

# the "​\Program Files\OpenVPN\log"​ directory).

+

-

# Use log or log-append to override this default.

+

-

# "​log"​ will truncate the log file on OpenVPN startup,

+

-

# while "​log-append"​ will append to it. Use one

+

-

# or the other (but not both).

+

-

;log ​openvpn.log

+

-

log-append ​/​var/​log/​openvpn.log

+

-

+

-

# Set the appropriate level of log

+

-

# file verbosity.

+

-

#

+

-

# 0 is silent, except for fatal errors

+

-

# 4 is reasonable for general usage

+

-

# 5 and 6 can help to debug connection problems

+

-

# 9 is extremely verbose

+

-

verb 3

+

-

+

-

# Silence repeating messages. ​ At most 20

+

-

# sequential messages of the same message

+

-

# category will be output to the log.

+

-

;mute 20

+

-

+

-

# If you want to use OpenVPN as a daemon, uncomment this line.

+

-

# Generally speaking, servers should run OpenVPN as a daemon

+

-

daemon

+

</​code>​

</​code>​

Line 559:

Line 251:

# /​etc/​rc.d/​rc.openvpn ​

# /​etc/​rc.d/​rc.openvpn ​

#

#

-

# Start/​stop/​restart the openvpn ​server. ​

+

# Start/​stop/​restart the OpenVPN ​server. ​

#

#

Line 598:

Line 290:

<​code>​

<​code>​

# chmod 755 /​etc/​rc.d/​rc.openvpn

# chmod 755 /​etc/​rc.d/​rc.openvpn

-

</​code>​

-

-

Eventually when you start openvpn on the server, you may read /​var/​log/​openvpn.log to verify that your work has been successful:

-

-

<​code>​

-

# cat /​var/​log/​openvpn.log

</​code>​

</​code>​

===== 7. Port Forwarding =====

===== 7. Port Forwarding =====

-

You will need to forward traffic from the port you have chosen for Openvpn ​to be routed to the Server. To accomplish this you will need to provide your Server with a fixed IP and you will need to configure your router. You may use netconfig, ​wicd or network-manager to set the fixed IP on Slackware. Then you also need to consult the documentation provided with your router to set up the selected IP address reserved for the Server, and the port forwarding. For our default ​Openvpn ​set up, the UDP Port would be 1194.

+

You will need to forward traffic from the port you have chosen for OpenVPN ​to be routed to the Server. To accomplish this you will need to provide your Server with a fixed IP and you will need to configure your router. You may use netconfig, network-manager ​or wicd to set the fixed IP on Slackware. Then you also need to consult the documentation provided with your router to set up the selected IP address reserved for the Server, and the port forwarding. For our default ​OpenVPN ​set up, the UDP Port would be 1194.

In case if you have misplaced such documentation,​ you may search on the Internet on how this may be achieved. A good place to start is http://​portforward.com/​.

In case if you have misplaced such documentation,​ you may search on the Internet on how this may be achieved. A good place to start is http://​portforward.com/​.

Line 616:

Line 302:

On the Client machine perform the following instructions to set it up.

On the Client machine perform the following instructions to set it up.

-

Download the openvpn ​source tarball and extracted it as explained in Chapter 6, then proceed to copy the included configuration file for clients:

+

Download the OpenVPN ​source tarball and extracted it as explained in Chapter 6, then proceed to copy the included configuration file for clients:

<​code>​

<​code>​

Line 653:

Line 339:

</​code>​

</​code>​

-

<​note>​Note that comments in client.conf ​may be either # or ; The former are used to comment out text while the latter are for commented out configuration lines. This should help you a lot in the configuration process.</​note>​

+

Finally add the following to /​etc/​openvpn/​client.conf:​

-

+

-

You will need this file that were generated by the Client'​s easy-rsa scripts:

+

<​code>​

<​code>​

-

$HOME/​easy-rsa/​easyrsa3/​pki/​private/​client1.key

+

# Select a cryptographic cipher.

+

# This config item must be copied to

+

# the server config file as well.

+

cipher AES-256-CBC

</​code>​

</​code>​

-

and the following from the Server's easy-rsa scripts:

+

<​note>​Note that comments in client.conf may be either # or ; The former are used to comment out text while the latter are for commented out configuration lines. This should help you a lot in the configuration process.</​note>​

+

+

You will need this file that was generated by the Client's easy-rsa scripts:

<​code>​

<​code>​

-

ca.crt

+

cp $HOME/​easy-rsa/​easyrsa3/​pki/​private/​client1.key \

-

ta.key

+

> /​etc/​openvpn/​keys/​

</​code>​

</​code>​

-

You will also need client1.crt generated by the Server ​as explained above in Chapter 5.2.1.

+

and the following from the Server's easy-rsa scripts:

-

+

-

Place these files as indicated in client.conf. So ca.crt and client1.crt go under /​etc/​openvpn/​certs/​ while client1.key and ta.key go under /​etc/​openvpn/​keys/​

+

-

+

-

Also in client.conf,​ comment out the line:

+

<​code>​

<​code>​

-

ns-cert-type server

+

$HOME/easy-rsa/​easyrsa3/​pki/​ca.crt

+

$HOME/easy-rsa/​easyrsa3/​pki/​issued/​client1.crt

</​code>​

</​code>​

-

and insert the line:

+

and this file as well:

<​code>​

<​code>​

-

remote-cert-tls server

+

/​etc/​openvpn/​keys/​ta.key

</​code>​

</​code>​

-

My full client.conf is the following:​

+

Place these files as indicated ​in client.conf. So ca.crt ​and client1.crt ​go under /​etc/​openvpn/​certs/ while client1.key ​and ta.key go under /​etc/​openvpn/​keys/​

On both you should see a new network interface called tun0. On the Server, I obtained the following:

On both you should see a new network interface called tun0. On the Server, I obtained the following:

Line 875:

Line 434:

===== 10. Storing the PEM pass phrase in a secure file and Automatic start of service after booting =====

===== 10. Storing the PEM pass phrase in a secure file and Automatic start of service after booting =====

-

To start the Openvpn ​service on boot, an entry in /​etc/​rc.d/​rc.local is needed, but you would have to enter the server PEM pass phrase every time. This might be undesirable if the Server is unreachable. If this is the case, create a file containing your PEM pass phrase in a secure location; e.g. /​root/​password.ovpn which contains only this pass phrase. Then restrict its permission:

+

To start the OpenVPN ​service on boot, an entry in /​etc/​rc.d/​rc.local is needed, but you would have to enter the server PEM pass phrase every time. This might be undesirable if the Server is unreachable. If this is the case, create a file containing your PEM pass phrase in a secure location; e.g. /​root/​password.ovpn which contains only this pass phrase. Then restrict its permission:

<​code>​

<​code>​

Line 887:

Line 446:

auth-nocache

auth-nocache

</​code>​

</​code>​

+

+

Also, uncomment the '​daemon'​ option.

This may be repeated also on the Client, just edit /​etc/​openvpn/​client.conf instead of /​etc/​openvpn/​server.conf.

This may be repeated also on the Client, just edit /​etc/​openvpn/​client.conf instead of /​etc/​openvpn/​server.conf.

-

To start the Openvpn ​service automatically on boot-up from the Server, include these lines in /​etc/​rc.d/​rc.local

+

To start the OpenVPN ​service automatically on boot-up from the Server, include these lines in /​etc/​rc.d/​rc.local

<​code>​

<​code>​

Line 898:

Line 459:

fi

fi

</​code>​

</​code>​

+

+

An alternate method (albeit less secure) is to remove the passphrase from server1.key file altogether. ​ Don't forget to set permissions on the key to avoid it being world-readable.

In the previous chapter we referred to a firewall you may include to protect your Openvpn ​Server. ​ However this chapter refers to firewalls on the Client LAN that may block the VPN connection by blocking traffic on UDP port 1194.

+

In the previous chapter we referred to a firewall you may include to protect your OpenVPN ​Server. ​ However this chapter refers to firewalls on the Client LAN that may block the VPN connection by blocking traffic on UDP port 1194.

In order to penetrate through the Client firewall your may want to try changing the port to 443 - normally reserved for https. Using TCP instead of UDP will also help. To make these change you will need to amend /​etc/​openvpn/​server.conf of the Server, from

In order to penetrate through the Client firewall your may want to try changing the port to 443 - normally reserved for https. Using TCP instead of UDP will also help. To make these change you will need to amend /​etc/​openvpn/​server.conf of the Server, from