Getting ProXPN to function correctly on linux is not hard, but if you are on a non-Debian distribution, things can get a little tricky for those new to OpenVPN connections. The guide will presume :
- A functional ProXPN account has already been made
- A focus on EL7 flavors (go figure) of linux. This has been tested and used on several RHEL 7 Desktop installations.
1) Install openvpn and the NetworkManager plugins. The last package below is for KDE, so if you are not using KDE, you may safely ignore that package.
yum install openvpn NetworkManager-openvpn NetworkManager-openvpn-gnome kde-plasma-networkmanagement-openvpn
2) Grab the MacOS X package and extract out the “/MacOSX/config/” directory.
3) Inside the “MacOSX/config” directory you extracted, you will see the proxpn.ovpn file. Copy this anywhere that you are confortable using as a workspace, or if you are like me, a directory for all my .ovpn files.
tar -zxf proxpn_mac_source.tar.gz MacOSX/config/
4) Inside the “MacOSX/config/ssl/” directory you will see the 3 certificate files that you WILL need to establish a connection. I STRONGLY recommend putting these in the standard spot of “~/.cert/”. To do this, make a directory called “proxpn” in there and copy those files into it. This makes things clean, and simple for dealing with any SELinux issues (a refresh if need be on the .cert/ tree is all that is needed).
5) Now you can go into Network Manager and add a new connection. To do this without any of the GNOME Shell addons that make this very easy, is rather straightforward. You will need to do this for each location you wish to have readily available.
Enter into your Network settings.
Click the + button on the bottom left.
Select “Import From File”
Select the proxpn.ovpn file you saved earlier.
Change the Name field to be something descriptive such as “ProXPN – Miami”.
Change the Gateway field to be your exit node (nodes are listed below). For Miami, use “mfl1.proxpn.com”
Enter into the User Name and Password fields your login credentials.
For the “User Certificate”, point it to ~/.cert/proxpn/client.crt
For the “CA Certificate”, point it to ~/.cert/proxpn/ca.crt
For the “Private Key”, point it to ~/.cert/proxpn/client.key
Click on “Add”
Now to enable your VPN connection, all you need to do is click on the connection name in your Network Settings on the left pane, and on the right pane, click the On/Off toggle switch. Clicking it again will turn the connection off (when you are through using it). Depending on where you are connecting to and from, the connection process can be a bit lengthy, but that is an OpenVPN trait, and not specific to ProXPN.
OpenVPN Server List (Not all servers I have found to be reliable) :
UK 188.8.131.52 uk1.proxpn.com
Seattle 184.108.40.206 se1.proxpn.com
Singapore 220.127.116.11 sg1.proxpn.com
NY1 18.104.22.168 ny1.proxpn.com
NY2 22.214.171.124 bny1.proxpn.com
NL 126.96.36.199 nl1.proxpn.com
Miami 188.8.131.52 mfl1.proxpn.com
LA 184.108.40.206 la1.proxpn.com
Dallas 220.127.116.11 d1.proxpn.com
Czech 18.104.22.168 cz1.proxpn.com
And for posterity, here is the PPTP server list (Untested by me):
UK 22.214.171.124 pptp-uk1.proxpn.com
Seattle 126.96.36.199 pptp-se1.proxpn.com
Singapore 188.8.131.52 pptp-sg1a.proxpn.com
NY1 184.108.40.206 pptp-ny1a.proxpn.com
NY2 220.127.116.11 pptp-bny1.proxpn.com
NL 18.104.22.168 pptp-nl1.proxpn.com
Miami 22.214.171.124 pptp-mfl.proxpn.com
LA 126.96.36.199 pptp-la1.proxpn.com
Dallas 188.8.131.52 pptp-d1.proxpn.com
Czech 184.108.40.206 pptp-cz.proxpn.com