public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Planning out Core Update 117
Date: Fri, 10 Nov 2017 14:35:12 +0100	[thread overview]
Message-ID: <9081866C-464F-4AB0-8CD8-F3D8A8623A98@ipfire.org> (raw)
In-Reply-To: <1510316322.4838.324.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1423 bytes --]

Hi Michael,

> Great.
> 
> Could you send the patch to the list so that we can comment on it?
OK will adapt the patches to Core 116 and send it as soon as possible to the dev list.

> 
> Also, do you have any plans to migrate to OpenVPN 2.4? Not sure how long 2.3
> will be patched.
Have builded and also tested the 2.4 from Alpha version to the until now actual 2.4.4 and have had no issues at all. The development in there --> https://forum.ipfire.org/viewtopic.php?f=50&t=18067#p104536 is relatively lonely since i do the testings on my own accept one user which made a very quick positive test. Since i normally want some more testers before i go for a merge request i am there a little lost until now since there is no feedback at all.
I developed a minimal solution which includes the needed changes to bring the 2.4.x version to life on IPFire but there is also an extended one with several new features also available over the ovpnmain.cgi.

Larger testing round can also be found in here --> https://forum.ipfire.org/viewtopic.php?f=50&t=17656 whereby i tried to explain also the new and for interesting features also al little.

I think 2.3 will be supported for longer time but 2.4 has some very good improvements under the hood and above and i think it might be nice for IPFire even some more testers might be great for that may it is nevertheless time to push it to mainline ?

Best,

Erik

  reply	other threads:[~2017-11-10 13:35 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-06 18:32 Michael Tremer
2017-11-06 21:06 ` Matthias Fischer
2017-11-07 10:44   ` Michael Tremer
2017-11-17 12:59     ` Matthias Fischer
2017-11-17 19:37       ` Matthias Fischer
2017-11-17 21:25         ` Michael Tremer
2017-11-17 23:15           ` Matthias Fischer
2017-11-18  7:44         ` Marcel Lorenz
2017-11-06 21:09 ` Matthias Fischer
2017-11-07 10:46   ` Michael Tremer
2017-11-07 15:05     ` Michael Tremer
2017-11-07 18:41       ` Matthias Fischer
2017-11-07 22:47         ` Michael Tremer
2017-11-21 14:42           ` Michael Tremer
2017-11-21 17:35             ` Matthias Fischer
2017-11-22 16:37               ` Michael Tremer
2018-01-29 13:23                 ` Compress images with XZ (was: Planning out Core Update 117) Michael Tremer
2018-01-30 16:47                   ` Compress images with XZ Matthias Fischer
2018-01-30 20:03                     ` Michael Tremer
2018-02-03 19:44                       ` Matthias Fischer
2018-02-03 21:09                         ` Matthias Fischer
2018-02-06  1:05                           ` Michael Tremer
2018-02-11 15:35                             ` Matthias Fischer
2018-02-11 19:57                               ` Michael Tremer
2018-05-11 20:27                                 ` Michael Tremer
2018-05-12  0:35                                   ` Tom Rymes
2018-05-12  8:48                                     ` Michael Tremer
2018-05-12 14:14                                   ` Matthias Fischer
2018-05-12 19:40                                     ` Michael Tremer
2017-11-10 11:01 ` Planning out Core Update 117 ummeegge
2017-11-10 12:18   ` Michael Tremer
2017-11-10 13:35     ` ummeegge [this message]
     [not found] <7EA8C1E7-14CC-4906-9688-504DA016795D@gmx.com>
2017-11-10 15:36 ` ummeegge
2017-11-18 20:53   ` Horace Michael
2017-11-21 10:25     ` ummeegge
2017-11-21 11:49       ` Michael Tremer
2017-11-21 12:30         ` Horace Michael
2017-11-22 10:30 ummeegge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9081866C-464F-4AB0-8CD8-F3D8A8623A98@ipfire.org \
    --to=ummeegge@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox