[ previous ] [ next ] [ threads ]
 From:  Peter Curran <peter at closeconsultants dot com>
 To:  "Quark IT - Hilton Travis" <hilton at quarkit dot com dot au>, <m0n0wall dash dev at lists dot m0n0 dot ch>
 Subject:  Re: [m0n0wall-dev] OpenVPN
 Date:  Tue, 8 Feb 2005 18:02:11 +0000

> Anyway, I'm asking if the next beta release of m0n0wall will have the
> current RC of OpenVPN 2.0 in it, because the current m0n0wall beta has
> an older (probably current at the time) OpenVPM 2.0 beta11 in it.  I'd
> like to hope that m0n0wall won't make 1.2 final until OpenVPN 2.0 has
> also gone final - it would only make sense (to me) considering this is a
> core component now.

I am about to send the latest version of the OpenVPN code to Manuel for 
inclusion in 1.2b4 (at least if I can get everything I need together as I am 
still working from remote).

The latest version includes:
-- OpenVPN 2.0 RC11 or RC12
-- Replacement for using the OPT devices to store OpenVPN tunnels (much more 
-- Support for bridging when using TAP tunnels
-- Support for PKCS#12 files on client side
--  Lost of interface bug fixes

I consider it likely that OpenVPN will hit 2.0 before 1.2 is out as I suspect 
that we have some way to go with the 1.2 beta series yet.  I had an email 
from Manuel some weeks ago that indicated that he was pretty busy and not 
able to do as much work on m0n0wall as he has in the past.

I am not convinced that m0n0-m0n0 using OpenVPN is a better solution than some 
sort of explicit tunnel secured with IPsec.  I really started the 
OpenVPN-in-m0n0 ball rolling to support vast numbers of Windows clients using 
OpenVPN.  The client side stuff was added later, and it is pretty crude at 
the moment.