Also, the standard warning; please be very careful with how you use ChatGPT with technical subjects. It will at some point straight up lie to you and either tell you about things that don’t exist, or worse, give you incomplete advise and open you up to troubleshooting headaches or security vulnerabilities.
You can get IPSEC working 100% even with native win/mac/ios/android vpn capabilities. (yes, there might be some caveats due to some mysterious outdated OS versions but overall it is doable).
As with sslvpn, I’ve seen guys was able to connect (and even use saml 2fa) with linux using openvpn, but I haven’t done it myself.
I have a IKEv2 dial up implementation which is working great for OS interoperability using the native clients on each operating system (MAC, Windows and Linux). As far as I’m aware, the SSL VPN implementation requires FortiClient.
I just got working IPSEC VPN with MacOS native VPN client and Windows. But when I connect with VPN, I don’t have internet access. Is this a normal scenario with a VPN?
A lot of people have had issues with FortiClient, or just have a distrust of the FortiClient software in general, so when they set up IPSEC remote access on the FortiGate instead of SSL-VPN then they go the extra mile and use an alternative VPN client as well. This is typically just the built-in windows client, though could be any.
I wouldn’t be surprised if the IPSEC functionality of FortiClient is fine, it’s just the poor reputation of FortiClient.