From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: OpenVPN-2.5.0 update procedure and idea collector
Date: Fri, 27 Nov 2020 14:24:23 +0100 [thread overview]
Message-ID: <e0f8f2e990d321ee58b66eb34e74839a9ac03708.camel@ipfire.org> (raw)
In-Reply-To: <0b611a91-46d1-3732-803c-02d1e795c9e6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2722 bytes --]
Am Freitag, den 27.11.2020, 13:40 +0100 schrieb Adolf Belka:
> Hi Erik,
>
> I tried downloading your file where the required files are already
> built. However I came up with a different sha256sum to the one you
> had in your file. I downloaded it several times and the same
> difference occurred each time.
That´s strange, have had such problems more often...
> I will do the build from scratch.
This might be even better :-)
>
> Regards,
>
> Adolf.
>
>
> On 27/11/2020 08:20, ummeegge wrote:
> > Good morning Adolf,
> >
> > Am Donnerstag, den 26.11.2020, 23:33 +0100 schrieb Adolf Belka:
> > > Hi Erik,
> > >
> > > I take it that I need to take the patch from your repo and apply
> > > it
> > > to my local repo and then build IPFire
> > you would only need to build the OpenVPN binary
> > https://patchwork.ipfire.org/patch/3679/
> > for those of you which can not build it by their own, in here
> > https://people.ipfire.org/~ummeegge/OpenVPN-2.5.0/
> > all files can be found.
> >
> > > and install it, and I will then have your version. Should I use
> > > master or next as the base on which to patch it.
> > the files from my repo can be manually installed, please backup up
> > all
> > existing files, the ovpnmain.cgi state is origin/next (incl. the
> > MTU
> > patch from Michael but excluding the up script line for the static-
> > routes for the client N2N).
> > After installation you need to execute 'update-lang-cache' via
> > console
> > that the changes in the language files takes affect.
> > Hit the save button also in the global section since --cipher
> > should be
> > renamed in --data-cipher-fallback...
> > Please check at the beginning that all your old settings are still
> > in
> > place.
> >
> > Thanks Adolf.
> >
> > Best,
> >
> > Erik
> >
> > >
> > > Thanks,
> > >
> > > Adolf.
> > >
> > >
> > > On 26/11/2020 19:47, ummeegge wrote:
> > > > Hi all,
> > > > for the interested ones, have push the current state to my repo
> > > > which
> > > > can be found in here -->
> > > >
> > > >
> > > > https://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=34af1d714178b2cd0c27e8c39052a8c7ce87d116
> > > > feel free to test and criticize it :-) .
> > > >
> > > > After integration and configuration, the 'save' button in the
> > > > global
> > > > section should also be pushed since --cipher will replaced by -
> > > > -
> > > > data-
> > > > channel-fallback. For the langs files, a update-lang-cache
> > > > should
> > > > be
> > > > executed via console so the changes can take affect.
> > > >
> > > > Happy testing. Best,
> > > >
> > > > Erik
> > > >
> >
> >
next prev parent reply other threads:[~2020-11-27 13:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 16:30 ummeegge
2020-11-23 9:14 ` ummeegge
2020-11-23 14:28 ` Kienker, Fred
2020-11-23 14:52 ` ummeegge
2020-11-23 18:06 ` Michael Tremer
2020-11-26 18:47 ` ummeegge
2020-11-26 22:33 ` Adolf Belka
2020-11-27 7:20 ` ummeegge
2020-11-27 12:19 ` Adolf Belka
2020-11-27 13:23 ` ummeegge
2020-11-27 16:43 ` ummeegge
2020-11-27 12:40 ` Adolf Belka
2020-11-27 13:24 ` ummeegge [this message]
2020-11-28 5:52 ` ummeegge
2020-11-28 14:12 ` Adolf Belka
2020-11-28 16:00 ` Adolf Belka
2020-11-29 11:15 ` ummeegge
2020-11-29 13:12 ` Adolf Belka
2020-11-29 18:36 ` ummeegge
2020-11-23 11:41 ` Adolf Belka
2020-11-23 14:44 ` ummeegge
2020-11-23 18:00 ` Michael Tremer
2020-11-23 22:29 ` Adolf Belka
2020-11-24 15:27 ` ummeegge
2020-12-14 14:13 ` Michael Tremer
2020-12-14 14:09 ` Michael Tremer
2020-11-23 17:58 ` Michael Tremer
2020-11-23 19:49 ` ummeegge
2020-11-23 22:38 ` Adolf Belka
2020-11-25 17:10 ` ummeegge
2020-12-14 14:05 ` Michael Tremer
[not found] <92ba003d-a1a9-4f7e-0608-35ff42f64bf8@gmail.com>
2020-12-01 4:26 ` 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=e0f8f2e990d321ee58b66eb34e74839a9ac03708.camel@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