Karol Babioch wrote:
Hi Per,
Am 05.10.19 um 10:10 schrieb Per Jessen:
I am in fact running 2.3.8. Guess I'll need an upgrade. I'd still like to know what prompted this, on 29 August.
I guess we upgraded the machine running OpenVPN on the server side to Leap 15.1 on Aug 29, which also included an update to OpenVPN itself:
Before the version we ran (and apparently didn't update for quite a while):
2017-10-27 19:30:07|install|openvpn|2.3.8-14.1|x86_64||repo-update-oss|271268eb074aa7199d88c957958c37a85f1aa03b3e28620aa09d2500673ae450|
Since August 29 we are now running:
2019-08-29 06:29:42|install|openvpn|2.4.3-lp151.4.3|x86_64||repo-oss|69ab2871d4175728a2e0eb581ebaa46c7c274aa23babd3156b7c0596614ab9b4|
Additionally a whole bunch of other packages have been touched (due to the distribution upgrade). I didn't notice anything wrong on my end, though, but on the other hand I'm not running the tunnel constantly and I'm running 2.4.7 locally.
Thanks Karol, that explains it. I just don't like such changes, without knowing what happened :-) I was unable to build the latest openvpn, so instead I patched my 2.3.8, to ignore the peer-id. Sofar it seems to have worked. /Per -- Per Jessen, Zürich (13.0°C) Member, openSUSE Heroes -- To unsubscribe, e-mail: heroes+unsubscribe@opensuse.org To contact the owner, e-mail: heroes+owner@opensuse.org