Dimitri Papadopoulos Orfanos

What did you try exactly? What do you mean by "does not work"? Which version of MacOS and openfortivpn? Because openfortivpn currently lacks the code to properly set the DNS...

I have no clue what GL.iNet is, but I think it is irrelevant here because it is just a piece of hardware hardware running OpenWrt. To answer your question, openfortivpn...

Please run openfortivpn from the command line if you want help, not as a daemon. https://github.com/adrienverge/openfortivpn/wiki#reporting-issues

I must admit didn't have the time to read everything. However: * If using NetworkManager, you'll have to raise issues: https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn * Indeed NetworkManager handles routing and DNS changes itself...

I suspect is a FortiOS version issue rather than a FortiGate device type issue. We have tested FortiOS 6.2 and it works for us but I'm not certain we have...

I may be wrong, but it seems to me this can be achieved outside openfortivpn. Does this need to be implemented inside openfortivpn?

Another problem might be this new FortiGate implements hostchecks (#713).

> On this page a client for Linux can be downloaded: https://www.forticlient.com/downloads (For Debian/Ubuntu based systems https://filestore.fortinet.com/forticlient/downloads/FortiClientFullVPNInstaller_6.4.0.0851.deb). That's interesting. This page has been changed recently and the Linux VPN SSL...

> I can connect from Windows and my colleagues using MacOS can also connect. In version 6.4, Windows and macOS both support IPSec VPN, the Linux version supports only SSL...

> I think we haven't tested against FortiOS 6.4.The FortiOS Version is contained in the xml output which openfortivpn shows in `-v -v` verbose mode. Unfortunately it looks like _openfortivpn_...