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 4cQN2X3XQ3z32wX for ; Mon, 15 Sep 2025 11:23:48 +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 server-signature ECDSA (secp384r1) 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 4cQN2T109zz2xQ9 for ; Mon, 15 Sep 2025 11:23:45 +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 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4cQN2R2VZbzkM; Mon, 15 Sep 2025 11:23:43 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1757935423; 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=yAARbyDcjpkRN9XXWkgkTBv44YLTIU8gXpqMH2c8n8A=; b=PAKu9ql7WyaFagwGLhz46akfy0DLYwyBSBsoMblEV92VV6c5s3Lnmuj6b1fH63hTPj8GAQ ATo3mrzyxspVLWDQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1757935423; 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=yAARbyDcjpkRN9XXWkgkTBv44YLTIU8gXpqMH2c8n8A=; b=LEaaXY2SAjNVsmFPTH7nHvk9x8Vxv+0IdphPB2Fr/cRhTWh7gAB/vFjKgSAESQdip0uybK 1UApx2NH5XL13HE6uMX9b40ToNfHu47iVANJ/E48S9cW/iNd5HMzbLbJA3f3sETbdW+whn wSaDJgY6X6vBcQ5uKfhahZrcYxJ4YKd25dmtgFf3SUExUodoc7FfkpV6OB9kpMQtzORAsK 0fG6RgKQRAvBdD6/ZN2MgmP2l99caD4ctoatlZofDfSWpQ4n3V03NAO2CI9aCiuLsx3Co1 dpU9TCBC+hoXdQNtQ9Qe67W4ugDYN128jsFk7GCYIvp36NWbXvoz3Uv7LHklEw== Message-ID: <27af52c0-d46d-4772-94eb-438f21ea62cf@ipfire.org> Date: Mon, 15 Sep 2025 13:23:40 +0200 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: MIME-Version: 1.0 Subject: Re: CU197 Testing - OpenVPN Road Warrior Statistics graphs not working. To: Michael Tremer Cc: "IPFire: Development-List" References: <4d1adf3c-1165-4cbf-917d-ea80c6009209@ipfire.org> <42d98f14-ffa8-4513-a5c5-04559d2624a0@ipfire.org> Content-Language: en-GB From: Adolf Belka In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi Michael, I am going to reply to all the openvpn changes related to CU197 Testing. The changes for the Road Warrior Statistics graphs worked. All the graphs are working in CU197 Testing. I also submitted changes for the wio addon to update the RW log file name. Those changes were implemented but obviously are not enough to make wio show the openvpn connection statuses. There must be some other aspects that the wio code is using that need to be updated. However, I think that this can be left for CU198. The status of the openvpn connections can be see on the openvpn WUI page and I don't think we need to delay CU197 Testing for me to fix the wio openvpn status. I will continue to look at that and submit any required patches once I understand what other changes in wio are needed. I also tested out the routes stuff, to the extent that I could.The data from the routes-push file is now being correctly taken on board and applied in the server.conf and then the old routes-push file is removed. The problem of the gateway push problem that @iptom raised the bug for, I don't think I can easily test as I could never reproduce the problem he had in my network, which is a very simple limited network. I will update the bug and request @iptom to test out the new CU197 Testing build. Presuming the routes issue of @iptom is solved with the latest version, then I am not aware of any remaining issues to block release. Regards, Adolf. On 14/09/2025 12:40, Michael Tremer wrote: > Sorry, I just overlooked them. > > I merged them and pushed them just now. > > -Michael > >> On 14 Sep 2025, at 11:11, Adolf Belka wrote: >> >> Hi Michael, >> >> On 08/09/2025 15:07, Adolf Belka wrote: >>> Hi All, >>> On 03/09/2025 20:21, Adolf Belka wrote: >>>> Hallo All. >>>> >>>> I have found another issue with OpenVPN on CU197 Testing. >>>> >>>> The RW graphs Statistics graphs are not getting updated. >>>> >>>> After some searching around, I found that it was because the collectd.vpn plugin was still saying /var/log/ovpnserver.log >>>> >>>> I discovered that there was an update to the collectd.vpn file but collectd was not shipped in CU197 Testing so it didn't get included. >>>> >>>> I have submitted a patch to ship collectd in CU197 Testing. >>> I have dropped that patch in patchwork. >>> I realised that doing that would update the ovpnserver.log to openvpn-rw.log but it would also remove any n2n entries in collectd.vpn >>> I have submitted two new patches. One for update.sh in CU197, which after running the ovpnmain.cgi file checks if collectd.vpn has the old log file name in it and if so replaces it with the new version. >>> The other patch is to do the same thing in backup.pl for any restores from old backups before CU197. >>> This makes sure that the RW entry is updated but leaves any existing n2n entries alone in collectd.vpn. >>> The above was tested and resulted in working graphs for the RW connection. >> >> The two new patches mentioned above >> >> https://lists.ipfire.org/development/20250908125938.3389609-1-adolf.belka@ipfire.org/T/#t >> >> have not been merged yet. Have they just been missed or is there a question about them? >> >> Regards, >> >> Adolf. >> >>> Regards, >>> Adolf. >>>> >>>> Evaluated the change in my vm and the rw graphs worked again. >>>> >>>> Regards, >>>> >>>> Adolf. > >