Dimitri Papadopoulos Orfanos

@msdobrescu You do **not** have a similar problem if openfortivpn works from the command line. Please create a ticket against the KDE Network Manager integration.

You could try [FortiClient](https://www.fortinet.com/support/product-downloads#vpn) in addition to openfortivpn and compare routing after starting either VPN. Possible issues: * openfortivpn does not have support for IPv6 (#112) * other routing issue...

Indeed, endpoint detection might be the issue here. Have you tried [FortiClient](https://www.fortinet.com/support/product-downloads#vpn)?

The Windows client relies on IPSec by default, while the Linux client is an SSL VPN. Perhaps VPN SSL is not enabled on that VPN server. > I was happy...

That's the code that emits the `DEBUG: Route not found` message, which looks suspect: ```c if (rtfound == 0) { // should not occur anymore unless there is no default...

@pkubaj Routing is handled differently on FreeBSD, so I doubt you experience the "same issue". Open a different ticket if needed.

@klaverjan Are you connecting from NetworkManager or directly from the command line by running openfortivpn?

As far as I know authentication is not implemented yet in proxy support code: ccaa359

We probably need [libproxy](https://github.com/libproxy/libproxy) for proper proxy support.

How do you come to the conclusion that openfortivpn does not exit/error even though pppd is terminated? I currently cannot see how it could happen. Perhaps openfortivpn exits with an...