On 25/05/22 04:20 PM, Wolfgang Walter wrote:
Hi Wolfgang,
> opt-verify
>
> on the server side allows 2.5.6 clients to connect again. So it seems that
> 2.5 and 2.6 disagree on tun-mtu (as the warning is not logged if both sides
> are either 2.5.6 or 2.6).
Could you try again with the just
Am 2022-05-25 15:40, schrieb Bernhard Schmidt:
Am 25.05.22 um 13:39 schrieb Wolfgang Walter:
Hi,
Could you please check the release notes at
https://github.com/OpenVPN/openvpn/blob/dco/Changes.rst for relevant
changes and post logs/redacted config to this bug?
I read them and I found
Am 25.05.22 um 13:39 schrieb Wolfgang Walter:
Hi,
Could you please check the release notes at
https://github.com/OpenVPN/openvpn/blob/dco/Changes.rst for relevant
changes and post logs/redacted config to this bug?
I read them and I found nothing problematic. There is no problem with a
Am 2022-05-25 09:28, schrieb Bernhard Schmidt:
Control: tags -1 moreinfo
Hi Wolfgang,
openvpn 2.5.6 with openssl 1.1 seem unable to establish a connection
to a sid openvpn-server upgraded to 2.6.0~git20220518+dco-1.
I checked the configs. They work if both sides are 2.5.6 or both sides
are
Control: tags -1 moreinfo
Hi Wolfgang,
openvpn 2.5.6 with openssl 1.1 seem unable to establish a connection to
a sid openvpn-server upgraded to 2.6.0~git20220518+dco-1.
I checked the configs. They work if both sides are 2.5.6 or both sides
are 2.6 with openssl 3.
I also see the following
Package: openvpn
Version: 2.6.0~git20220518+dco-1
Severity: important
openvpn 2.5.6 with openssl 1.1 seem unable to establish a connection to
a sid openvpn-server upgraded to 2.6.0~git20220518+dco-1.
I checked the configs. They work if both sides are 2.5.6 or both sides
are 2.6 with openssl
6 matches
Mail list logo
