[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/12/27 19:41 (UTC)] – chrisabela | playground:openvpn_-_how_to_set_up_a_slackware_server_and_a_slackware_client [2018/04/06 21:16 (UTC)] – chrisabela | ||
---|---|---|---|
Line 15: | Line 15: | ||
The emphasis is to provide a reliable method that can be easily followed to set-up OpenVPN on Slackware Servers and Clients. Nevertheless the process is still not free from pitfalls and require some attention and determination. | The emphasis is to provide a reliable method that can be easily followed to set-up OpenVPN on Slackware Servers and Clients. Nevertheless the process is still not free from pitfalls and require some attention and determination. | ||
- | This article comprises of a selection of other similar tutorials found on Internet particularly (2) and (3) and the documents contained in the downloaded source files. However these are reformatted to satisfy the objective. | + | This article comprises of a selection of other similar tutorials found on the Internet particularly (2) and (3) and the documents contained in the downloaded source files. However these are reformatted to satisfy the objective. |
===== 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" |
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 33: | Line 33: | ||
==== 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. | + | 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. |
==== 4.2. Server details ==== | ==== 4.2. Server details ==== | ||
Line 54: | 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. 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. |
==== 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 70: | Line 70: | ||
< | < | ||
# cd | # cd | ||
- | # git clone git:// | + | # git clone http:// |
</ | </ | ||
Line 108: | Line 108: | ||
</ | </ | ||
- | Confirm the request by entering | + | Confirm the request by entering |
Now create two additional key files: | Now create two additional key files: | ||
Line 123: | Line 123: | ||
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: |
< | < | ||
Line 138: | Line 138: | ||
</ | </ | ||
- | 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. |
Copy pki/ | Copy pki/ | ||
Line 144: | Line 144: | ||
=== 5.2.1 Sign the Client' | === 5.2.1 Sign the Client' | ||
- | For the purpose of this article, it is assumed that the Client' | + | For the purpose of this article, it is assumed that the Client' |
< | < | ||
- | # cd /root/ | + | # cd $HOME/ |
- | # ./easyrsa import-req | + | # ./easyrsa import-req |
# ./easyrsa sign-req client client1 | # ./easyrsa sign-req client client1 | ||
</ | </ | ||
- | When prompted enter “yes” and the server1 CA PEM pass phrase. | + | When prompted enter "yes" |
- | Copy the generated | + | Copy the generated |
back to the client. | back to the client. | ||
Line 162: | Line 162: | ||
< | < | ||
- | # cp /root/ | + | # cp $HOME/ |
> / | > / | ||
- | # cp /root/ | + | # cp $HOME/ |
> / | > / | ||
- | # cp /root/ | + | # cp $HOME/ |
> / | > / | ||
</ | </ | ||
- | Copy the sample server.conf from the openvpn | + | Copy the sample server.conf from the OpenVPN |
< | < | ||
Line 180: | Line 180: | ||
</ | </ | ||
- | Copy the file server.conf contained in the source to the openvpn | + | Copy the file server.conf contained in the source to the OpenVPN |
< | < | ||
- | # cp openvpn-2.3.2/ | + | # cp openvpn-*/ |
> / | > / | ||
</ | </ | ||
Line 226: | Line 226: | ||
< | < | ||
+ | # 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 |
</ | </ | ||
- | My full server.conf | + | < |
< | < | ||
- | ################################################# | + | # cat / |
- | # Sample OpenVPN 2.0 config file for # | + | </code> |
- | # multi-client server. | + | |
- | # # | + | |
- | # This file is for the server side # | + | |
- | # of a many-clients | + | |
- | # 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. | + | |
- | # Windows to quote pathnames and use # | + | |
- | # double backslashes, | + | |
- | # " | + | |
- | # # | + | |
- | # Comments are preceded with '#' | + | |
- | ################################################# | + | |
- | # Which local IP address should OpenVPN | + | <note>Note that comments |
- | # 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 " | + | |
- | # 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). | + | |
- | # and the server must have their own cert and | + | |
- | # key file. The server and all clients will | + | |
- | # use the same ca file. | + | |
- | # | + | |
- | # See the " | + | |
- | # 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 " | + | |
- | ca / | + | |
- | cert / | + | |
- | key / | + | |
- | + | ||
- | # Diffie hellman parameters. | + | |
- | # Generate your own with: | + | |
- | # | + | |
- | # Substitute 2048 for 1024 if you are using | + | |
- | # 2048 bit keys. | + | |
- | dh / | + | |
- | + | ||
- | # 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 | + | |
- | # 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. | + | |
- | # IP/netmask on the bridge interface, here we | + | |
- | # assume 10.8.0.4/ | + | |
- | # must set aside an IP range in this subnet | + | |
- | # (start=10.8.0.50 end=10.8.0.100) to allocate | + | |
- | # to connecting clients. | + | |
- | # 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. | + | |
- | # 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. | + | |
- | ; | + | |
- | + | ||
- | # Push routes to the client to allow it | + | |
- | # to reach other private subnets behind | + | |
- | # the server. | + | |
- | # private subnets will also need | + | |
- | # to know to route the OpenVPN client | + | |
- | # address pool (10.8.0.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 " | + | |
- | # configuration files (see man page for more info). | + | |
- | + | ||
- | # EXAMPLE: Suppose the client | + | |
- | # having the certificate common name " | + | |
- | # also has a small subnet behind his connecting | + | |
- | # machine, such as 192.168.40.128/ | + | |
- | # First, uncomment out these lines: | + | |
- | ; | + | |
- | ;route 192.168.40.128 255.255.255.248 | + | |
- | # Then create a file ccd/ | + | |
- | # | + | |
- | # This will allow Thelonious' | + | |
- | # access the VPN. This example will only work | + | |
- | # if you are routing, not bridging, i.e. you are | + | |
- | # using "dev tun" and " | + | |
- | + | ||
- | # EXAMPLE: Suppose you want to give | + | |
- | # Thelonious a fixed VPN IP address of 10.9.0.1. | + | |
- | # First uncomment out these lines: | + | |
- | ; | + | |
- | ;route 10.9.0.0 255.255.255.252 | + | |
- | # Then add this line to ccd/ | + | |
- | # | + | |
- | + | ||
- | # Suppose that you want to enable different | + | |
- | # firewall access policies for different groups | + | |
- | # of clients. | + | |
- | # (1) Run multiple OpenVPN daemons, one for each | + | |
- | # | + | |
- | # for each group/ | + | |
- | # (2) (Advanced) Create a script to dynamically | + | |
- | # | + | |
- | # from different clients. | + | |
- | # page for more info on 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 | + | |
- | # or bridge the TUN/TAP interface to the internet | + | |
- | # in order for this to work properly). | + | |
- | ;push " | + | |
- | + | ||
- | # Certain Windows-specific network settings | + | |
- | # can be pushed to clients, such as DNS | + | |
- | # or WINS server addresses. | + | |
- | # http:// | + | |
- | # The addresses below refer to the public | + | |
- | # DNS servers provided by opendns.com. | + | |
- | ;push " | + | |
- | ;push " | + | |
- | + | ||
- | # Uncomment this directive to allow different | + | |
- | # clients to be able to " | + | |
- | # 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' | + | |
- | ; | + | |
- | + | ||
- | # Uncomment this directive if multiple clients | + | |
- | # might connect | + | |
- | # files or common names. | + | |
- | # only for testing purposes. | + | |
- | # each client should have its own certificate/ | + | |
- | # pair. | + | |
- | # | + | |
- | # IF YOU HAVE NOT GENERATED INDIVIDUAL | + | |
- | # CERTIFICATE/ | + | |
- | # EACH HAVING ITS OWN UNIQUE " | + | |
- | # 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 | + | |
- | # | + | |
- | # | + | |
- | # The server and each client must have | + | |
- | # a copy of this key. | + | |
- | # The second parameter should be ' | + | |
- | # on the server and ' | + | |
- | tls-auth / | + | |
- | + | ||
- | # Select a cryptographic cipher. | + | |
- | # This config item must be copied to | + | |
- | # the client config file as well. | + | |
- | ;cipher BF-CBC | + | |
- | ;cipher AES-128-CBC | + | |
- | ;cipher DES-EDE3-CBC | + | |
- | + | ||
- | # 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. | + | |
- | ; | + | |
- | + | ||
- | # It's a good idea to reduce the OpenVPN | + | |
- | # daemon' | + | |
- | # | + | |
- | # 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, | + | |
- | # 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 " | + | |
- | # Use log or log-append to override this default. | + | |
- | # " | + | |
- | # while " | + | |
- | # or the other (but not both). | + | |
- | ;log | + | |
- | log-append | + | |
- | + | ||
- | # Set the appropriate level of log | + | |
- | # file verbosity. | + | |
- | # | + | |
- | # 0 is silent, except | + | |
- | # 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> | + | |
- | < | + | Copy the rc.openvpn listed hereunder and place under /etc/rc.d/ |
- | Copy the rc.openvpn listed hereunder and place under /etc/rc.d/</ | + | |
< | < | ||
Line 547: | Line 250: | ||
# / | # / | ||
# | # | ||
- | # Start/ | + | # Start/ |
# | # | ||
Line 586: | Line 289: | ||
< | < | ||
# chmod 755 / | # chmod 755 / | ||
- | </ | ||
- | |||
- | Eventually when you start openvpn on the server, you may read / | ||
- | |||
- | < | ||
- | # cat / | ||
</ | </ | ||
===== 7. Port Forwarding ===== | ===== 7. Port Forwarding ===== | ||
- | YYou 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, | ||
Line 604: | Line 301: | ||
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 | + | Download the OpenVPN |
< | < | ||
Line 641: | Line 338: | ||
</ | </ | ||
- | < | + | Finally add the following to / |
- | + | ||
- | You will need the this files that were generated by the Client' | + | |
< | < | ||
- | / | + | # Select a cryptographic cipher. |
+ | # This config item must be copied to | ||
+ | # the server config file as well. | ||
+ | cipher AES-256-CBC | ||
</ | </ | ||
- | and the following from the Server's easy-rsa scripts: | + | < |
+ | |||
+ | You will need this file that was generated by the Client's easy-rsa scripts: | ||
< | < | ||
- | ca.crt | + | cp $HOME/ |
- | ta.key | + | > / |
</ | </ | ||
- | You will also need client1.crt generated by the Server | + | 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 / | + | |
- | + | ||
- | Also in client.conf, | + | |
< | < | ||
- | ns-cert-type server | + | $HOME/easy-rsa/ |
+ | $HOME/easy-rsa/ | ||
</ | </ | ||
- | and insert the line: | + | and this file as well: |
< | < | ||
- | remote-cert-tls server | + | / |
</ | </ | ||
- | My full client.conf is the following: | + | Place these files as indicated |
- | + | ||
- | < | + | |
- | ############################################## | + | |
- | # Sample client-side OpenVPN 2.0 config file # | + | |
- | # for connecting to multi-client server. | + | |
- | # # | + | |
- | # This configuration can be used by multiple # | + | |
- | # clients, however each client should have # | + | |
- | # its own cert and key files. # | + | |
- | # # | + | |
- | # On Windows, you might want to rename this # | + | |
- | # file so it has a .ovpn extension | + | |
- | ############################################## | + | |
- | + | ||
- | # Specify that we are a client and that we | + | |
- | # will be pulling certain config file directives | + | |
- | # from the server. | + | |
- | client | + | |
- | + | ||
- | # Use the same setting | + | |
- | # the server. | + | |
- | # 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, | + | |
- | # you may need to disable the firewall | + | |
- | # for the TAP adapter. | + | |
- | ;dev-node MyTap | + | |
- | + | ||
- | # Are we connecting to a TCP or | + | |
- | # UDP server? | + | |
- | # on the server. | + | |
- | ;proto tcp | + | |
- | proto udp | + | |
- | + | ||
- | # The hostname/IP and port of the server. | + | |
- | # You can have multiple remote entries | + | |
- | # to load balance between the servers. | + | |
- | remote servervpn.no-ip.org 1194 | + | |
- | ;remote my-server-2 1194 | + | |
- | + | ||
- | # Choose a random host from the remote | + | |
- | # list for load-balancing. | + | |
- | # try hosts in the order specified. | + | |
- | ; | + | |
- | + | ||
- | # Keep trying indefinitely to resolve the | + | |
- | # host name of the OpenVPN server. | + | |
- | # on machines which are not permanently connected | + | |
- | # to the internet such as laptops. | + | |
- | resolv-retry infinite | + | |
- | + | ||
- | # Most clients don't need to bind to | + | |
- | # a specific local port number. | + | |
- | nobind | + | |
- | + | ||
- | # Downgrade privileges after initialization (non-Windows only) | + | |
- | user nobody | + | |
- | group nobody | + | |
- | + | ||
- | # Try to preserve some state across restarts. | + | |
- | persist-key | + | |
- | persist-tun | + | |
- | + | ||
- | # If you are connecting through an | + | |
- | # HTTP proxy to reach the actual OpenVPN | + | |
- | # server, put the proxy server/IP and | + | |
- | # port number here. See the man page | + | |
- | # if your proxy server requires | + | |
- | # authentication. | + | |
- | ; | + | |
- | ;http-proxy [proxy server] [proxy port #] | + | |
- | + | ||
- | # Wireless networks often produce a lot | + | |
- | # of duplicate packets. | + | |
- | # to silence duplicate packet warnings. | + | |
- | ; | + | |
- | + | ||
- | # SSL/TLS parms. | + | |
- | # See the server config file for more | + | |
- | # description. | + | |
- | # a separate .crt/.key file pair | + | |
- | # for each client. | + | |
- | # file can be used for all clients. | + | |
- | ca / | + | |
- | cert / | + | |
- | key / | + | |
- | + | ||
- | # Verify server certificate by checking | + | |
- | # that the certicate has the nsCertType | + | |
- | # field set to " | + | |
- | # important precaution to protect against | + | |
- | # a potential attack discussed here: | + | |
- | # http:// | + | |
- | # | + | |
- | # To use this feature, you will need to generate | + | |
- | # your server certificates with the nsCertType | + | |
- | # field set to " | + | |
- | # script in the easy-rsa folder will do this. | + | |
- | ; | + | |
- | remote-cert-tls server | + | |
- | + | ||
- | # If a tls-auth key is used on the server | + | |
- | # then every client must also have the key. | + | |
- | tls-auth | + | |
- | + | ||
- | # Select a cryptographic cipher. | + | |
- | # If the cipher option is used on the server | + | |
- | # then you must also specify it here. | + | |
- | ;cipher x | + | |
- | + | ||
- | # Enable compression on the VPN link. | + | |
- | # Don't enable this unless it is also | + | |
- | # enabled in the server config file. | + | |
- | comp-lzo | + | |
- | + | ||
- | # Set log file verbosity. | + | |
- | verb 3 | + | |
- | + | ||
- | # Silence repeating messages | + | |
- | ;mute 20 | + | |
- | #</ | + | |
===== 9. Testing the VPN ===== | ===== 9. Testing the VPN ===== | ||
Line 817: | Line 387: | ||
</ | </ | ||
- | Enter the Client PEM pass phrase when prompted. To stop openVPN | + | Enter the Client PEM pass phrase when prompted. To stop OpenVPN |
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 861: | 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 904: | 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 914: | 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 971: | Line 583: | ||
$IPT -A INPUT -j SERVICES # append the services chain to the input | $IPT -A INPUT -j SERVICES # append the services chain to the input | ||
- | # allowed forwarding for openVPN | + | # allowed forwarding for OpenVPN |
$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 -o eth0 -j MASQUERADE | $IPT -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE | ||
Line 981: | Line 593: | ||
#$IPT -A SERVICES -p tcp --dport 22 -j ACCEPT # Uncomment to allow sshd | #$IPT -A SERVICES -p tcp --dport 22 -j ACCEPT # Uncomment to allow sshd | ||
- | # allow openvpn | + | # allow OpenVPN |
- | $IPT -A SERVICES -p tcp --dport | + | $IPT -A SERVICES -p udp --dport |
| | ||
echo " | echo " | ||
Line 1038: | Line 650: | ||
</ | </ | ||
- | Restart the Openvpn | + | Restart the OpenVPN |
< | < | ||
Line 1050: | Line 662: | ||
</ | </ | ||
- | ===== 11. Firewalls ===== | + | ===== 12. Firewalls ===== |
- | In the previous chapter we referred to a firewall you may include to protect your Openvpn | + | 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 1100: | Line 712: | ||
You also have to modify your Router' | You also have to modify your Router' | ||
- | ===== 12. Sources ===== | + | ===== 13. Sources ===== |
(1) http:// | (1) http:// | ||
Line 1110: | 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> | ||