Hi,
openvpn3 is not packaged for Debian.
Yes, the client is:
https://tracker.debian.org/pkg/openvpn3-client
https://packages.debian.org/sid/openvpn3-client
Whoops, you are right. Sorry for missing that. Note that openvpn2 and
openvpn3 are two different implementations around the same wire
protocol, and don't have any overlap on the Debian maintainer side.
Upstream calls ovpn-dco-v2 obsolete, see
https://github.com/OpenVPN/ovpn-dco . There is no in-Debian consumer for
openvpn-dco-dkms. OpenVPN3 will need to migrate to the new in-tree dco
module at some point.
This behavior is very strange, I didn't know about the in-tree ovpn module, but
when I launch openvpn3 session-start with "--dco true" (you can test it), this
command
loads these modules:
ovpn_dco_v2 94208 0
ip6_udp_tunnel 16384 1 ovpn_dco_v2
udp_tunnel 40960 1 ovpn_dco_v2
But when I launch openvpn3 without any flags, no kernel module is loaded at
all, not even ovpn.
Yup, it looks like openvpn3 is still using the deprecated out-of-tree
ovpn-dco-v2 module.
Do you understand this, or do you know why this might be happening if this
module is deprecated?
Why does the v3 client use it?
I found some threads about the openvpn3 client in need to migrate to the
new DCO version, i.e.
https://codeberg.org/OpenVPN/openvpn3-linux/issues/96
On top of that, the OpenVPN 3 Core Library v3.11 releases does not support the
ovpn kernel module in the upstream kernel - which is the base line for the v27
releases. And we have an important DCO fix there as well, which is on the way
into the openvpn3-core git master - but not yet there. So right now, until we
get the v27.1 and a new Core v3.11 releases out the door, it will be a little
bit messy. It will eventually be properly synced up.
However, I cannot find any change going into that direction on
openvpn3-core master. So it might take some more time.
I assume openvpn3 will be on the new in-tree module before Forky is
released, so openvpn-dco-dkms can go for good. If not, someone is always
free to adopt this package.
Bernhard
