Adolf, i have another request for you :-) ,
if the 2.5.0 binary has been build, can you please check first (no nnew
cgi or lang files) before all if it works with your actual clients and
report it here -->
https://lists.ipfire.org/pipermail/development/2020-November/008783.html
this might be great.

Thanks and best,

Erik


Am Freitag, den 27.11.2020, 14:23 +0100 schrieb ummeegge:
Hi Adolf

Am Freitag, den 27.11.2020, 13:19 +0100 schrieb Adolf Belka:
> Good Morning Erik,
> 
> Thanks for the information. You say that I only need to build the
> OpenVPN binary. I may be missing something here with my knowledge of
> IPFire. The only way I know to build the OpenVPN binary in IPFire is
> to do the ./make.sh clean followed by ./make.sh build which then
> builds the whole of IPFire. Are you suggesting that I build the
> OpenVPN binary by doing the ./configure then make then make install
> commands or is there some other way that I am not aware of.
> I am still learning a lot about what is "under the bonnet" in IPFire
> programming so excuse me if my questions are a bit basic.
you would need to make a clean build if the ROOTFILE is not produced.
In the patchwork link you can find the changes in the ROOTFILE which
you can adapt to the already existing under ipfire-
2.x/config/rootfiles/common/.
You would need the sources from OpenVPN community download page, move
openvpn-2.5.0.tar.xz to the cache folder, check the md5sum and change
the OpenVPN LFS file with this data.
You won´t need ./configure since all that is already in the LFS build
stage. Here https://patchwork.ipfire.org/patch/3679/
scroll to the bottom and you can find the path and diffs.

If this is done, just delete the OpenVPN log under ipfire-2.x/log and
make a ./make.sh build. After that you can find the new binary under
ipfire-2.x/build/usr/sbin .

Best,

Erik

> 
> 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
> > > > 
> > 
> >