-
-
Save SydoxX/f40a9d4d7af414049b6e07092e8bbc2b to your computer and use it in GitHub Desktop.
#!/bin/bash | |
# version 2 thanks to @dhx-mike-palandra | |
echo "Creating /etc/NetworkManager/conf.d/99-forticlient.conf..." | |
sudo cat > /etc/NetworkManager/conf.d/99-forticlient.conf << 'EOF' | |
[keyfile] | |
unmanaged-devices=interface-name:~vpn*,type:tun | |
EOF | |
if [ $? -eq 0 ] | |
then | |
echo "Successfully created config file. VPN connection should work now." | |
else | |
echo "Failed to create config file! Try running this script with root permissions." | |
fi |
Thanks!
Works excellent! So useful!
(Maybe it's necessary to reboot the system)
Can you update the script to request the user to reboot
, or restart NetworkManager?
sudo systemctl restart NetworkManager.service
Also, I'm curious, why does your hackish script work? As far as I can tell, it tells NetworkManager to treat 'vpn' interfaces and 'tun' devices as unmanaged, but I don't understand how NetworkManager can interfere with FortiClient
Can you update the script to request the user to
reboot
, or restart NetworkManager?
sudo systemctl restart NetworkManager.service
Also, I'm curious, why does your hackish script work? As far as I can tell, it tells NetworkManager to treat 'vpn' interfaces and 'tun' devices as unmanaged, but I don't understand how NetworkManager can interfere with FortiClient
Thank you guys!, you save my day!!
Guys, there is a checkbox regarding "invalid certificates" in Options, and a drop-down list too. .)
Friends, the script works for me in PepperMintOS and FortiClient 7.0.7. Thanks a lot
Life saver, worksss
using forticlientvpn 7.0.7.0246
worked after running script and restartinng NetworkManager :)
./forti-fix.sh
systemctl restart NetworkManager
Works for opensuse
Forticlientvpn 7.0.7.0246
Debian 12
worked after
./forti-fix.sh
systemctl restart NetworkManager
reboot
Thans guys, the script works for me With
./forti-fix.sh
systemctl restart NetworkManager
in LMDE 6 (Faye - Debian 12.1 ) and FortiClient 7.0.7.0246 Thanks a lot
This sorted my issues on Fedora 38.
I use an OpenConnect VPN as well and the original configuration line did cause problems with that. To tighten up the NetworkManager match, you may want to change the line to:
unmanaged-devices=interface-name:~vpn00*,type:tun
This assumes that Fortinet creates all its interfaces starting with vpn00
for you like it does on my device. This way it won't affect VPNs created with OpenConnect which are usually vpn0
, vpn1
, etc.
Any luck with Fedora 39?
Hi all, if you are facing issues with Forti's own client, I can recommend openfortivpn
Hi all, if you are facing issues with Forti's own client, I can recommend
openfortivpn
Unfortunately, I need the SAML Login which upon my knowledge is not supported by openfortivpn.
You can try openfortivpn-webview
. openfortivpn
has a link to SAML in their README
Thanks! Ubuntu 23.10 works!
Dosen't work on ubuntu 23.10 / FortiClient VPN 7.2.2.0753 :(
Works on kali 2023.4 . Thank you very much !
The script worked perfectly with FortiClient VPN 7.0.7.0246 but it does not work with version 7.2.2.0753. My OS is Debian 12.
ubuntu 24, forticlient 7.0.0.0018, reboot was needed
thanks!
ubuntu 24, forticlient 7.0.0.0018, reboot was not needed.
Thank you!! you save my day
Reboot was needed. My hero, thanks!
Hi,
Thanks for the script work perfectly
But i can't aceess to my lan network