From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [IPv6:::1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4fGyPV6dsrz3613 for ; Thu, 19 Feb 2026 15:45:02 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519) (Client CN "mail01.haj.ipfire.org", Issuer "R12" (not verified)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4fGyPQ5MlDz2xHP for ; Thu, 19 Feb 2026 15:44:58 +0000 (UTC) Received: by mail01.ipfire.org (Postfix, from userid 106) id 4fGyPQ2dBLz5lB; Thu, 19 Feb 2026 15:44:49 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange secp256r1 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4fGxTn1RXGz5jf for ; Thu, 19 Feb 2026 15:03:41 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1771513421; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iFGKAbjMMms7JwCS+NcTfpM63W6NALaANQ/Wy145xJ0=; b=/TaVDrz3wdZOD5bWKKWRUOt1EjFLS3T2+6TP1R9nqn1o4gZ5jnxBrnbyPzw0hDozN+f9ZU 1OHt9mFB9ITxSLBQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1771513421; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iFGKAbjMMms7JwCS+NcTfpM63W6NALaANQ/Wy145xJ0=; b=uTWro2xccVtmn1TSmKE/0d8jl4fWK3T+XsjOOcCqa9/UYF75YLU5RlZerCIcfQkK/mREYB AIyt1KvfC3R4rlKMdnyy0HqcjazCqZTKMNVLFDlLCjeyaKcQKuVKG33ABj0y+aR4ey1Lzx 25WtA7NVD37h7Vj2tt+nfoBouKkJ+BLPGF25ZLRClXyf9YMT4AFhZo5KjwoSlUeA83vRl3 KbIP6ekCa3FlRQGTV9RFT+FlKJL9gQUfxIEizSIqZPHJtF8DQoeH8DOukthNykLDkwIce9 8b2sepWMePY4vQGqH+9lZBrrE/Ddi34g7qvRNZwb8wpnCStNO59JaBNBfPscqw== Message-ID: <414d5c1c72ceabb0f3051ba917bb45ff7de3f90f.camel@ipfire.org> Subject: Re: openvpn-2.7_rc1 From: ummeegge To: development@lists.ipfire.org Date: Thu, 19 Feb 2026 16:03:36 +0100 In-Reply-To: <4247a605-6aac-4c9c-93c8-db236c2cb769@ipfire.org> References: <4247a605-6aac-4c9c-93c8-db236c2cb769@ipfire.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Hi all, since OpenVPN 2.7.0 was released last week, I=E2=80=99ve done some more tes= ting with the new DCO flag. ``` @@ -73,10 +73,10 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects)) cd $(DIR_APP) && ./configure \ --prefix=3D/usr \ --sysconfdir=3D/var/ipfire/ovpn \ - --enable-iproute2 \ --enable-plugins \ --enable-plugin-auth-pam \ - --enable-plugin-down-root + --enable-plugin-down-root \ + --enable-dco ``` I=E2=80=99ve found a couple of other issues: There have been some changes in the management interface, and a protocol prefix is now included (e.g. udp4:). As a result, the old regex patterns for a) OpenVPN Connection Statistics and b) Connection Status no longer update or show data. This shouldn=E2=80=99t be hard to fix. With OpenVPN 2.7.0, a MULTI ERROR appears when creating a client with =E2=80=9Credirect-gateway=E2=80=9D. Example message: ``` Feb 19 13:34:36 ipfire-prime openvpnserver[7329]: PeterForden/udp4:192.168.110.10:38103 MULTI ERROR: primary virtual IP for PeterForden/udp4:192.168.110.10:38103 (10.12.52.2) violates tunnel network/netmask constraint (10.73.104.0/255.255.255.0) ``` The connection still works fine, but the log entries don=E2=80=99t look goo= d. This happens because older setups used `redirect-gateway def1` in the advanced options, and remnants of this are still present in server.conf (push "redirect-gateway def1"), even though the checkbox for this option has disappeared. When creating a new client, enabling redirect-gateway (here without def1) now triggers this MULTI ERROR (=E2=80=9Cviolates tunnel network/netma= sk constraint=E2=80=9D). Using redirect-gateway def1 might actually be the better and more modern approach, since it adds two more specific routes (0.0.0.0/1 and 128.0.0.0/1) instead of replacing the original default route =E2=80=94 keep= ing it available as a fallback. =E2=86=92 Should `redirect-gateway def1` therefore be pushed globally for a= ll clients? If not explicitly configured otherwise, it would still apply. So far, DCO seems to makes his job. Some smaller issues have been noticed, but I think these are the key points so far. Hope this mail isn=E2=80=99t **too long**, but I thought it might be useful= to share. Best, Erik Am Donnerstag, dem 06.11.2025 um 22:19 +0100 schrieb Adolf Belka: > Hi All, >=20 > Follow-on from my previous mails about testing openvpn-2.7_alpha3. >=20 > Since then I have tested out openvpn-2.7_beta1 and today I tested out > openvpn-2.7_rc1 >=20 > It built without any problems and I also tested it on my vm system > and confirmed that my android phone and linux laptop road warriors > worked without any problems. > I also tested out the n2 connection with openvpn-2.7_rc1 at one end > and openvpn-2.6.15 at the other end and it connected without any > issues. >=20 > So the rc1 version has performed as the previous alpha3 and beta1 > versions. >=20 > I have merged the build branch into my ipfire repo >=20 > https://git.ipfire.org/?p=3Dpeople/bonnietwin/ipfire-2.x.git;a=3Dshortlog= ;h=3Drefs/heads/openvpn-2.7_rc1 >=20 > Regards, >=20 > Adolf.