Re: Testing of openvpn-2.6-meetup branch

[Adolf Belka <adolf.belka@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 4516 bytes --]

Hi Michael,

I did a fresh new clone of the openvpn-2.6-meetup branch and built it with only uncommenting the Compress/Raw/Zlib.pm

I then installed it onto a vm and tested it out. The same issues are present as before so it is not a problem of the repo clone that I had.

Basically the OpenVPN RW server can be started and using the openvpnctrl program the status says it is running and shows the pid but the WUI still says that it is Stopped.

Also any client connection creation shows up with Invalid input, even with client connections that work with CU189.

Regards,

Adolf.

On 06/12/2024 12:59, Adolf Belka wrote:
> 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
>