openfortivpn
openfortivpn copied to clipboard
adrienverge
Openfortivpn malfunctions with KDE Network Manager
Openfortivpn seems to connect, to create the routes, to add the DNS servers, but it can't access the services behind, there is no ping response, although the commercial version under Windows works for the same connection. Compared to the Windows version, it seems to generate the same setup. Also, it stays for some time connected, maybe 10-20 mins, then disconnects.
My system is a Gentoo-based distro, MocaccinoOS, we use openfortivpn 1.20.3. I've tested under KDE Plasma, where the Network Manager integration seems to be the cause, as the CLI version works fine. Although seems similar to https://github.com/adrienverge/openfortivpn/issues/1120, version 1.20.3 does not work for me either.
The OpenVPN client and works fine with the KDE Network Manager.
Please open a ticket against KDE Network Manager. It's probably (although never certainly) KDE Network Manager malfunctioning with openfortivpn, not the other way round.
The report is here: https://bugs.kde.org/show_bug.cgi?id=472491 They've read your devs comments and decided is not their issue! Tried under Gnome, there Network Manager does not claim it connects, it simply goes back to disconnected instantly.
I understand openfortivpn works for you from the command line, doesn't it? If so, how isn't this an issue with the GUI integration?
Well, this is what I try to figure out, actually. As you can see, KDE team denied it's their fault, so I'd appreciate if you reply to them on the matter, as you may know better how to prove it's their issue, as I incline too.
In my experience, KDE and Gnome integrations are suddenly broken, but I am a KDE user, Gnome being just a "witness". Also, openvpn interations work in both DEs. Maybe they've missed something when changed the implementations, although I wonder why would change this ignoring openfortivpn particular parametrization?
It's much more likely that the issue is with NetworkManager(-fortisslvpn), not Plasma's UI for it.
See https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/-/issues/63
I experience this issue too. The main difference I see with journalctl, is when using NetworkManager there are various "permission denied" errors, like trying to run ip-up and ip-down and trying to delete pid file /var/run/pppdppp0.pid. I run openfortivpn with sudo, and there is therefore no permissions issue.
What makes you think you're experiencing the "same issue", including the same causes? Only actual logs and actionable information are useful, "me too" posts don't help.
See Reporting issues.
Well what I'm experiencing matches what is described in the description, in particular that command line openfortivpn works but a connection via NetworkManager does not (though it used to). I thought perhaps the permission messages might offer a clue. Feel free to disregard, sorry.