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 4cDBmx46ptz30Qc for ; Fri, 29 Aug 2025 21:51:45 +0000 (UTC) Received: from mail01.ipfire.org (mail01.haj.ipfire.org [IPv6:2001:678:b28::25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (secp384r1 raw public key) server-digest SHA384 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mail01.haj.ipfire.org", Issuer "R13" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4cDBmt14nbz2xP7 for ; Fri, 29 Aug 2025 21:51:42 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4cDBmr1mFmz3Fq; Fri, 29 Aug 2025 21:51:40 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1756504300; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=b4uU2xWO6lEe2IxWsp/lzROz+JVkyyi2UNtTvxt50sw=; b=FUIWF3JKuK4/NZpWtYAGqsgMrKpzLIk41joLXHGymf73Pb6uRTNa0hpavN5s43TcNjD0vW upctfP9nLtOcY+DQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1756504300; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=b4uU2xWO6lEe2IxWsp/lzROz+JVkyyi2UNtTvxt50sw=; b=FrtYTby1/XTgodQNx+EJcmgqQeGoZ77R1o+8gnR/Zzxu60LbEL/+5LbOFVYiRLgqsM7ySO jAbTPQ0aVEzA80mqLu/aT3qUu1nBwh5Y6a71/c00l/XYiKSubaO3vShEbpb3ck9QsxQMfl mWs7yb9Lwjp04cIlJBJH5PkbLG47bA71mPbEeKOcil+3rytiJtPaewkU+tQQkCqHFTOU0Q fx0iY6VtewYnGQBUKkwjkL11rNBbjkutdZBkOeNxrfE8YzXbl5Gcy+bjuzlue76MTQElLz zNAkEDUiPdgvIEOezQ1236Ro+aGBPbWShJkjCH3ruagD9wYE/xXKeUCLIxaUqQ== Content-Type: text/plain; charset=us-ascii Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: Problem with push routes when updating a CU196 openvpn to CU197 From: Michael Tremer In-Reply-To: Date: Fri, 29 Aug 2025 22:51:39 +0100 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: References: <76a9ee78-65ac-4117-b196-820580448ed8@ipfire.org> To: Adolf Belka Hello, This was probably introduced in this commit: = https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dcommitdiff;h=3D460942d7ed28= ebf8c7727faa6321b63ee1c56964 It is supposed to read the routes_push file and write it to = /var/ipfire/ovpn/settings. This should happen whenever the CGI script is being called and does not = even require that any configuration is being rewritten. Can you confirm that nothing is in ROUTES_PUSH? Best, -Michael > On 29 Aug 2025, at 19:50, Adolf Belka wrote: >=20 > Hi All, >=20 > On 29/08/2025 19:05, Adolf Belka wrote: >> Hi All, >> I normally have not had any routes to be pushed specified on my = openvpn connections. While investigating some other things I did some = setups with routes specified in the CU196 server advanced settings. = These were stored in the routes_push file and defined in the server.conf = file. >> When I did an update to CU197 I found that the routes were specified = in the routes_push file but no longer in the server.conf file. They were = also not in the ROUTES_PUSH entry in the settings file. >> I then went into the Advanced Settings page on the CU197 and the = routes were in the push routes entry box but separated by a blank line. >> I then pressed the Save Advanced Settings button and now the routes = were in the server.conf and settings files and were in the advanced = settings page without any blank lines between them. >> So something is not being fully completed when doing an update from a = CU196 server with push routes specified and it requires the advanced = settings to be saved to get everything updated as it should be. >> I suspect that a similar thing might happen if a CU196 backup with = push routes is restored into a CU197 system but I haven't tested this = yet. I will feedback what I find when I do that. >=20 > I can confirm that the same thing happens when a CU196 backup with = push routes specified does the same thing as described above and = requires the Save Advanced Settings button to be pressed to put = everything in the right files. >=20 > Regards, >=20 > Adolf. >=20 >> Should I create a bug report for this? >> Regards, >> Adolf. >=20 >=20