[![](http://blog.jumpbox.com/images/2009/01/rampupheader.gif "rampup")](http://blog.jumpbox.com/category/screencasts/) [![OpenVPNrampup](http://blog.jumpbox.com/images/2010/04/OpenVPNrampup.png "OpenVPNrampup")](http://openvpn.net/)

We’re proud to present the newest addition to the library today: The JumpBox for OpenVPN. If you have a distributed work force, are looking to offer telecommuting capabilities to your employees or simply want a solution for accessing the contents of your office network from the road, the JumpBox for OpenVPN is your answer. From the OpenVPN about page, noteworthy “S’s” of using OpenVPN include:

  • Security: OpenVPN’s security model is based on using SSL/TLS for session authentication and the IPSec ESP protocol for secure tunnel transport over UDP.
  • Stability: If the IP layer goes down for 5 minutes, when it comes back up, tunnel traffic will immediately resume even if the outage interfered with a dynamic key exchange which was scheduled during that time.
  • Scalability: Configure a scalable, load-balanced VPN server farm using one or more machines which can handle thousands of dynamic connections from incoming VPN clients,.
  • Simplicity: OpenVPN is an extensible VPN framework which has been designed to ease site-specific customization, such as providing the capability to distribute a customized installation package to clients.
  • Standards: OpenVPN has been built with a strongly modular design. All of the crypto is handled by the OpenSSL library, and all of the IP tunneling functionality is provided through the TUN/TAP virtual network driver.
  • Speed: OpenVPN achieved a send/receive transfer rate of 1.455 megabytes per second of CPU time running Redhat 7.2 on a Pentium II 266mhz machine, using TLS-based session authentication, the Blowfish cipher, SHA1 authentication for the tunnel data, and tunneling an FTP session with large, precompressed files.

In this 12min video we’ll use the JumpBox for OpenVPN to bridge two disparate home networks and then use VNC to take control of a remote computer across the VPN. We’ll launch the OpenVPN JumpBox on Amazon EC2 and establish a temporary cloud-based VPN to conduct remote tech support (with someone who is quite possibly the world’s least-technical person ;-).

Having a dormant, pre-configured OpenVPN JumpBox in EC2 gives you a simple, cost-effective mechanism to deliver remote tech support on demand. This JumpBox allows you to make remote resources appear local so there are many other interesting use cases it enables. You can work along with the video by launching an instance of your own using the widget below. Enjoy!

P.S. Make sure to join us this Friday for the first ever “Study Hall” where we’ll show undocumented features and answer live Q & A from attendees. You’ll have a chance to win a free annual Pro account by attending and we’ll take the first 30 signups. Details here.

Time Topic
01:16 Revive a suspended OpenVPN JumpBox on EC2
02:30 Generate the keys to be used by the client
04:41 Move the generated keys to the local client machine
06:20 Configure the TunnelBlick VPN client
08:20 Connect the source & target machines to the VPN
09:24 Launch VNC client and take over target machine

*Tip: To view video at full-resolution in hi-def, make sure the button is on and click the button to expand the screen.