[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
playground:openvpn_-_how_to_set_up_a_slackware_server_and_a_slackware_client [2013/11/22 19:24 (UTC)] – chrisabela | playground:openvpn_-_how_to_set_up_a_slackware_server_and_a_slackware_client [2018/04/06 21:16 (UTC)] – chrisabela | ||
---|---|---|---|
Line 11: | Line 11: | ||
===== 2. Scope and Objective ===== | ===== 2. Scope and Objective ===== | ||
- | The objective of this how-to | + | The objective of this article |
- | The emphasis | + | The emphasis is to provide a reliable method that can be easily |
- | This document | + | This article |
===== 3. Installation ===== | ===== 3. Installation ===== | ||
- | Openvpn is already installed on Slackware if a default installation was followed. If this was not the case, then it is available from the " | + | Openvpn is already installed on Slackware if a default installation was followed. If this was not the case, then the package |
If you want to confirm that Openvpn is indeed installed, you can check it by listing the / | If you want to confirm that Openvpn is indeed installed, you can check it by listing the / | ||
Line 25: | Line 25: | ||
< | < | ||
# ls / | # ls / | ||
- | / | ||
</ | </ | ||
===== 4. Requirements ===== | ===== 4. Requirements ===== | ||
- | A Server and a Client computers would be needed. They would have to be connected to the Internet on two different Routers and different Network Routes. | + | Server and a Client computers would be needed. They would have to be connected to the Internet on two different Routers and different Network Routes. |
==== 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 | + | A URL is normally used to address the Server. This is not mandatory and instead you may use only the Internet IP. However |
==== 4.2. Server details ==== | ==== 4.2. Server details ==== | ||
Line 40: | Line 39: | ||
< | < | ||
hostname: server1 | hostname: server1 | ||
- | IP: 192.168.200.199/ | + | IP: 192.168.200.195/ |
URL: servervpn.no-ip.org | URL: servervpn.no-ip.org | ||
Network Interface: eth0 | Network Interface: eth0 | ||
Line 49: | Line 48: | ||
< | < | ||
hostname: client1 | hostname: client1 | ||
- | IP: 192.168.1.234/ | + | IP: 192.168.1.101/ |
Network Interface: wlan0 | Network Interface: wlan0 | ||
</ | </ | ||
Line 55: | Line 54: | ||
==== 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. | + | You will need to have administrator rights to set up OpenVPN. This applies to both the Server and the Client. |
==== 4.4 Possible Constraints and Possible Solutions for a WiFi equipped Client ==== | ==== 4.4 Possible Constraints and Possible Solutions for a WiFi equipped Client ==== | ||
Line 67: | Line 66: | ||
===== 5. Creating a Public Key Infrastructure (PKI) using the easy-rsa Scripts ===== | ===== 5. Creating a Public Key Infrastructure (PKI) using the easy-rsa Scripts ===== | ||
- | The PKI may be created on any computer with an Openvpn | + | The PKI may be created on any computer with a VPN installation, |
- | + | ||
- | The easy-rsa scripts referred | + | |
- | + | ||
- | It is not recommended | + | |
- | + | ||
- | Download | + | |
< | < | ||
# cd | # cd | ||
- | # git clone git:// | + | # git clone http:// |
- | # cd easy-rsa/ | + | |
- | # cp vars.example vars | + | |
</ | </ | ||
- | Find the vars file. As a minimum | + | and then archive |
< | < | ||
- | KEY_COUNTRY | + | # tar cvf easy-rsa.tar easy-rsa |
- | KEY_PROVINCE | + | |
- | KEY_ORG | + | |
- | KEY_EMAIL | + | |
</ | </ | ||
- | The purpose of this recommendation is to assure consistency in the default values of some following steps that need to be followed. You should not be really worried about the exact meaning or the correctness of the chosen entries as the actual values will have no bearing on the success or failure of this exercise. | + | ==== 5.1 Create |
- | The following is my complete vars file. You may note some additional entries that were entered. Most of these are meant to enhance the range of default values that will be immediately available, thus increasing the chances of a successful creation of the PKI. | + | Follow |
< | < | ||
- | # Easy-RSA 3 parameter settings | + | # cd easy-rsa/easyrsa3 |
- | + | ||
- | # NOTE: If you installed Easy-RSA from your distro' | + | |
- | # this file in place -- instead, you should copy the entire | + | |
- | # to another location so future upgrades don't wipe out your changes. | + | |
- | + | ||
- | # HOW TO USE THIS FILE | + | |
- | # | + | |
- | # vars.example contains built-in examples to Easy-RSA settings. You MUST name | + | |
- | # this file ' | + | |
- | # not, it WILL NOT be automatically read when you call easyrsa commands. | + | |
- | # | + | |
- | # It is not necessary to use this config file unless you wish to change | + | |
- | # operational defaults. These defaults should be fine for many uses without the | + | |
- | # need to copy and edit the ' | + | |
- | # | + | |
- | # All of the editable settings are shown commented and start with the command | + | |
- | # ' | + | |
- | # modified by the user. If you're happy with a default, there is no need to | + | |
- | # define the value to its default. | + | |
- | + | ||
- | # NOTES FOR WINDOWS USERS | + | |
- | # | + | |
- | # Paths for Windows | + | |
- | # backslashes (single forward slashes are recommended.) This means your path to | + | |
- | # the openssl binary might look like this: | + | |
- | # "C:/Program Files/ | + | |
- | + | ||
- | # A little housekeeping: | + | |
- | # | + | |
- | # Easy-RSA 3.x doesn' | + | |
- | # Complain if a user tries to do this: | + | |
- | if [ -z " | + | |
- | echo "You appear to be sourcing an Easy-RSA ' | + | |
- | echo "This is no longer necessary and is disallowed. See the section called" | + | |
- | echo "' | + | |
- | return 1 | + | |
- | fi | + | |
- | + | ||
- | # DO YOUR EDITS BELOW THIS POINT | + | |
- | + | ||
- | # This variable should point to the top level of the easy-rsa tree. By default, | + | |
- | # this is taken to be the directory you are currently in. | + | |
- | + | ||
- | #set_var EASYRSA | + | |
- | + | ||
- | # If your OpenSSL command is not in the system PATH, you will need to define the | + | |
- | # path to it here. Normally this means a full path to the executable, otherwise | + | |
- | # you could have left it undefined here and the shown default would be used. | + | |
- | # | + | |
- | # Windows users, remember to use paths with forward-slashes (or escaped | + | |
- | # back-slashes.) Windows users should declare the full path to the openssl | + | |
- | # binary here if it is not in their system PATH. | + | |
- | + | ||
- | #set_var EASYRSA_OPENSSL | + | |
- | # | + | |
- | # This sample is in Windows syntax -- edit it for your path if not using PATH: | + | |
- | #set_var EASYRSA_OPENSSL | + | |
- | + | ||
- | # Edit this variable to point to your soon-to-be-created key directory. | + | |
- | # | + | |
- | # WARNING: init-pki will do a rm -rf on this directory so make sure you define | + | |
- | # it correctly! (Interactive mode will prompt before acting.) | + | |
- | + | ||
- | #set_var EASYRSA_PKI | + | |
- | + | ||
- | # Define X509 DN mode. | + | |
- | # This is used to adjust what elements are included in the Subject field as the DN | + | |
- | # (this is the " | + | |
- | # Note that in cn_only mode the Organizational fields further below aren't used. | + | |
- | # | + | |
- | # Choices are: | + | |
- | # | + | |
- | # | + | |
- | + | ||
- | #set_var EASYRSA_DN | + | |
- | + | ||
- | # Organizational fields (used with ' | + | |
- | # These are the default values for fields which will be placed in the | + | |
- | # certificate. | + | |
- | # you may omit any specific field by typing the " | + | |
- | # email.) | + | |
- | + | ||
- | set_var EASYRSA_REQ_COUNTRY | + | |
- | set_var EASYRSA_REQ_PROVINCE | + | |
- | set_var EASYRSA_REQ_CITY | + | |
- | set_var EASYRSA_REQ_ORG | + | |
- | set_var EASYRSA_REQ_EMAIL | + | |
- | #set_var EASYRSA_REQ_OU | + | |
- | + | ||
- | # Choose a size in bits for your keypairs. The recommended value is 2048. Using | + | |
- | # 2048-bit keys is considered more than sufficient for many years into the | + | |
- | # future. Larger keysizes will slow down TLS negotiation and make key/DH param | + | |
- | # generation take much longer. Values up to 4096 should be accepted by most | + | |
- | # software. | + | |
- | + | ||
- | #set_var EASYRSA_KEY_SIZE | + | |
- | + | ||
- | # In how many days should the root CA key expire? | + | |
- | + | ||
- | #set_var EASYRSA_CA_EXPIRE | + | |
- | + | ||
- | # In how many days should certificates expire? | + | |
- | + | ||
- | #set_var EASYRSA_CERT_EXPIRE | + | |
- | + | ||
- | # How many days until the next CRL publish date? Note that the CRL can still be | + | |
- | # parsed after this timeframe passes. It is only used for an expected next | + | |
- | # publication date. | + | |
- | + | ||
- | #set_var EASYRSA_CRL_DAYS | + | |
- | + | ||
- | # Support deprecated " | + | |
- | # is " | + | |
- | # feature to use with --ns-cert-type, | + | |
- | # should be replaced with the more modern --remote-cert-tls feature. | + | |
- | # not use --ns-cert-type in your configs, it is safe (and recommended) to leave | + | |
- | # this defined to " | + | |
- | # nsCertType=server attribute, and also get any NS_COMMENT defined below in the | + | |
- | # nsComment field. | + | |
- | + | ||
- | #set_var EASYRSA_NS_SUPPORT | + | |
- | + | ||
- | # When NS_SUPPORT is set to " | + | |
- | # Set this blank to omit it. With NS_SUPPORT set to " | + | |
- | + | ||
- | #set_var EASYRSA_NS_COMMENT | + | |
- | + | ||
- | # A temp file used to stage cert extensions during signing. The default should | + | |
- | # be fine for most users; however, some users might want an alternative under a | + | |
- | # RAM-based FS, such as /dev/shm or /tmp on some systems. | + | |
- | + | ||
- | #set_var EASYRSA_TEMP_FILE | + | |
- | + | ||
- | # !! | + | |
- | # NOTE: ADVANCED OPTIONS BELOW THIS POINT | + | |
- | # PLAY WITH THEM AT YOUR OWN RISK | + | |
- | # !! | + | |
- | + | ||
- | # Broken shell command aliases: If you have a largely broken shell that is | + | |
- | # missing any of these POSIX-required commands used by Easy-RSA, you will need | + | |
- | # to define an alias to the proper path for the command. | + | |
- | # some form of a ' | + | |
- | # shell is BROKEN, but you can hack around it here if you really need. These | + | |
- | # shown values are not defaults: it is up to you to know what you're doing if | + | |
- | # you touch these. | + | |
- | # | + | |
- | #alias awk="/ | + | |
- | #alias cat="/ | + | |
- | + | ||
- | # X509 extensions directory: | + | |
- | # If you want to customize the X509 extensions used, set the directory to look | + | |
- | # for extensions here. Each cert type you sign must have a matching filename, | + | |
- | # and an optional file named ' | + | |
- | # when undefined here, default behaviour is to look in $PKI_DIR first, then | + | |
- | # fallback to $EASYRSA for the ' | + | |
- | # detection with an explicit dir here. | + | |
- | # | + | |
- | #set_var EASYRSA_EXT_DIR | + | |
- | + | ||
- | # OpenSSL config file: | + | |
- | # If you need to use a specific openssl config file, you can reference it here. | + | |
- | # Normally this file is auto-detected from a file named openssl-1.0.cnf from the | + | |
- | # PKI_DIR or EASYRSA dir (in that order.) NOTE that this file is Easy-RSA | + | |
- | # specific and you cannot just use a standard config file, so this is an | + | |
- | # advanced feature. | + | |
- | + | ||
- | #set_var EASYRSA_SSL_CONF | + | |
- | + | ||
- | # Defualt CN: | + | |
- | # This is best left alone. Interactively you will set this manually, and BATCH | + | |
- | # callers are expected to set this themselves. | + | |
- | + | ||
- | #set_var EASYRSA_REQ_CN | + | |
- | + | ||
- | # Cryptographic digest to use. | + | |
- | # Do not change this default unless you understand the security implications. | + | |
- | # Valid choices include: md5, sha1, sha256, sha224, sha384, sha512 | + | |
- | + | ||
- | #set_var EASYRSA_DIGEST | + | |
- | + | ||
- | # Batch mode. Leave this disabled (set to 0) unless you intend to call Easy-RSA | + | |
- | # explicitly in batch mode without any user input, confirmation on dangerous | + | |
- | # operations, or most output. | + | |
- | + | ||
- | #set_var EASYRSA_BATCH | + | |
</ | </ | ||
- | Proceed like this: | + | Create the PKI and the CA: |
< | < | ||
- | ./easyrsa init-pki | + | # ./easyrsa init-pki |
+ | # ./easyrsa build-ca | ||
+ | </ | ||
+ | Enter a PEM pass phrase, reverify it and then enter a name for the server. In this article I am using the hostnames for clarity (in this case: server1), but you may choose any name. | ||
- | Note: using Easy-RSA configuration from: ./vars | + | Then generate the request: |
- | + | ||
- | init-pki complete; you may now create a CA or requests. | + | |
- | Your newly created PKI dir is: / | + | |
- | </ | + | |
< | < | ||
- | # ./ | + | # ./easyrsa gen-req server1 |
- | # ./build-ca | + | |
- | Generating a 2048 bit RSA private key | + | |
- | .....................+++ | + | |
- | .......................................................................+++ | + | |
- | writing new private key to ' | + | |
- | ----- | + | |
- | You are about to be asked to enter information that will be incorporated | + | |
- | into your certificate request. | + | |
- | What you are about to enter is what is called a Distinguished Name or a DN. | + | |
- | There are quite a few fields but you can leave some blank | + | |
- | For some fields there will be a default value, | + | |
- | If you enter ' | + | |
- | ----- | + | |
- | Country Name (2 letter code) [MT]: | + | |
- | State or Province Name (full name) [Malta]: | + | |
- | Locality Name (eg, city) [Valletta]: | + | |
- | Organization Name (eg, company) [ABCDEF Co. Ltd.]: | + | |
- | Organizational Unit Name (eg, section) []: | + | |
- | Common Name (eg, your name or your server' | + | |
- | Name [server1]: | + | |
- | Email Address [support@abcdef.com]: | + | |
</ | </ | ||
- | **Hint: The less information you enter, the less likely it will cause you problems later on.** | + | You will be prompted for another PEM pass phrase to reverify it and to confirm that the name of the entity is indeed server1. Now you may proceed to sign this request: |
< | < | ||
- | # ./build-key-server server1 | + | # ./easyrsa sign-req server server1 |
</ | </ | ||
- | **Do not enter a challenge password or company name when prompted.** | + | Confirm the request by entering " |
+ | |||
+ | Now create two additional key files: | ||
< | < | ||
- | Generating a 2048 bit RSA private key | + | # cd / |
- | ........................+++ | + | # openssl dhparam -out dh2048.pem 2048 |
- | ................................................+++ | + | # cd / |
- | writing new private key to ' | + | # / |
- | ----- | + | </code> |
- | You are about to be asked to enter information that will be incorporated | + | |
- | into your certificate request. | + | |
- | What you are about to enter is what is called a Distinguished Name or a DN. | + | |
- | There are quite a few fields but you can leave some blank | + | |
- | For some fields there will be a default value, | + | |
- | If you enter ' | + | |
- | ----- | + | |
- | Country Name (2 letter | + | |
- | State or Province Name (full name) [Malta]: | + | |
- | Locality Name (eg, city) [Valletta]: | + | |
- | Organization Name (eg, company) [ABCDEF Co. Ltd.]: | + | |
- | Organizational Unit Name (eg, section) []: | + | |
- | Common Name (eg, your name or your server' | + | |
- | Name [server1]: | + | |
- | Email Address [support@abcdef.com]: | + | |
- | Please enter the following ' | + | ==== 5.2 Create |
- | to be sent with your certificate request | + | |
- | A challenge password []: | + | |
- | An optional company name []: | + | |
- | Using configuration from / | + | |
- | Check that the request matches the signature | + | |
- | Signature ok | + | |
- | The Subject' | + | |
- | countryName | + | |
- | stateOrProvinceName | + | |
- | localityName | + | |
- | organizationName | + | |
- | commonName | + | |
- | name : | + | |
- | emailAddress | + | |
- | Certificate is to be certified until Jan 18 19:37:43 2023 GMT (3650 days) | + | |
- | Sign the certificate? | + | |
+ | Follow these steps on the Client to create the needed keys and certificates: | ||
- | 1 out of 1 certificate requests certified, commit? [y/n]y | + | You will need the easy-rsa scripts, so you can copy the easy-rsa tarball from the Server to the Client and extract it: |
- | Write out database with 1 new entries | + | |
- | Data Base Updated | + | |
- | </ | + | |
< | < | ||
- | # ./build-dh | + | # cd |
- | This is going to take a long time | + | # tar xvf easy-rsa.tar |
- | ..................+........................................................................................................... | + | |
- | ................................................................. | + | |
</ | </ | ||
+ | |||
+ | Now create the PKI and generate the request: | ||
< | < | ||
- | # ./build-key client1 | + | # cd easy-rsa/ |
+ | # ./easyrsa init-pki | ||
+ | # ./easyrsa gen-req client1 | ||
</ | </ | ||
- | ** Do not enter a challenge password or company name when prompted.** | + | You will be prompted |
- | < | + | Copy pki/reqs/client1.req back to the Server. |
- | Generating a 2048 bit RSA private key | + | |
- | ...............................................................................................+++ | + | |
- | ..+++ | + | |
- | writing new private key to 'client1.key' | + | |
- | ----- | + | |
- | You are about to be asked to enter information that will be incorporated | + | |
- | into your certificate request. | + | |
- | What you are about to enter is what is called a Distinguished Name or a DN. | + | |
- | There are quite a few fields but you can leave some blank | + | |
- | For some fields there will be a default value, | + | |
- | If you enter ' | + | |
- | ----- | + | |
- | Country Name (2 letter code) [MT]: | + | |
- | State or Province Name (full name) [Malta]: | + | |
- | Locality Name (eg, city) [Valletta]: | + | |
- | Organization Name (eg, company) [ABCDEF Co. Ltd.]: | + | |
- | Organizational Unit Name (eg, section) []: | + | |
- | Common Name (eg, your name or your server' | + | |
- | Name [server1]: | + | |
- | Email Address [support@abcdef.com]: | + | |
- | Please enter the following ' | + | === 5.2.1 Sign the Client' |
- | to be sent with your certificate request | + | |
- | A challenge password []: | + | |
- | An optional company name []: | + | |
- | Using configuration from / | + | |
- | Check that the request matches the signature | + | |
- | Signature ok | + | |
- | The Subject' | + | |
- | countryName | + | |
- | stateOrProvinceName | + | |
- | localityName | + | |
- | organizationName | + | |
- | commonName | + | |
- | name : | + | |
- | emailAddress | + | |
- | Certificate is to be certified until Jan 18 19:42:33 2023 GMT (3650 days) | + | |
- | Sign the certificate? | + | |
+ | For the purpose of this article, it is assumed that the Client' | ||
- | 1 out of 1 certificate requests certified, commit? [y/n]y | + | < |
- | Write out database with 1 new entries | + | # cd $HOME/easy-rsa/ |
- | Data Base Updated | + | # ./easyrsa import-req $HOME/ |
+ | # ./easyrsa sign-req client client1 | ||
</ | </ | ||
- | < | + | When prompted enter " |
- | # openvpn --genkey --secret /root/easy-rsa/2.0/keys/ta.key | + | |
- | </ | + | Copy the generated $HOME/easy-rsa/easyrsa3/pki/issued/ |
+ | back to the client. | ||
===== 6. Setting up the Server ===== | ===== 6. Setting up the Server ===== | ||
Line 443: | Line 162: | ||
< | < | ||
- | # cp /root/easy-rsa/2.0/keys/{ca.crt,server1.crt, | + | # cp $HOME/easy-rsa/easyrsa3/pki/ |
+ | > / | ||
+ | # cp $HOME/ | ||
> / | > / | ||
- | # cp /root/easy-rsa/2.0/keys/{server1.key, | + | # cp $HOME/easy-rsa/easyrsa3/pki/private/ |
> / | > / | ||
</ | </ | ||
- | Restrict | + | Copy the sample server.conf from the OpenVPN source onto the OpenVPN' |
< | < | ||
- | # chmod 700 /etc/openvpn/keys | + | # cd /tmp/ |
+ | # wget -c \ | ||
+ | > ftp:// | ||
+ | # cd /usr/src/ | ||
+ | # tar xvf / | ||
</ | </ | ||
- | On the Server machine copy the sample | + | Copy the file server.conf |
< | < | ||
- | # cp /usr/doc/openvpn-2.2.2/ | + | # cp openvpn-*/sample/ |
> / | > / | ||
</ | </ | ||
Line 477: | Line 202: | ||
;user nobody | ;user nobody | ||
;group nobody | ;group nobody | ||
+ | |||
+ | ; | ||
</ | </ | ||
- | To | + | To: |
< | < | ||
Line 492: | Line 219: | ||
user nobody | user nobody | ||
group nobody | group nobody | ||
+ | |||
+ | log-append | ||
</ | </ | ||
- | **Note** that comments in server.conf | + | Finally add the following to / |
- | Copy the rc.openvpn-server | + | < |
+ | # 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. | ||
+ | # Generally speaking, servers should run OpenVPN as a daemon | ||
+ | ;daemon | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | # cat / | ||
+ | </ | ||
+ | |||
+ | < | ||
+ | |||
+ | Copy the rc.openvpn listed hereunder and place under /etc/rc.d/ | ||
< | < | ||
# | # | ||
# | # | ||
- | # / | + | # / |
# | # | ||
- | # Start/ | + | # Start/ |
- | # | + | # |
- | # To make OpenVPN start automatically at boot, make this | + | |
- | # file executable: | + | |
- | # | + | |
ovpn_start() { | ovpn_start() { | ||
if [ -x / | if [ -x / | ||
echo " | echo " | ||
- | / | + | / |
fi | fi | ||
} | } | ||
Line 544: | Line 288: | ||
< | < | ||
- | # chmod 755 / | + | # chmod 755 / |
</ | </ | ||
===== 7. Port Forwarding ===== | ===== 7. Port Forwarding ===== | ||
- | You will need to forward traffic from the port you have chosen for Openvpn | + | You will need to forward traffic from the port you have chosen for OpenVPN |
- | In case if you have misplaced such documentation, | + | In case if you have misplaced such documentation, |
===== 8. Setting up the Client ===== | ===== 8. Setting up the Client ===== | ||
- | On the client | + | On the Client |
+ | |||
+ | Download the OpenVPN source tarball and extracted it as explained in Chapter 6, then proceed to copy the included configuration file for clients: | ||
< | < | ||
- | # cp /usr/doc/openvpn-2.2.2/ | + | # cp /usr/src/openvpn-*/sample/ |
> / | > / | ||
</ | </ | ||
Line 592: | Line 338: | ||
</ | </ | ||
- | **Note** that comments in client.conf | + | Finally add the following to / |
- | + | ||
- | You will need the following files that were generated by the easy-rsa scripts: | + | |
< | < | ||
- | ca.crt | + | # Select a cryptographic cipher. |
- | client1.crt | + | # This config item must be copied to |
- | client1.key | + | # the server config file as well. |
- | ta.key | + | cipher AES-256-CBC |
</ | </ | ||
- | Place these files as indicated | + | < |
- | Copy the following rc.openvpn-client listed hereunder and place under /etc/rc.d/ | + | You will need this file that was generated by the Client' |
< | < | ||
- | #!/bin/sh | + | cp $HOME/easy-rsa/easyrsa3/pki/private/client1.key \ |
- | # | + | > /etc/openvpn/keys/ |
- | # /etc/rc.d/rc.openvpn-client | + | </ |
- | # | + | |
- | # Start/stop/restart the openvpn | + | |
- | # | + | |
- | ovpn_start() { | + | and the following from the Server' |
- | if [ -x / | + | |
- | echo " | + | |
- | / | + | |
- | fi | + | |
- | } | + | |
- | ovpn_stop() { | + | < |
- | | + | $HOME/ |
- | } | + | $HOME/ |
- | + | ||
- | ovpn_restart() { | + | |
- | ovpn_stop | + | |
- | sleep 2 | + | |
- | ovpn_start | + | |
- | } | + | |
- | + | ||
- | case "$1" in | + | |
- | ' | + | |
- | ovpn_start | + | |
- | ;; | + | |
- | ' | + | |
- | ovpn_stop | + | |
- | ;; | + | |
- | ' | + | |
- | ovpn_restart | + | |
- | ;; | + | |
- | *) | + | |
- | echo " | + | |
- | esac | + | |
</ | </ | ||
- | Then give it executable permissions: | + | and this file as well: |
< | < | ||
- | # chmod +x /etc/rc.d/rc.openvpn-client | + | /etc/openvpn/keys/ta.key |
</ | </ | ||
+ | |||
+ | Place these files as indicated in client.conf. So ca.crt and client1.crt go under / | ||
===== 9. Testing the VPN ===== | ===== 9. Testing the VPN ===== | ||
Line 658: | Line 376: | ||
< | < | ||
- | # / | + | # / |
</ | </ | ||
+ | |||
+ | Enter the Server PEM pass phrase when prompted. | ||
On the Client: | On the Client: | ||
< | < | ||
- | # /etc/rc.d/rc.openvpn-client | + | # /usr/sbin/ |
</ | </ | ||
+ | |||
+ | Enter the Client PEM pass phrase when prompted. To stop OpenVPN on the Client just hit CTRL+C | ||
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 709: | Line 431: | ||
</ | </ | ||
- | To start the openvpn | + | ===== 10. Storing the PEM pass phrase in a secure file and Automatic start of service after booting ===== |
+ | |||
+ | To start the OpenVPN | ||
< | < | ||
- | # Start the OpenVPN Server | + | # chmod 600 / |
- | if [ -x / | + | </ |
- | / | + | |
+ | On the Server, edit / | ||
+ | |||
+ | < | ||
+ | askpass / | ||
+ | auth-nocache | ||
+ | </ | ||
+ | |||
+ | Also, uncomment the ' | ||
+ | |||
+ | This may be repeated also on the Client, just edit / | ||
+ | |||
+ | To start the OpenVPN | ||
+ | |||
+ | < | ||
+ | # Start the OpenVPN Service | ||
+ | if [ -x / | ||
+ | / | ||
fi | fi | ||
</ | </ | ||
- | ===== 10. IP Routing ===== | + | An alternate method (albeit less secure) is to remove the passphrase from server1.key file altogether. |
+ | |||
+ | < | ||
+ | # cd / | ||
+ | # openssl rsa -in server1.key -out tmp.key | ||
+ | # mv tmp.key server1.key | ||
+ | # chmod 600 server1.key | ||
+ | </ | ||
+ | |||
+ | |||
+ | ===== 11. IP Routing ===== | ||
Up to now we have created a tunnel device on both the Server and the Client called tun0 which is visible only to these two machines. However more work is needed to route the Client' | Up to now we have created a tunnel device on both the Server and the Client called tun0 which is visible only to these two machines. However more work is needed to route the Client' | ||
- | ==== 10.1 Server Configuration ==== | + | ==== 11.1 Server Configuration ==== |
Enable IP forwarding: | Enable IP forwarding: | ||
Line 752: | Line 503: | ||
push "route 192.168.200.0 255.255.255.0" | push "route 192.168.200.0 255.255.255.0" | ||
- | client-config-dir ccd | + | client-config-dir |
route 192.168.1.0 255.255.255.0 | route 192.168.1.0 255.255.255.0 | ||
Line 762: | Line 513: | ||
Naturally replace 192.168.200.0 255.255.255.0 with the Server' | Naturally replace 192.168.200.0 255.255.255.0 with the Server' | ||
+ | 208.67.222.222 and 208.67.220.220 are the OpenDNS IP addresses. | ||
- | 208.67.222.222 and 208.67.220.220 are the OpenDNS IP addresses. | + | <note warning>Up to now the DNS push configuration has not been successful.</ |
+ | |||
+ | You can either use the original Client DNS servers or else you may rewrite | ||
+ | |||
+ | < | ||
+ | # OpenDNS Servers | ||
+ | nameserver 208.67.222.222 | ||
+ | nameserver 208.67.220.220 | ||
+ | </ | ||
+ | |||
+ | According to your routing table however, | ||
+ | |||
+ | Some users have reported that their Client' | ||
Next you will have to configure some iptables NAT forwarding on the Server (only). You can do this by first flushing the iptables: | Next you will have to configure some iptables NAT forwarding on the Server (only). You can do this by first flushing the iptables: | ||
Line 791: | Line 555: | ||
< | < | ||
- | #!/bin/sh | + | #!/bin/bash |
- | # Start/ | + | # Start/ |
- | # A VPN server iptable filter rules | + | |
- | + | IPT=/ | |
- | IPT=/ | + | |
+ | firewall_start() { | ||
+ | |||
+ | # flush the iptables | ||
+ | echo -e " | ||
+ | $IPT -F | ||
+ | |||
+ | # policies | ||
+ | $IPT -P OUTPUT DROP | ||
+ | $IPT -P INPUT DROP | ||
+ | $IPT -P FORWARD DROP | ||
- | firewall_start() { | + | $IPT -N SERVICES # services is a custom chain |
- | # Flush the iptables | + | # allowed output |
- | $IPT -F | + | $IPT -A OUTPUT -o lo -j ACCEPT |
+ | $IPT -A OUTPUT -o eth0 -j ACCEPT | ||
+ | $IPT -A OUTPUT -o tun0 -j ACCEPT | ||
- | # Policies | + | # allowed inputs |
- | $IPT -P OUTPUT | + | |
- | $IPT -P INPUT DROP | + | $IPT -A INPUT -m conntrack --ctstate ESTABLISHED, |
- | $IPT -P FORWARD DROP | + | $IPT -A INPUT -j SERVICES # append the services |
- | $IPT -N SERVICES # Services is a custom | + | |
- | # Allowed inputs | + | # allowed forwarding for OpenVPN |
- | | + | $IPT -A FORWARD |
- | $IPT -A INPUT -m conntrack | + | $IPT -A FORWARD -s 10.8.0.0/24 -o eth0 -j ACCEPT |
- | $IPT -A INPUT -j SERVICES # Append the services chain to the input | + | |
- | # Allowed forwards | + | # masquerade the OpenVPN network |
- | $IPT -A FORWARD -i eth0 -o tun0 -m state --state ESTABLISHED, | + | $IPT -t nat -A POSTROUTING |
- | $IPT -A FORWARD | + | |
- | # Masquerade the openvpn network | + | # allow sshd on the default tcp port 22 |
- | $IPT -t nat -A POSTROUTING -s 10.8.0.0/24 ! -d 10.8.0.0/24 -o eth0 -j MASQUERADE | + | |
- | + | ||
- | # Allow services | + | |
- | # Allow vpn on the default udp port 1194 | + | |
- | $IPT -A SERVICES -p udp --dport 1194 -j ACCEPT | + | |
- | # Allow sshd on the default tcp port 22 | + | |
- | $IPT -A SERVICES -p tcp --dport 22 -j ACCEPT | + | |
+ | # allow OpenVPN for the default udp port 1194 | ||
+ | $IPT -A SERVICES -p udp --dport 1194 -j ACCEPT | ||
+ | | ||
+ | echo " | ||
} | } | ||
firewall_stop() { | firewall_stop() { | ||
+ | echo -e " | ||
- | # Polcies | + | # polcies |
+ | $IPT -P OUTPUT ACCEPT | ||
$IPT -P INPUT ACCEPT | $IPT -P INPUT ACCEPT | ||
+ | $IPT -P FORWARD ACCEPT | ||
- | # Flush the iptables | + | # flush the iptables |
$IPT -F | $IPT -F | ||
- | # Delete | + | # delete |
- | $IPT -X SERVICES | + | $IPT -X SERVICES |
- | } | + | echo " |
+ | } | ||
+ | |||
+ | firewall_status() { | ||
+ | $IPT -vL | ||
+ | } | ||
case " | case " | ||
Line 851: | Line 630: | ||
firewall_start | firewall_start | ||
;; | ;; | ||
+ | ' | ||
+ | firewall_status | ||
+ | ;; | ||
*) | *) | ||
- | echo "Usage $0 start|stop|restart" | + | echo "Usage $0 start|stop|restart|status" |
esac | esac | ||
</ | </ | ||
Line 868: | Line 650: | ||
</ | </ | ||
- | Now you will you need to do is to restart | + | Restart |
- | ===== 11. Firewalls ===== | + | < |
+ | # /etc/rc.d/ | ||
+ | </ | ||
- | In the previous chapter we referred to a firewall you may include to protect your Openvpn | + | and reconnect from the Client: |
+ | |||
+ | < | ||
+ | # / | ||
+ | </ | ||
+ | |||
+ | ===== 12. Firewalls ===== | ||
+ | |||
+ | In the previous chapter we referred to a firewall you may include to protect your OpenVPN | ||
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 / | 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 / | ||
Line 920: | Line 712: | ||
You also have to modify your Router' | You also have to modify your Router' | ||
- | ===== 12. References | + | ===== 13. Sources |
(1) http:// | (1) http:// | ||
Line 930: | Line 722: | ||
(4) http:// | (4) http:// | ||
+ | (5) http:// | ||
+ | |||
+ | * Written for Slackware 14.2 in April 2018 | ||
* Originally written by [[wiki: | * Originally written by [[wiki: | ||
<!-- Please do not modify anything below, except adding new tags.--> | <!-- Please do not modify anything below, except adding new tags.--> | ||
{{tag> | {{tag> | ||