![fortinet vpn client linux fortinet vpn client linux](https://4.bp.blogspot.com/-E4CmeJrscqI/V-thx5JQRzI/AAAAAAAABZ4/qFliTcFrgi8MorkRcf-CP8QOJFsKk14EgCEw/s1600/Selection_015.png)
It seems that FortiGate is using a wrong value for this field, or at least one that isn't accepted by vpnc. So, after playing around with the VPN settings in the FortiGate UI I finally found that the problem is the " a->next->type = IKE_ATTRIB_LIFE_DURATION" part. Vpnc: vpnc.c:1194: lifetime_ike_process: Assertion `a->next->type = IKE_ATTRIB_LIFE_DURATION' failed. etc/resolvconf/update.d/libc: Warning: /etc/nf is not a symbolic link to /run/resolvconf/nf NAT status: this end behind NAT? YES - remote end behind NAT? no Or, when you've using the command line interface: SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/tun0, iface: tun0) Writing DNS information to /sbin/resolvconf
![fortinet vpn client linux fortinet vpn client linux](https://i1.wp.com/securityaffairs.co/wordpress/wp-content/uploads/2017/12/FortiClient-flaws.png)
Policy set 'FortiGate VPN' (tun0) as default for IPv4 routing and DNS. (11) failed to find interface name for index VPN connection 'FortiGate VPN' (IP Config Get) complete. Internal Point-to-Point Address: 172.20.1.1 VPN connection 'FortiGate VPN' (IP4 Config Get) reply received from old-style plugin. For example, when using NetworkManager, you might see something like this in syslog: This article might be relevant to you if you have problems connecting to a FortiGate IPSec VPN with Linux (vpnc). See my new article Connecto to Fortigate VPN with OpenfortiVPN. This article might not longer be relevant as a new opensource client called "openfortivpn" exists that utilized the SSLVPN feature of Fortigate instead of IPSec.