On Tue, 5 Jul 2022 22:59:14 -0400, Nathan Stratton Treadway <natha...@ontko.com> wrote:
>On Tue, Jul 05, 2022 at 14:40:31 +0200, Bo Berglund wrote: >> Hopefully I can get there and upgrade it on location come September. >> I don't dare doing that remotely. > >Agreed. > >> Here you go: >> >> $ apt-cache policy openvpn >> openvpn: >> Installed: 2.4.7-xenial0 >> Candidate: 2.4.7-xenial0 >> Version table: >> *** 2.4.7-xenial0 100 >> 100 /var/lib/dpkg/status >> 2.4.4-2ubuntu1.7 500 >> 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 >> Packages >> 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 >> Packages >> 2.4.4-2ubuntu1 500 >> 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > >Yeah, this confirms that the system sees openvpn 2.4.4 out in the Ubuntu >Bionic archives but currently has the 2.4.7-xenial0 (i.e. from >build.openvpn.net) package installed. > >If you can log in to that server directly (i.e. not over the OpenVPN >link), In fact when I set up the VPN server I also put a RaspberryPi device with OpenVPN server installed as a "back door" so I could reach the system even if the main OVPN server (wich is in a VMWare ESX) should go down. It should still be operational so I can get onto the LAN that way. But I have not used it much, except when the power was lost on the VMWare server. Upon testing now it seems like it does not connect, though... But when I log on to that RPi server I see this for the startup service: $ sudo systemctl status openvpn ? openvpn.service - OpenVPN service Loaded: loaded (/lib/systemd/system/openvpn.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2022-07-06 11:16:02 CDT; 11s ago Process: 27735 ExecStart=/bin/true (code=exited, status=0/SUCCESS) Main PID: 27735 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/openvpn.service And for the local only service: $ sudo systemctl status openvpn@serverlocal.service ? openvpn@serverlocal.service - OpenVPN connection to serverlocal Loaded: loaded (/lib/systemd/system/openvpn@.service; disabled; vendor preset: enabled) Active: active (running) since Wed 2022-07-06 11:16:05 CDT; 3min 49s ago Docs: man:openvpn(8) https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage https://community.openvpn.net/openvpn/wiki/HOWTO Process: 27751 ExecStart=/usr/sbin/openvpn --daemon ovpn-serverlocal --status /run/openvpn/serverlocal.status 10 --cd /etc/openvpn --config /etc/openvpn/serverlocal.conf --writepid /run/openvpn/serverlocal.pid (code=exited, s Main PID: 27756 (openvpn) Tasks: 1 (limit: 4915) CGroup: /system.slice/system-openvpn.slice/openvpn@serverlocal.service +-27756 /usr/sbin/openvpn --daemon ovpn-serverlocal --status /run/openvpn/serverlocal.status 10 --cd /etc/openvpn --config /etc/openvpn/serverlocal.conf --writepid /run/openvpn/serverlocal.pid So the service I need is running on that RPi, but when I try using it it fails. "Someone" must have messed with port forwarding on the router. :( Sigh... Now I have to go into the Fortigate firewall router and re-enable the VPN forwarding. >then you should be safe using the "apt install" commands to force >installation of the 2.4.4-2ubuntu1.7 package and then try bringing up >the link to see if 2.4.4 works in that environment (with the plan to >switch back to the build.openvpn.net packages if it doesn't...) > >Alternately, you can follow the notes in the OpenVPN community wiki page >to re-enable the build.openvpn.net repository, presumably using a >"...debian/openvpn/2.4 bionic main" line. > >(Looks like if you do that, you'll be offered openvpn 2.4.11_bionic0 as >the available version to upgrade to...) > I will check if I van get the "back door" operational and then try this. -- Bo Berglund Developer in Sweden _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
