Next, we need to allow IPv4 forwarding so the server can send out packets on the VPN’s behalf. # NOTE: If you are running OpenVPN in a virtual machine, then uncomment these lines: # dns-* options are implemented by the resolvconf package, if installed # This file describes the network interfaces available on your system You will, of course, adjust the file for your specific subnet scheme. This creates a new br0 interface and allows eth0 to essentially communicate across it (hence the label ‘bridge’). When editing this file, you need to remove or comment out the original eth port settings and replace with what you see below. This is done by modifying the interfaces file. OpenVPN requires this ‘virtual interface’ when setting up the tap interface it needs to pass traffic into the internal network. On the Ubuntu Server, we need to start by configuring the bridge adapter with Bridge Utilities. apt-get install bridge-utils openvpn libssl-dev openssl However, with a recompiled client, you can also use Id/password authentication as well providing 2 factor auth into your network (something you have = the cert, something you know = the password).īefore we begin, lets get the installation of the pre-reqs done. Out of the box, OpenVPN relies on certificate based auth. OpenVPN has a few methods of authentication.

However, for PC/MAC/Linux clients, it works just fine. The big downside to this is that Android clients as of 4.2.2 don’t support TAP based tunnels. Very useful if you don’t have a gateway/router in the local subnet that can do static routes since, to the internal hosts, the traffic will seem to originate from a locally connected device on the same subnet. The TAP solution is useful if you want the remote VPN users to use the same IP scheme that is in use on the local subnet. This article will guide you in a basic OpenVPN installation on an Ubuntu server running 12.04 or 14.04 using a TAP device on the server.

Download ubuntu 14.04 headlesss