Start with the example in the docs.Ĭp /usr/share/doc/openvpn/examples/sample-config-files/nf. Next, back on the server, create the openvpn server config file. Switching to the client machine for just a moment, copy the client keys to the /etc/openvpn directory. The files needed by the client are ca.crt, client_kevin.crt, and client_kevin.key (or whatever you named the files when you generated them with the build-key script). Copy the keys listed below to the server's /etc/openvpn directory.Īnd copy the keys needed for the client either directly to the client via scp or to a USB disk. When this is done, you will have a number of files in the keys/ subdirectory. Generate the Diffie Hellman parameters for the server. For the client keys (build-key), use 'client1' or 'client2' or whatever you like, I used 'client_kevin'. For the Certificate Authority (build-ca), use 'server'. For the 'Common Name' field, you can use anything to your liking. Next, source the vars file and then clean the directory. In the vars file, edit the KEY_* entries at the bottom of the file, such as KEY_COUNTRY, KEY_ORG, KEY_EMAIL, etc. Next, create the keys needed by both server and client.Ĭp -ai /usr/share/doc/openvpn/examples/easy-rsa/2.0/ /etc/openvpn/easy-rsa
#AIRVPN CONFIG GENERATOR INSTALL#
First, install OpenVPN on it, with (e.g.) If you're cautious (and that's a good thing!), repeat these baseline diagnostics after installing those packages, to be extra-sure your client is still networking properly. Note that, in section= Client configuration (below), you'll be installing some network-related packages. It should return the client IP# as listed in your ifconfig. Open a web browser and access (or the IP-echo website you prefer).
The number of lines of traceroute output (aka the number of "hops") is probably not relevant.Ĩ. The last IP# must be that of your target IP-echo website (as noted by nslookup and ping). The first IP# is your IP gateway (e.g., the modem/router on your client's physical LAN). Trace the route to (or the IP-echo website you prefer). ping (or the IP-echo website you prefer): this will later be used to establish validity of routing beyond your VPN. Use (or the IP-echo website you prefer), since you will access this website later. This should fail, since you have not yet setup your VPN.ĥ. ping your server from your client using IP#=10.8.0.1. If this fails, you probably don't actually know its IP#, and you must know it, so stop now and learn it.Ĥ. ping your server from your client using the server's IP#. From your ifconfig, note the IP# (or inet addr) of the ethernet interface you are using. E.g., from a workstation with both wired and wireless ethernet interface, you should see something sudo ifconfig -aĢ. Your client's ifconfig should not have an entry for tun0. Switch to your client and run the following diagnostics:ġ. These notes presume you are not ethernet bridging: i.e., these instructions are for dev tun not dev tap.įirst, let's be sure that you know the real IP#s of both your client and your server, and that your underlying networking is sound. We do a quick "client baseline," then the server config, then the client config, then testing. Once setup, all internet traffic, including browser traffic, from the client will travel via the VPN to the server. These notes cover the installation of OpenVPN on a Debian server and client. Configure openvpn on a Debian server and client
0 kommentar(er)
