Package Details: forticlient-vpn 7.4.0.1636-2

Git Clone URL: https://aur.archlinux.org/forticlient-vpn.git (read-only, click to copy)
Package Base: forticlient-vpn
Description: Build through the official package of FortiClient VPN only
Upstream URL: https://www.fortinet.com/support/product-downloads
Keywords: FortiClient Fortinet VPN
Licenses: custom:fortinet
Conflicts: forticlient
Provides: FortiClient, fortivpn
Submitter: douglasimcabral
Maintainer: Meowser
Last Packager: Meowser
Votes: 15
Popularity: 0.001942
First Submitted: 2020-09-05 13:48 (UTC)
Last Updated: 2024-07-31 20:51 (UTC)

Dependencies (21)

Required by (0)

Sources (1)

Pinned Comments

douglasimcabral commented on 2022-11-10 15:37 (UTC) (edited on 2023-03-10 00:41 (UTC) by douglasimcabral)

Community,

The Fortinet provides two products, "FortiClient EMS" and "FortiClient VPN only". This package only correspond to "FortiClient VPN only" and your lastest version is 7.0.7.0246 at 03-09-2023.

If you are interested in "FortiClient EMS", I suggest following the AUR package 'forticlient' [https://aur.archlinux.org/packages/forticlient]

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

reeslo commented on 2024-11-30 16:05 (UTC) (edited on 2024-11-30 16:06 (UTC) by reeslo)

Hi there is an issue since last Manjaro upgrade 

nov. 30 17:04:08 manjaro NetworkManager[1421]: <info>  [1732982648.5856] vpn[xxx,"Forti VPN"]: starting fortisslvpn
nov. 30 17:04:08 manjaro NetworkManager[1421]: <info>  [1732982648.5863] audit: op="connection-activate" uuid="xxx" name="Forti VPN" pid=2715 uid=1000 result="success"
nov. 30 17:04:08 manjaro NetworkManager[8005]: INFO:   Connected to gateway.
nov. 30 17:04:08 manjaro NetworkManager[8005]: INFO:   Authenticated.
nov. 30 17:04:09 manjaro NetworkManager[8005]: INFO:   Remote gateway has allocated a VPN.
nov. 30 17:04:09 manjaro NetworkManager[8021]: /usr/bin/pppd: Plugin /usr/lib/pppd/2.5.0/nm-fortisslvpn-pppd-plugin.so is for pppd version 2.5.0, this is 2.5.1
nov. 30 17:04:09 manjaro pppd[8021]: Plugin /usr/lib/pppd/2.5.0/nm-fortisslvpn-pppd-plugin.so is for pppd version 2.5.0, this is 2.5.1
nov. 30 17:04:09 manjaro NetworkManager[8005]: ERROR:  read: Input/output error
nov. 30 17:04:09 manjaro NetworkManager[8005]: INFO:   Cancelling threads...
nov. 30 17:04:09 manjaro NetworkManager[8005]: INFO:   Cleanup, joining threads...
nov. 30 17:04:09 manjaro NetworkManager[8005]: ERROR:  pppd: An error was detected in processing the options given, such as two mutually exclusive options being used.
nov. 30 17:04:09 manjaro NetworkManager[8005]: INFO:   Terminated pppd.
nov. 30 17:04:09 manjaro NetworkManager[8005]: INFO:   Closed connection to gateway.
nov. 30 17:04:09 manjaro NetworkManager[8005]: INFO:   Logged out.
nov. 30 17:04:09 manjaro NetworkManager[1421]: <warn>  [1732982649.5099] vpn[yyy,xxx,"Forti VPN"]: dbus: failure: connect-failed (1)
nov. 30 17:04:09 manjaro NetworkManager[1421]: <warn>  [1732982649.5099] vpn[yyy,xxx,"Forti VPN"]: dbus: failure: connect-failed (1)

kristo commented on 2024-11-12 13:54 (UTC)

Thanks for sharing the scripts @Meowser, it will work as a temporary solution, but I hope it gets fixed in the main repo as well :)

Meowser commented on 2024-11-12 13:40 (UTC)

@kristo I had the same issue and someone at my work came up with a solution to modify the resolv.conf. I ended up with this script using inotifywait, whenever the file is changed this will fix the bad name.

#!/bin/sh

if [[ $EUID -ne 0 ]]; then
   echo "This script must be run as root"
   exit 1
fi

inotifywait --monitor --event create --include 'resolv.conf' /etc |
while read file; do
    if grep -q example.com /etc/resolv.conf
      then
        sed 's/comname/com|name/g' /etc/resolv.conf | tr '|' '\n' > /tmp/resolv.conf.new
        cp /tmp/resolv.conf.new /etc/resolv.conf
    fi
done

I run it with a systemd job at network startup:

# /etc/systemd/system/forticlient-fixer.service
[Unit]
Wants=network-online.target
After=network-online.target

[Service]
ExecStart=/root/bin/monitor-resolv.sh

[Install]
WantedBy=multi-user.target

kristo commented on 2024-11-12 13:24 (UTC) (edited on 2024-11-12 13:25 (UTC) by kristo)

I have an issue where the dynamic resolv.conf file does not get created correctly if a dns-suffix is provided in SSL-VPN configuration in FortiGate.

forticlient package version: FortiClient Version: 7.4.0.1636

It creates the resolv.conf file like this:

Dynamic resolv.conf(5) file for glibc resolver(3) generated by forticlient
The original resolv.conf is backed up as /etc/resolv.conf.forticlient.backup, and will be restored after VPN disconnects.

search example.comnameserver 10.10.10.53

beli3ver commented on 2024-09-16 03:56 (UTC) (edited on 2024-09-16 03:56 (UTC) by beli3ver)

Somebody else gets this error:

Notification: Create VPN network interface failed

LynXDT commented on 2024-08-31 06:26 (UTC)

Was not working upon install on KDE - stuck on connecting forever. Fixed by installing libgnome-keyring, do not know how to edit PKGBUILDS, moreover not familiar with uploading them here, so maybe someone can add this as a dependancy?

mcmann commented on 2024-08-20 19:43 (UTC)

The only issue I've been having with this package is actual VPN connection. I am able to send data but I cannot receive data; tunnels are not being successfully opened. This is with ipv6 being temporarily disabled for the sake of testing.

amos commented on 2024-08-15 13:09 (UTC)

With version 7.4.0.1636 (and not with 7.0.7.0246) I get the following error:

Failed to create instance lock file [2]

anyone know something?

Meowser commented on 2024-07-31 20:55 (UTC)

I pushed an updated with some of the dependency changes listed in previous comments by sshijacker. I had removed some of these in a previous build because they were flagged as unnecessary

ruaeci commented on 2024-07-30 16:34 (UTC)

On all versions of 7.x I get the following error:

vpn_connection:1231 Create VPN network interface failed

Haven't been able to determine why. I can use openfortivpn without issue. Anyone else find a remedy for this problem?

1 2 3 4 5 6 .. 9 Next › Last »