Package Details: networkmanager-fortisslvpn 1.4.0-6

Git Clone URL: https://aur.archlinux.org/networkmanager-fortisslvpn.git (read-only, click to copy)
Package Base: networkmanager-fortisslvpn
Description: NetworkManager VPN plugin for Fortinet SSLVPN
Upstream URL: https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn
Licenses: GPL-2.0-or-later
Submitter: heftig
Maintainer: supermario
Last Packager: supermario
Votes: 12
Popularity: 0.70
First Submitted: 2023-09-09 21:42 (UTC)
Last Updated: 2024-09-27 11:16 (UTC)

Dependencies (12)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

kuzyn commented on 2024-03-14 14:41 (UTC) (edited on 2024-03-14 14:41 (UTC) by kuzyn)

Anyone else is getting a conflict with the core/ppp package when updating this? (Been like that for at least 6 months.)

drws commented on 2024-02-07 18:00 (UTC)

Probably a better upstream URL: https://wiki.gnome.org/Projects/NetworkManager/VPN

uumas commented on 2023-12-14 15:09 (UTC)

Getting the following error when trying to connect:

NetworkManager[8481]: INFO:   Connected to gateway.
NetworkManager[8481]: INFO:   Authenticated.
NetworkManager[8481]: INFO:   Remote gateway has allocated a VPN.
NetworkManager[8482]: /usr/bin/pppd: /usr/lib/pppd/2.5.0/nm-fortisslvpn-pppd-plugin.so: undefined symbol: add_notifier
NetworkManager[8482]: /usr/bin/pppd: Couldn't load plugin /usr/lib/pppd/2.5.0/nm-fortisslvpn-pppd-plugin.so
pppd[8482]: /usr/lib/pppd/2.5.0/nm-fortisslvpn-pppd-plugin.so: undefined symbol: add_notifier
pppd[8482]: Couldn't load plugin /usr/lib/pppd/2.5.0/nm-fortisslvpn-pppd-plugin.so
NetworkManager[8481]: ERROR:  read: Input/output error
NetworkManager[8481]: INFO:   Cancelling threads...
NetworkManager[8481]: INFO:   Cleanup, joining threads...
NetworkManager[8481]: ERROR:  pppd: An error was detected in processing the options given, such as two mutually exclusive options being used.
NetworkManager[8481]: INFO:   Terminated pppd.
NetworkManager[8481]: INFO:   Closed connection to gateway.
NetworkManager[8481]: INFO:   Logged out.

Using openfortivpn cli directly works

qube222pl commented on 2023-09-27 13:05 (UTC)

It always adds the default route "default dev ppp0 scope link", even though it was added in the configuration [ipv4] ignore-auto-routes=true never-default=true route1=10.0.0.0/8 The previous version didn't do this

smart2128 commented on 2023-09-19 08:13 (UTC)

I also confirm that adding NAN-aurf's suggested flags fixes the issue. Thanks @NAN-aur

likan_blk commented on 2023-09-18 20:06 (UTC)

During building I'm getting an error: configure.ac:15: error: possibly undefined macro: dnl If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. I have automake 1.16.5-2.

guigqui commented on 2023-09-18 10:38 (UTC)

I have tryed NaN-aur's "pacth" and now the connection is working for me.

@NAN-aur, you're correct. Thanks for the fix.

NaN-aur commented on 2023-09-17 22:54 (UTC)

I got the plugin working on my system by patching it. First --pppd-accept-remote should be added to arguments of openfortivpn. Then a connection can be established, although routing doesn't work. Thus I removed the --no-routes argument of openfortivpn and it worked. I can't tell why it doesn't work with the --no-routes argument because the routes don't look wrong, though the routes aren't identical. I didn't spent too much time debugging this, but once the connection started working after some time and after changing the routes. I didn't spent much time on it because I wasn't able to reproduce it the second time I tried it. Maybe there is a race condition or a too early state transition in the plugin.

As workaround I added the following to the PKGBUILD: sed -i 's/"--no-routes"/"--pppd-accept-remote"/g' src/nm-fortisslvpn-service.c

@guigqui: Your observation is not related to the specific issue. Running pppd as root doesn't fix the issue. The only issue when running pppd as nobody is that the DNS server will never be updated (assuming a default installation without additional scripts).

guigqui commented on 2023-09-15 11:22 (UTC)

Like @Terseus commented, if you change de option in /etc/ppp/options the VPN works vía openfortivpn. Via networkmanager it looks like it works but it doesnt, i think that is beacause networkmanager plugin runs pppd as nobody user instead root.

P.D.: Sorry for my english

chindit commented on 2023-09-12 09:29 (UTC) (edited on 2023-09-12 09:29 (UTC) by chindit)

Waiting for the Peer refused to agree to his IP address bug to be resolve, you can directly connect from the terminal by launching sudo openfortivpn --pppd-accept-remote your.vpn.host -u your_username

Thanks @Terseus for the CLI flag ^^

« First ‹ Previous 1 2 3 4 Next › Last »