Leaderboard

Maybe we already built DCO including the TCP rework (on our dedicated server)? Can you tell when the rework and simplification have been committed? To use that change you need openvpn 2.6.2 in userspace, which was released just yesterday. So the tests you performed were still using the old ovpn-dco version. You can easily check dmesg and see what version you have loaded. If the DCO version starts with v0.1 it means it's the "old" one. If it starts with v0.2, then you have the newest version including the change I am talking about. Just remember that you must use openvpn-2.6.2 to be able to use DCO v0.2. Should you guys have a chance to run DCO v0.2 and encounter any issue, do not hesitate to let us know! Thanks a lot

Hello! We have experienced a serious kernel panic problem apparently reported here: https://github.com/OpenVPN/ovpn-dco/issues The reported kernel crashes which we also experienced are fearsome, because when they occur all users (even WireGuard ones of course) are disconnected, machine control is lost, and a reboot via IPMI or hard power cycle is required. Before allowing something to run as a kernel part on a production server for all of you, that something must behave more properly. We will keep testing and searching for a stable setup, and of course we also hope in imminent bug fixes. We will keep you informed. Of course rolling out OpenVPN 2.6 without DCO is an option, but we would prefer to migrate directly to OpenVPN with DCO, instead of having to do it in two different steps. Kind regards