Forticlient on Opensuse Tumbleweed

Hi,

What is the fortios and FCT version

What error you are getting in FGT VPN event logs

Hi! There is any Fortinet staff to help me to use Forticlient on Opensuse Tumbleweed. As the opening post, It worked previously, but just stopped after some system update and can't work even rolling back to system snapshots. Curiously, I updated my system last week and the client suddenly worked fine for a few days and then just stopped again even without any new update. As far as I know, it is not possible to use the fortisslvpn Network Manager plugin in my case since my provider requires a SAML login in a 365 account. This situation has been driving me crazy because I need to use this VPN in a daily basis (I've been working around via a VM jumpbox, but it drains my computer) My provider just answered that the client sent a RESET to the server. The following log is the excerpt that looks different from the day it worked:

20250129 22:30:51.318 TZ=-0300 [sslvpn:INFO] sslvpn:234 Authentication passed. 20250129 22:30:51.318 TZ=-0300 [sslvpn:INFO] vpn_connection:1944 /remote/fortisslvpn 20250129 22:30:54.393 TZ=-0300 [sslvpn:DEBG] vpn_connection:595 http request error: 1 20250129 22:30:54.393 TZ=-0300 [sslvpn:EROR] vpn_connection:552 socket error = Resource temporarily unavailable (11) 20250129 22:30:54.393 TZ=-0300 [sslvpn:EROR] vpn_connection:1815 Error: Can not connect to VPN server. 20250129 22:30:54.403 TZ=-0300 [sslvpn:DEBG] vpn_util:260 Get connection name: Wired connection 1 20250129 22:30:54.404 TZ=-0300 [sslvpn:DEBG] dns:203 Failed to open /etc/nm_resolv.forticlient.backup 20250129 22:30:54.410 TZ=-0300 [sslvpn:DEBG] vpn_util:260 List fctvpn connection: Wired connection 1 lo Neo's iPhone enp2s0 20250129 22:30:54.411 TZ=-0300 [sslvpn:DEBG] dns:632 default interface restore: 1, vpn interface restore: 1 20250129 22:30:54.411 TZ=-0300 [sslvpn:DEBG] mtu:116 Restore MTU. 20250129 22:30:54.411 TZ=-0300 [sslvpn:DEBG] mtu:120 No MTU backup file was found. Skip. 20250129 22:30:54.411 TZ=-0300 [sslvpn:DEBG] route:160 clean up route... 20250129 22:30:54.411 TZ=-0300 [sslvpn:DEBG] route:164 Cleanup file not found 20250129 22:30:54.411 TZ=-0300 [sslvpn:DEBG] main:1911 exception: Error: Can not connect to VPN server. 20250129 22:30:54.430 TZ=-0300 [sslvpn:INFO] main:1817 Init

Hi ,
TW user here , not a solution but some more debug output .

Once installed , the vpn client with SAML login option, cannot connect and add proper routes.
The connection aborts with the error message : Config routing table failed

Seems like some recent system updates have changed the behavior , prior to recent update , the vpn could connect but could not apply routes .

Now the connection is aborted.

here is a sniped of /var/log/forticlient/sslvpn.log

20250211 12:56:53.178 TZ=+0100 [sslvpn:DEBG] dns:710 Add DNS suffix: domain.local
20250211 12:56:53.178 TZ=+0100 [sslvpn:DEBG] dns:717 Add DNS suffix: domain.local
20250211 12:56:53.178 TZ=+0100 [sslvpn:DEBG] dns:723 Setup default interface
20250211 12:56:53.178 TZ=+0100 [sslvpn:DEBG] dns:729 Disable DHCP auto DNS
20250211 12:56:53.189 TZ=+0100 [sslvpn:DEBG] dns:744 Set IPv4 DNS servers: 10.xxx.xxx.40 10.144.150.41  
20250211 12:56:53.201 TZ=+0100 [sslvpn:DEBG] dns:759 Set IPv4 DNS search domains: domain.local  
20250211 12:56:53.213 TZ=+0100 [sslvpn:DEBG] dns:774 Re-apply settings.
20250211 12:56:53.224 TZ=+0100 [sslvpn:DEBG] dns:791 Setup VPN interface
20250211 12:56:53.224 TZ=+0100 [sslvpn:DEBG] dns:793 Set IPv4 DNS servers: 10.xxx.xxx.40 10.xxx.xxx.41  
20250211 12:56:53.344 TZ=+0100 [sslvpn:DEBG] dns:808 Set IPv4 DNS search domains: domain.local  
20250211 12:56:53.358 TZ=+0100 [sslvpn:DEBG] dns:823 Re-apply settings.
20250211 12:56:53.385 TZ=+0100 [sslvpn:DEBG] dns:182 Restart DNS service failed.
20250211 12:56:53.386 TZ=+0100 [sslvpn:DEBG] dns:192 Flush DNS cache failed.
20250211 12:56:53.387 TZ=+0100 [sslvpn:DEBG] route:102 route backup START
20250211 12:56:53.387 TZ=+0100 [sslvpn:DEBG] route:154 route backup DONE
20250211 12:56:53.387 TZ=+0100 [sslvpn:DEBG] route:396 begin route config
20250211 12:56:53.387 TZ=+0100 [sslvpn:DEBG] route:397 Remote IP: xxx.xxx.xxx.150
20250211 12:56:53.387 TZ=+0100 [sslvpn:DEBG] route:398 Local IP: 10.xxx.3.xx
20250211 12:56:53.387 TZ=+0100 [sslvpn:DEBG] route:399 Tunnel mode: Split tunnel
20250211 12:56:53.387 TZ=+0100 [sslvpn:DEBG] route:400 Exclusive routing: Disabled
20250211 12:56:53.387 TZ=+0100 [sslvpn:DEBG] route:474 Add the route for xxxx.xxx.xx.150(10.2xx.xx.254)
20250211 12:56:53.387 TZ=+0100 [sslvpn:DEBG] route:477 Failed to add route for xxx.xxx.x.150(10.2xx.xx.254)
20250211 12:56:53.387 TZ=+0100 [sslvpn:EROR] vpn_connection:1712 Config routing table failed
20250211 12:56:53.389 TZ=+0100 [sslvpn:DEBG] dns:210 Read DNS backup /etc/nm_resolv.forticlient.backup: [{"default_dev_name":"eth1","default_connection_name":"eth1","ignore_auto_dns":"no","system_dns_list":"","system_dns_search_domain_list":"","current_dns_list":
"192.xxx.xxx.40,192.xxx.xxx.41","vpn_dev_name":"fctvpn354ff353"}]
20250211 12:56:53.389 TZ=+0100 [sslvpn:DEBG] dns:547 Restoring DNS config 0:
20250211 12:56:53.389 TZ=+0100 [sslvpn:DEBG] dns:548 Device name: eth1
20250211 12:56:53.389 TZ=+0100 [sslvpn:DEBG] dns:549 Connection name: eth1
20250211 12:56:53.389 TZ=+0100 [sslvpn:DEBG] dns:550 Ignore auto DNS: no
20250211 12:56:53.389 TZ=+0100 [sslvpn:DEBG] dns:551 DNS list:  
20250211 12:56:53.389 TZ=+0100 [sslvpn:DEBG] dns:552 DNS search domain list:  
20250211 12:56:53.389 TZ=+0100 [sslvpn:DEBG] dns:553 VPN device name: fctvpn354ff353

Regards

I finally got the 7.4.2.1698 version by a friend that works for a partner, and it worked at first. The saddest part was getting a support deny from the official partner of my company. They just answered  since OpenSUSE wasn't supported, they can't provide any assistance.

Hi ,
it seems the new 7.4.3 , despite a conflicting install , still works after ignoring warning.
i managed to login through sso / saml and the routes were now propagated to my computer.
to be continued ...

sudo zypper install ./forticlient_vpn_7.4.3.1736_x86_64.rpm  Loading repository data... Reading installed packages... Resolving package dependencies...  Problem: 1: nothing provides 'libXext' needed by the to be installed forticlient-7.4.3.1736-1.el7.x86_64  Solution 1: do not install forticlient-7.4.3.1736-1.el7.x86_64  Solution 2: break forticlient-7.4.3.1736-1.el7.x86_64 by ignoring some of its dependencies  Choose from above solutions by number or cancel [1/2/c/d/?] (c): 2  Resolving dependencies... Resolving package dependencies...  The following NEW package is going to be installed:   forticlient  1 new package to install.  Package download size:   131.2 MiB  Package install size change:               |     434.8 MiB  required by packages that will be installed    434.8 MiB  |  -      0 B    released by packages that will be removed  Backend:  classic_rpmtrans Continue? [y/n/v/...? shows all options] (y): y Retrieving: forticlient-7.4.3.1736-1.el7.x86_64 (Plain RPM files cache)                                                               (1/1), 131.2 MiB     forticlient_vpn_7.4.3.1736_x86_64.rpm:     Package header is not signed!  forticlient-7.4.3.1736-1.el7.x86_64 (Plain RPM files cache): Signature verification failed [6-File is unsigned] Abort, retry, ignore? [a/r/i] (a): i  Checking for file conflicts: .......................................................................................................................[done] ===================================================================== If fortitray is not auto-started, try running /opt/forticlient/start-fortitray-launcher.sh as non-root. ===================================================================== gtk-update-icon-cache: Cache file created successfully. Created symlink '/etc/systemd/system/multi-user.target.wants/forticlient.service' -> '/usr/lib/systemd/system/forticlient.service'. (1/1) Installing: forticlient-7.4.3.1736-1.el7.x86_64 ..............................................................................................[done] Running post-transaction scripts ...................................................................................................................[done]