From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Testing of openvpn-2.6-meetup branch
Date: Fri, 06 Dec 2024 12:59:53 +0100 [thread overview]
Message-ID: <4ee66855-d930-4924-a8a6-ca025188e3b0@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3768 bytes --]
Hi Michael,
So I did a pull of the openvpn-2.6-meetup branch from your repo. I noticed that it was using OpenVPN-2.6.9 and 2.6.12 is available now so I updated the openvpn to 2.6.12 and did a build.
Then I installed the created iso and the OpenVPN WUI page came up with an Internal Server Error.
The logs indicated that it couldn't find the Compress::Raw::Zlib perl module.
That was one of the separate perl modules removed from the system because they were now in the core.
I checked the perl rootfile on the openvpn-2.6.meetup branch and it had the
usr/lib/perl5/5.36.0/xxxMACHINExxx-linux-thread-multi/Compress/Raw/Zlib.pm line commented out.
So I uncommented that line in the rootfile and rebuilt the branch and now the OpenVPN WUI page was shown okay.
However when I tried to create a client connection I kept getting an "Oops something went wrong Invalid input" message but it didn't say what was invalid.
I then restored a backup with my existing OpenVPN root/host and client settings and using the pencil icon to go into edit mode for one of the known working client connections when I just pressed the Save button without changing anything it again gave me the Invalid input message.
The other issue I found was that the OpenVPN Server page was constantly showing Stopped.
At this point I did a rebuild of the openvpn-2.6-meetup branch with the previous 2.6.9 OpenVPN but the same as above occurred, again with a fresh client connection creation or with the restored known working client connections.
I then tried to start the openvpn from the command line to see what messages it cam up with.
I tried first of all using the restart command and got
/usr/local/bin/openvpnctrl rw restart
Stopping OpenVPN Authenticator... Not running. [ WARN ]
Stopping OpenVPN Roadwarrior Server... [ FAIL ]
Starting OpenVPN Roadwarrior Server...
Unable to continue: /var/run/openvpn-rw.pid exists [ WARN ]
Starting OpenVPN Authenticator... [ OK ]
so I checked and the openvpn-rw.pid file was present. So I then removed that file and ran the status command
/usr/local/bin/openvpnctrl rw status
/usr/sbin/openvpn is not running.
Then I ran the start command
/usr/local/bin/openvpnctrl rw start
Starting OpenVPN Roadwarrior Server... [ OK ]
Starting OpenVPN Authenticator... [ OK ]
So tried the status command again
/usr/local/bin/openvpnctrl rw status
openvpn is running with Process ID(s) 6883.
So good the server is running but when I looked at the OpenVPN WUI page it still showed Stopped, also on the Services page.
I then pressed the Save button on the OpenVPN WUI main page and then checked the status again and got
/usr/local/bin/openvpnctrl rw status
/usr/sbin/openvpn is not running but /var/run/openvpn-rw.pid exists.
So doing the save caused the server to stop but leave the pid in place.
So I am not sure what has changed between our meetup and what I am building now. As far as I can tell from the branch in the repo, nothing has changed since 23rd Sept.
Maybe how I have done the pull of the repo is incorrect in some way and I am ending up in some mixed up situation but as it stands I definitely cannot test anything.
I will try creating a complete new copy of that branch on my system to see if anything gets better but I am also open to any suggestions of what I might have done wrong.
Regards,
Adolf
next reply other threads:[~2024-12-06 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 11:59 Adolf Belka [this message]
2024-12-06 18:13 ` Adolf Belka
2024-12-06 20:11 ` Michael Tremer
2024-12-07 14:11 ` Adolf Belka
2024-12-07 14:23 ` Adolf Belka
2024-12-07 14:29 ` Adolf Belka
2024-12-07 14:48 ` Adolf Belka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ee66855-d930-4924-a8a6-ca025188e3b0@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox