Software Development, Cloud, DevOps and PfSense
The 2.0 release is finally available.
Here is the news:
My experience so far is good, I’ve already upgrade some of my machines.
You can take a look at the upgrade process from RC3 to RTM here:
Introduction
If you are in a café or another place with free wireless Internet access you are under a security risk. Your traffic can be monitored, captured and analysed. Your sensitive data can be stolen or your laptop infected with malicious application.
To avoid as much as possible of the above we can route all your traffic through the internet connection at home or in your office.
Configuration
As a base configuration you can use pfSense 2.0 RC1 configuration of OpenVPN Server for Road Warrior with TLS and User Authentication
up until the Tunnel Settings section of the OpenVPN Configuration.
There tick the Redirect Gateway.
Under Client Settings enter DNS Server 1 as the IP address of you LAN interface.
Explanation
By doing so you will redirect all your traffic through the VPN connection and avoid the risks related to the publicly available Internet access hotspots. The addition of DNS server address is needed in order to use you own device to resolve web sites IPs instead of the publicly available DNS server of the hotspot.
Testing
As a test you can trace route (tracert bbc.co.uk for example) a popular internet site with or without established VPN Connection.
Conclusion
At the cost of building just another VPN Server on your device you are gaining a little peace of mind while surfing the net from insecure location.