[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 revisionNext revisionBoth sides next revision | ||
howtos:network_services:openvpn [2013/05/19 18:30 (UTC)] – chrisabela | howtos:network_services:openvpn [2018/04/06 21:19 (UTC)] – Updated for Slackware 14.2 chrisabela | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
====== 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 11: | Line 12: | ||
===== 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 26: | ||
< | < | ||
# 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 40: | ||
< | < | ||
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 49: | ||
< | < | ||
hostname: client1 | hostname: client1 | ||
- | IP: 192.168.1.234/ | + | IP: 192.168.1.101/ |
Network Interface: wlan0 | Network Interface: wlan0 | ||
</ | </ | ||
Line 55: | 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. | + | 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 67: | ||
===== 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 | + | |
- | + | ||
- | Copy the whole easy-rsa | + | |
< | < | ||
- | # cp -r /usr/doc/ | + | # cd |
- | # cd /root/easy-rsa/2.0/ | + | # git clone http://github.com/OpenVPN/easy-rsa |
</ | </ | ||
- | 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 | + | # cd easy-rsa/easyrsa3 |
- | + | ||
- | # NOTE: If you installed from an RPM, | + | |
- | # don't edit this file in place in | + | |
- | # /usr/ | + | |
- | # instead, you should copy the whole | + | |
- | # easy-rsa directory to another location | + | |
- | # (such as / | + | |
- | # edits will not be wiped out by a future | + | |
- | # OpenVPN package upgrade. | + | |
- | + | ||
- | # This variable should point to | + | |
- | # the top level of the easy-rsa | + | |
- | # tree. | + | |
- | export EASY_RSA=" | + | |
- | + | ||
- | # | + | |
- | # This variable should point to | + | |
- | # the requested executables | + | |
- | # | + | |
- | export OPENSSL=" | + | |
- | export PKCS11TOOL=" | + | |
- | export GREP=" | + | |
- | + | ||
- | + | ||
- | # This variable should point to | + | |
- | # the openssl.cnf file included | + | |
- | # with easy-rsa. | + | |
- | export KEY_CONFIG=`$EASY_RSA/ | + | |
- | + | ||
- | # Edit this variable to point to | + | |
- | # your soon-to-be-created key | + | |
- | # directory. | + | |
- | # | + | |
- | # WARNING: clean-all will do | + | |
- | # a rm -rf on this directory | + | |
- | # so make sure you define | + | |
- | # it correctly! | + | |
- | export KEY_DIR=" | + | |
- | + | ||
- | # Issue rm -rf warning | + | |
- | echo NOTE: If you run ./ | + | |
- | + | ||
- | # PKCS11 fixes | + | |
- | export PKCS11_MODULE_PATH=" | + | |
- | export PKCS11_PIN=" | + | |
- | + | ||
- | # Increase this to 2048 if you | + | |
- | # are paranoid. | + | |
- | # down TLS negotiation performance | + | |
- | # as well as the one-time DH parms | + | |
- | # generation process. | + | |
- | export KEY_SIZE=2048 | + | |
- | + | ||
- | # In how many days should the root CA key expire? | + | |
- | export CA_EXPIRE=3650 | + | |
- | + | ||
- | # In how many days should certificates expire? | + | |
- | export KEY_EXPIRE=3650 | + | |
- | + | ||
- | # These are the default values for fields | + | |
- | # which will be placed in the certificate. | + | |
- | # Don't leave any of these fields blank. | + | |
- | export KEY_COUNTRY=" | + | |
- | export KEY_PROVINCE=" | + | |
- | export KEY_CITY=" | + | |
- | export KEY_ORG=" | + | |
- | #export KEY_EMAIL=" | + | |
- | export KEY_EMAIL=support@abcdef.com | + | |
- | export KEY_CN=server1 | + | |
- | export KEY_NAME=server1 | + | |
- | export KEY_OU="" | + | |
- | export PKCS11_MODULE_PATH=changeme | + | |
- | export PKCS11_PIN=1234 | + | |
</ | </ | ||
- | Source | + | Create |
< | < | ||
- | # source | + | # ./easyrsa init-pki |
- | NOTE: If you run ./clean-all, I will be doing a rm -rf on / | + | # ./easyrsa build-ca |
</ | </ | ||
- | Proceed like this: | + | 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. |
+ | |||
+ | Then generate the request: | ||
< | < | ||
- | # ./clean-all | + | # ./easyrsa gen-req server1 |
- | # ./ | + | |
- | 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 | |
- | 1 out of 1 certificate requests certified, commit? [y/n]y | + | |
- | Write out database with 1 new entries | + | |
- | Data Base Updated | + | |
- | </code> | + | |
< | < | ||
- | # openvpn --genkey --secret /root/easy-rsa/2.0/keys/ta.key | + | # cd $HOME/easy-rsa/easyrsa3 |
+ | # ./easyrsa import-req $HOME/openvpn/ | ||
+ | # ./easyrsa sign-req client client1 | ||
</ | </ | ||
+ | |||
+ | When prompted enter " | ||
+ | |||
+ | Copy the generated $HOME/ | ||
+ | back to the client. | ||
===== 6. Setting up the Server ===== | ===== 6. Setting up the Server ===== | ||
Line 326: | Line 163: | ||
< | < | ||
- | # 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 360: | Line 203: | ||
;user nobody | ;user nobody | ||
;group nobody | ;group nobody | ||
+ | |||
+ | ; | ||
</ | </ | ||
- | To | + | To: |
< | < | ||
Line 375: | Line 220: | ||
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 427: | Line 289: | ||
< | < | ||
- | # 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 475: | Line 339: | ||
</ | </ | ||
- | **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 541: | Line 377: | ||
< | < | ||
- | # / | + | # / |
</ | </ | ||
+ | |||
+ | 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 592: | Line 432: | ||
</ | </ | ||
- | 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 | ||
+ | |||
+ | < | ||
+ | # chmod 600 / | ||
+ | </ | ||
+ | |||
+ | On the Server, edit / | ||
< | < | ||
- | if [ -x / | + | askpass / |
- | / | + | auth-nocache |
+ | </ | ||
+ | |||
+ | Also, uncomment the ' | ||
+ | |||
+ | This may be repeated also on the Client, just edit / | ||
+ | |||
+ | To start the OpenVPN service automatically on boot-up from the Server, include these lines in / | ||
+ | |||
+ | < | ||
+ | # 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 627: | Line 497: | ||
</ | </ | ||
- | Replace 192.168.1.0 255.255.255.0 by the Network Route of you Client. | + | Replace 192.168.1.0 255.255.255.0 by the Network Route of your Client. |
Similarly edit / | Similarly edit / | ||
Line 634: | Line 504: | ||
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 644: | Line 514: | ||
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. | ||
+ | |||
+ | <note warning> | ||
+ | |||
+ | 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, it is still worth trying to use the DNS servers listed by the Client, I find that they are generally still available, so you would not need to do anything. However do be aware of possible DNS leaks if you are concerned about your privacy. | ||
- | 208.67.222.222 and 208.67.220.220 are the OpenDNS IP addresses. Up to now the DNS push configuration has not been successful. You can either use the original | + | 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 673: | Line 556: | ||
< | < | ||
- | #!/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 | |
- | # policies | + | $IPT -A OUTPUT |
- | $IPT -P OUTPUT ACCEPT | + | |
- | $IPT -P INPUT DROP | + | |
- | $IPT -P FORWARD DROP | + | |
- | $IPT -N SERVICES # services is a custom chain | + | |
# allowed inputs | # allowed inputs | ||
- | #$IPT -A INPUT -i lo -j ACCEPT # Uncomment | + | #$IPT -A INPUT -i lo -j ACCEPT # uncomment |
- | $IPT -A INPUT -j SERVICES # Append | + | $IPT -A INPUT -m conntrack --ctstate ESTABLISHED, |
+ | $IPT -A INPUT -j SERVICES # append | ||
- | # allowed | + | # allowed |
- | $IPT -A FORWARD -i eth0 -o tun0 -m state --state ESTABLISHED, | + | $IPT -A FORWARD -i eth0 -o tun0 -m state --state ESTABLISHED, |
- | $IPT -A FORWARD -s 10.8.0.0/24 -o eth0 -j ACCEPT | + | $IPT -A FORWARD -s 10.8.0.0/24 -o eth0 -j ACCEPT |
- | # masquerade the openvpn | + | # masquerade the OpenVPN |
- | $IPT -t nat -A POSTROUTING -s 10.8.0.0/24 ! -d 10.8.0.0/24 -o eth0 -j MASQUERADE | + | $IPT -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE |
- | | + | # allow sshd on the default tcp port 22 |
- | $IPT -A INPUT -m state --state ESTABLISHED, | + | |
- | + | ||
- | # allow services | + | |
- | + | ||
- | # allow vpn on the default udp port 1194 | + | |
- | $IPT -A SERVICES -p udp --dport 1194 -j ACCEPT | + | |
- | + | ||
- | | + | |
- | $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 (permissive) | + | # polcies (permissive) |
+ | $IPT -P OUTPUT ACCEPT | ||
$IPT -P INPUT ACCEPT | $IPT -P INPUT ACCEPT | ||
+ | $IPT -P FORWARD ACCEPT | ||
# flush the iptables | # flush the iptables | ||
Line 723: | Line 612: | ||
# delete the services custom chain | # delete the services custom chain | ||
- | $IPT -X SERVICES | + | $IPT -X SERVICES |
- | } | + | echo " |
+ | } | ||
+ | |||
+ | firewall_status() { | ||
+ | $IPT -vL | ||
+ | } | ||
case " | case " | ||
Line 737: | Line 631: | ||
firewall_start | firewall_start | ||
;; | ;; | ||
+ | ' | ||
+ | firewall_status | ||
+ | ;; | ||
*) | *) | ||
- | echo "Usage $0 start|stop|restart" | + | echo "Usage $0 start|stop|restart|status" |
esac | esac | ||
</ | </ | ||
Line 751: | Line 648: | ||
< | < | ||
- | # / | + | # / |
</ | </ | ||
- | ===== 11. Firewalls ===== | + | Restart the OpenVPN service on the Server: |
- | 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 804: | Line 713: | ||
You also have to modify your Router' | You also have to modify your Router' | ||
- | ===== 12. References | + | ===== 13. Sources |
(1) http:// | (1) http:// | ||
Line 814: | Line 723: | ||
(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> | ||