Category: Linux

PrivateInternetAccess SOCKS Proxy Tutorial – Software Installation

In this article we are going to run through the Debian, OpenVPN and Squid proxy software installation. In this tutorial we are installing it on a virtual machine in an ESXi environment but it can obviously be installed on any PC, virtual or otherwise. We are using a dual-core CPU with 2GB of RAM which is more than enough for a light-user proxy.

Let’s get started!

1. Download the netinstall iso, burn it to CD/DVD if necessary and boot. Run through the install and make sure to specify your static IP. You only need a minimal installation, no desktop manager so select the options as shown:

2. Once installed and logged in, update the apt repositories with apt-get update:

3. Install the OpenVPN software:

• apt-get install openvpn

4. Install the dante software software:

• apt-get install dante-server

Now we’re all installed, it’s time for the configuration.

PrivateInternetAccess SOCKS Proxy Tutorial – Introduction

In a previous series of articles we looked at how to use Squid Proxy to overcome the five devices maximum limit when subscribed to the PrivateInternetAccess VPN anonymising service. While this is useful when needing to browse anonymously, it doesn’t help when using other non-HTTP protocols  e.g. FTP, SMTP, SSH so to that end we present this PrivateInternetAccess SOCKS Proxy tutorial.

To this end, we need to employ a SOCKS (sockets) proxy: A SOCKS proxy is a general purpose proxy server that establishes a TCP connection to another server on behalf of a client and then routes all the traffic back and forth between the client and the server. It works for any kind of network protocol on any port.

In this tutorial we will be building on parts of the previous tutorial but using the Dante SOCKS proxy instead of Squid.

We will be using:

• Debian Wheezy netinstall ISO
  • OpenVPN – to create our VPN connection
  • dante – to proxy specific traffic or applications through the VPN

Our network diagram for this example is as follows:

The client is sitting on the 172.16.16.0 network and accessing the proxy in the DMZ 192.168.101.0 subnet. Outgoing traffic will then be routed out through the VPN interface (tun0) encrypted and anonymised.