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 4cD4Qd39q5z30QP for ; Fri, 29 Aug 2025 17:05:29 +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) (Client CN "mail01.haj.ipfire.org", Issuer "R13" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4cD4QZ0XyNz2xMw for ; Fri, 29 Aug 2025 17:05:26 +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 x25519) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4cD4QX56s7z5n for ; Fri, 29 Aug 2025 17:05:24 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1756487124; 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; bh=t2hxQeCItStmSmiet5EAxJ3+0C3xXqaZg8NrhMUPa3w=; b=6Ad2EOvjLvedsn3KA0XgS+HsVHqMfuvZwfF2V+R80v6MmaMYXaZSmgAA6eTRqm3ND4dgij Sw01bUxl2WNXVPAQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1756487124; 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; bh=t2hxQeCItStmSmiet5EAxJ3+0C3xXqaZg8NrhMUPa3w=; b=gMiRtwDE3vhWG8AaJ8eLx785hSSp/mdp3aH7jxfSYaxy7jJ9xQYdB0EAc/jkt/GL/dPlhM vzuymteF/udfsJQEwzbGs3EQDkDFHDcTVeKschpPKE8NCOeqHPVfsX0fKZZ0E3e77KSffw 6vwm+r5nlvA6T+FRz86vQ9voarhXitM+o/MFiTvKQbDk9TlV6jtGCoq0T80B5A2pf0BrV3 MFAc0EG/uewHQStBp/ZdcWxO4zIj4BEx+Si0KMEHZt3WlJXZXdzVztz/xZ83Cze3/N5tKd ZmTJ3JnekEToneM+O6/0I09PoMofEuZkK2JjzU0Q4OA1AopKl9wERK9jUH6Apg== Message-ID: <76a9ee78-65ac-4117-b196-820580448ed8@ipfire.org> Date: Fri, 29 Aug 2025 19:05:24 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Content-Language: en-GB To: "IPFire: Development-List" From: Adolf Belka Subject: Problem with push routes when updating a CU196 openvpn to CU197 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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. Should I create a bug report for this? Regards, Adolf.