Re: [Openvpn-devel] Patch Queue, was: Re: [PATCH] Fix for "Cannot read current defaultgateway" problem on Linux

[David Balazic]

James Yonan wrote:

> Alon Bar-Lev wrote:
> > On Tuesday 10 February 2009 13:35:35 David Balazic wrote:
> >> Ping ?
> >>
> >> Should I resend the patch without the end-of-line-spaces change ?
> > 
> > James has his own response times.
> > I suggest you have much patience :)
> > 
> > Alon.
> 
> I apologize for not having the bandwidth to focus as much on 
> the patch 
> queue as I would like, but please understand that we're on 
> the verge of 
> releasing 2.1 and we have to be very conservative about accepting 
> patches at this point.
> 
> I think it's fair to ask that we try to limit ourselves at this late 
> stage to patches that address issues that affect a large number of 
> users, or bug fixes that are sufficiently trivial that there 
> is little 
> or no chance of causing unforeseen breakage.  I think there 
> needs to be 
> an argument for why the patch is important right now, as opposed to 
> waiting a while for the 2.2 beta series.

Of course.

 - the bug has been reported in several instances (see my first mail)
 - the patch affects only one architecture (besides the unused parameter
on others;
I could have made different function declarations for different archs,
but that
would be less readable/maintainable IMO)
 - the patch affects only one code path, that is taken only when the bug
is triggered
 - it is simple:
   - a few lines to record the gateway interface name
   - a few lines to use it in case the gw addresss is 0.0.0.0
 - it is field tested (in a scenario which triggers the bug)

Regards,
David

Re: [Openvpn-devel] Patch Queue, was: Re: [PATCH] Fix for "Cannot read current defaultgateway" problem on Linux

[Alon Bar-Lev]

On 2/12/09, James Yonan  wrote:
> fixes that are sufficiently trivial that there is little or no chance of
> causing unforeseen breakage.

Please review the following ones [1][2] for windows compilation.
Only renames.

Alon.

[1] 
http://www.opensc-project.org/build/browser/trunk/patches/openvpn-002-mingw.patch
[2] 
http://www.opensc-project.org/build/browser/trunk/patches/openvpn-003-windows.patch

[Openvpn-devel] Patch Queue, was: Re: [PATCH] Fix for "Cannot read current defaultgateway" problem on Linux

[James Yonan]

Alon Bar-Lev wrote:

On Tuesday 10 February 2009 13:35:35 David Balazic wrote:

Ping ?

Should I resend the patch without the end-of-line-spaces change ?


James has his own response times.
I suggest you have much patience :)

Alon.


I apologize for not having the bandwidth to focus as much on the patch 
queue as I would like, but please understand that we're on the verge of 
releasing 2.1 and we have to be very conservative about accepting 
patches at this point.


I think it's fair to ask that we try to limit ourselves at this late 
stage to patches that address issues that affect a large number of 
users, or bug fixes that are sufficiently trivial that there is little 
or no chance of causing unforeseen breakage.  I think there needs to be 
an argument for why the patch is important right now, as opposed to 
waiting a while for the 2.2 beta series.


Remember that sometimes just posting a patch here on the list is an 
optimal solution even if it is not immediately merged into the mainline 
-- people that need it can always apply it, and this allows the patch to 
be tested more extensively before it is merged.


James

Re: [Openvpn-devel] IPv6 Support

[James Yonan]

Marcel Pennewiß wrote:

On Thursday 13 November 2008 01:23:46 Marcel Pennewiß wrote:

Hi,


Hi again,


a long time ago Juanjo Ciarlante wrote a patch for openvpn to create a
tunnel via ipv6 [1]. Later i fixed the patch to work with openvpn-2.0 and
2.1 which i use on OpenWRT and Gentoo. Roy (from Gentoo) wrote about this
also to the devel-list [1]. But since that no one answered :(

What about IPv6-support to create a tunnel over IPv6? Since my first patch
i try to adapt the patch to newer versions. This patches are not properly
tested but works fine for me (on gentoo).[2][3]


What about full IPv6-support - is this scheduled in the future or on any 
roadmap? No answer is not a good practice :(


Full IPv6 support is planned for OpenVPN 3.

Some more details on OpenVPN 3:

OpenVPN 3.0 is a revamping of the OpenVPN core into a modular, more
maintainable architecture.  Planned features include:

* IPv6 support
* IP multicast support
* Pluggable crypto library support (so that crypto libraries other than
OpenSSL may be used)
* Pluggable packet filter and network access control API
* Pluggable dynamic routing API (BGP, OSPF, etc.)
* Support for full-mesh topologies (in addition to the star and
point-to-point topologies supported in OpenVPN 2.x)
* Library API support allowing OpenVPN tunnels to be programmatically
created and destroyed
* Embedding support to allow OpenVPN to be embedded in other applications
* Asynchronous, event driven I/O subsystem (in the vein of Twisted,
boost::asio, or libevent)

James