On Sun, Aug 02, 2026 at 01:29:13PM +0200, Bernhard Schmidt wrote: > Hi Angel,
Hi Bernhard > Am 01.08.26 um 12:29 schrieb Angel Abad: > > Hello, I don't fully understand your comment that the dco module only works > > with OpenVPN 2.6. > > > > I use this module (openvpn-dco-dkms) with the openvpn3-client package, via > > the --dco true flag. > > > > You can see this option in the openvpn3-client documentation here: > > > > https://openvpn.net/community-docs/openvpn-client-for-linux.html#about-dco--data-channel-offload- > > > > So, currently I'm affected by this bug on sid with openvpn3-client. > > > > Thanks for your work! > > openvpn3 is not packaged for Debian. Yes, the client is: https://tracker.debian.org/pkg/openvpn3-client https://packages.debian.org/sid/openvpn3-client > 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. 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? Happy to provide more logs/output if needed. Thanks! Angel, > Bernhard > >
signature.asc
Description: PGP signature
