From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4bVR1D0k5nz331x for ; Sun, 29 Jun 2025 10:51:28 +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 "R10" (verified OK)) by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4bVR183khwz2xGG for ; Sun, 29 Jun 2025 10:51:24 +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 4bVR173lRszdN for ; Sun, 29 Jun 2025 10:51:23 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1751194283; 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=Km49oyifzZGCEubbaDJRv/GGAaVtMp+LLNXC0zgkYNc=; b=WeVn7DpF3DOIG7z1lVWfY6KkLiLM1IW9zgQL20w7xxGgn6RSmpl9Tx/ePLfTC1kprWVbJh 8E1MT0OE/LqZhOCQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1751194283; 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=Km49oyifzZGCEubbaDJRv/GGAaVtMp+LLNXC0zgkYNc=; b=TWzU3rlrz/cGYLgxrEnlTniJXocDM8P5h7TMqSxTsQiCgUG0bhSdGPaYt7M/+uXY58EY0a VU2iMKkDWgNzgeTj2PycGMorIoalAKlO/XbEDiM+fHaE0G046gh5MnHvmxWlvNc3Psb5YL SFlYJLWun1Sa9TtLSPBKsOKoDN3EVBZITJCtJY5HhLlNwHvi2c8z/A/dyDB4kUudS2P+Sx 1cng5Vmo/cjEXcJ24S0za9iETgtAvcWm+Ob6ZNJnmjxi3Ov5dKu4fekzSBfXeWo/BVXD2P Xv+vmrOAZG9fWi3HWSQiLYJPslJ/Xmqjcbv078+YnLBQLd+zFyEhaTaxU23NDA== Message-ID: Date: Sun, 29 Jun 2025 12:51:19 +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: Feedback on the branch openvpn-rebase Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi All, Tested out the latest openvpn-rebase branch from @ms using the link to the iso that he provided from the latest fixes. The disable and enable checkbox now works. If you enable the checkbox and save then the box is enabled and if you then disable and save it the checkbox now is disabled so that previous issue is fixed. Unfortunately the start and stop issue is still present. When I start the system running with the openvpn server running and then I disable the server then it shows the server as stopped. If I then enable the server and save then the checkbox is enabled but the server stays stopped. On the command line the status shows /usr/sbin/openvpn is not running but /var/run/openvpn-rw.pid exists. So the server stopped but the pid was not removed. If I boot the system and the server was checked as enabled then everything starts properly. The boot screen shows Starting OpenVPN Roadwarrior Server... OK Starting OpenVPN Authenticator... OK Starting OpenVPN N2N connection 'ipfirenet2net'... OK then if I straight away reboot the shutdown screen shows Stopping OpenVPN Authenticator... Not running WARN Stopping OpenVPN Roadwarrior Server... FAIL Stopping OpenVPN N2N connection 'ipfirenet2net'... OK The N2N connection starts and stops correctly and the pid is removed. I believe that this might be due to the variable PIDFILE being used for both the authenticator and the rw daemons and when the openvpn-rw daemon is being shutdown it has the authenticator pid in the PIDFILE variable and not the openvpn-rw.pid file name. I have tried various ways to change this in the openvpn-rw initscript but I ended up fixing it for one thing but then creating a problem for another one. Basically I think because I don't understand how the whole initscript and pid process is running in IPFire. Regards, Adolf.