First let me say that I am aware that openvpn3 is not an official Fedora package; one must obtain it from a COPR repo. Therefore I could not file a bug against it in Fedora and in fact I don't know how I COULD file an official bug report, so I am just hoping that someone here has it working and could help.
I have had openvpn3 working since F35, including on a laptop that I originally installed openvpn3 on and it has been upgraded to F36 and now F37, and openvpn3 is working fine. However, on my new laptop with a fresh install of F37, I cannot get openvpn3 to work. The config manager seems to be OK, but the session manager is totally broken. First I import my config, and then:
[greg@ivanova ~]$ openvpn3 config-import --config /local/etc/OVPN.ovpn Configuration imported. Configuration path: /net/openvpn/v3/configuration/f75863b0x38dcx4ea5xa36ex35936d9cc4df [greg@ivanova ~]$ openvpn3 configs-list Configuration path Imported Last used Used Name Owner ------------------------------------------------------------------------------ /net/openvpn/v3/configuration/f75863b0x38dcx4ea5xa36ex35936d9cc4df Wed Mar 15 10:10:42 2023 0 /local/etc/OVPN.ovpn greg ------------------------------------------------------------------------------ [greg@ivanova ~]$ openvpn3 session-start --config-path !$ openvpn3 session-start --config-path /net/openvpn/v3/configuration/f75863b0x38dcx4ea5xa36ex35936d9cc4df ** ERROR ** Could not establish a connection with 'net.openvpn.v3.sessions' [greg@ivanova ~]$ openvpn3 sessions-list ** ERROR ** Could not establish a connection with 'net.openvpn.v3.sessions' [greg@ivanova ~]$
Any of the session commands result in the same error, after a noticeable delay.
Anybody else seen this or have openvpn3 working on a fresh install of F37?
Thanks, --Greg
On Wed, Mar 15, 2023 at 10:38 AM Greg Woods greg@gregandeva.net wrote:
I have had openvpn3 working since F35, including on a laptop that I originally installed openvpn3 on and it has been upgraded to F36 and now F37, and openvpn3 is working fine. However, on my new laptop with a fresh install of F37, I cannot get openvpn3 to work. The config manager seems to be OK, but the session manager is totally broken.
Made some progress with more careful examination of the systems where it works and where it doesn't, and it turns out that there is also an openvpn3-client package that has to be installed as well as openvpn3. This didn't occur to me because the openvpn3 client binary was installed. But when I installed openvpn3-client, the missing binary for the session manager was installed. So now I can get a little farther; I just need to figure out why user authentication is failing (I've tried it on the old system so I can verify I have the correct user name and password, and I have tried it enough times on the new system to rule out simple password typo as the cause). So now I can execute the session-start command, and it does prompt me for the username and password, but always returns authentication failure.
--Greg
I didn't change anything else, but now the authentication is working. I still don't know why it was failing consistently but now it works. The real issue was the need to install the openvpn3-client package.
--Greg
On Wed, Mar 15, 2023 at 1:38 PM Greg Woods greg@gregandeva.net wrote:
On Wed, Mar 15, 2023 at 10:38 AM Greg Woods greg@gregandeva.net wrote:
I have had openvpn3 working since F35, including on a laptop that I originally installed openvpn3 on and it has been upgraded to F36 and now F37, and openvpn3 is working fine. However, on my new laptop with a fresh install of F37, I cannot get openvpn3 to work. The config manager seems to be OK, but the session manager is totally broken.
Made some progress with more careful examination of the systems where it works and where it doesn't, and it turns out that there is also an openvpn3-client package that has to be installed as well as openvpn3. This didn't occur to me because the openvpn3 client binary was installed. But when I installed openvpn3-client, the missing binary for the session manager was installed. So now I can get a little farther; I just need to figure out why user authentication is failing (I've tried it on the old system so I can verify I have the correct user name and password, and I have tried it enough times on the new system to rule out simple password typo as the cause). So now I can execute the session-start command, and it does prompt me for the username and password, but always returns authentication failure.
--Greg
-
Greg Woods