Am Thu, 26 Mar 2020 09:38:49 +0100
schrieb Arne Schwabe :
> > RPI? You mean Raspberry PI?
> > Maybe on this machine the problem is not a problem. We also use
> > OpenVPN 2.4.7 on a ARMv7, and there is no obvious problem, just on
> > the old ARMv4.
> >
> > Finding all problematic places in the
Am 25.03.20 um 19:35 schrieb Michael Kress:
> Hello Arne,
>
> Am Wed, 25 Mar 2020 12:50:34 +0100
> schrieb Arne Schwabe :
>>> 1) Do you run automated tests of the OpenVPN code on any build
>>> server?
>>>
>>> 2) If that is the case, is there any test with a version, where
>>>
Hello Arne,
Am Wed, 25 Mar 2020 12:50:34 +0100
schrieb Arne Schwabe :
> > 1) Do you run automated tests of the OpenVPN code on any build
> > server?
> >
> > 2) If that is the case, is there any test with a version, where
> >-DVERIFY_ALIGNMENT is enabled?
> >
>
> I never heard of this
>> LZO is known to miscompile with gcc 10 and requires
>> -fno-strict-aliasing to compile. and also in my OpenVPN for Android
>> app I have to compile lzo with -O1 instead -O2 since it otherwise
>> segfaults on armv7a. Android uses LLVM/clang to compile so the broken
>> behaviour is present also
вт, 24 мар. 2020 г. в 22:19, Michael Kress :
> Am Tue, 24 Mar 2020 11:21:56 +0100
> schrieb Arne Schwabe :
>
> > Am 23.03.20 um 17:11 schrieb Michael Kress:
> > > Hello list,
> > >
> > > There seems to be some kind of alignment problem in OpenVPN 2.4
> > > versions on ARMv4 based machines (32
Am Tue, 24 Mar 2020 11:21:56 +0100
schrieb Arne Schwabe :
> Am 23.03.20 um 17:11 schrieb Michael Kress:
> > Hello list,
> >
> > There seems to be some kind of alignment problem in OpenVPN 2.4
> > versions on ARMv4 based machines (32 bit), especially when lzo
> > compression kicks in.
>
> LZO
Am 23.03.20 um 18:19 schrieb Michael Kress:
> Hi,
>
> Unfortunatelly it seems, we are stuck to LZO for now, because it has
> been configured in the clients, which run 2.3. Most of these clients are
> offline most of the time, so reconfiguring or upgrading all of them
> before updating the server
Am 23.03.20 um 17:11 schrieb Michael Kress:
> Hello list,
>
> There seems to be some kind of alignment problem in OpenVPN 2.4
> versions on ARMv4 based machines (32 bit), especially when lzo
> compression kicks in.
LZO is known to miscompile with gcc 10 and requires -fno-strict-aliasing
to
Hi,
Unfortunatelly it seems, we are stuck to LZO for now, because it has
been configured in the clients, which run 2.3. Most of these clients are
offline most of the time, so reconfiguring or upgrading all of them
before updating the server will become difficult.
You are completely right: One
thank you for wonderful investigation.
however, are there reasons for using lzo ? it consumes too much cpu
(comparing to lz4). also, it highly depends on traffic itself, many
application already compress their bytes themselves.
if you are stick to lzo, because it is propagated to all configs,
10 matches
Mail list logo
