Dimitri Papadopoulos Orfanos

@peutch Thank you so much for spending the time (you and the maintainer) ironing things out on Debian. I must admit I am not happy with this breaking change I...

> Regarding your comment, this is still strange that the command line worked for me. Could then the option `--pppd-accept-remote=0` be somehow default? Do you perhaps have 2 versions of...

I understand openfortivpn without `--pppd-accept-remote` works fine. However, does it also work fine with both `--pppd-accept-remote=0` and `--pppd-accept-remote=1`? In the [build log you refer to](https://buildd.debian.org/status/fetch.php?pkg=openfortivpn&arch=amd64&ver=1.21.0-1&stamp=1700366564&raw=1) openfortivpn is configured without `--enable-legacy-pppd`:...

@epsilon77 Thank you for looking into this issue. One thing you may help with, is remind me whether NetworkManager-fortisslvpn handles routing internally, or delegates routing to pppd, like DNS. I...

Yes, when using _NetworkManager_, it's best to let _NetworkManager-fortisslvpn_ handle the VPN too. _NetworkManager-fortisslvpn_ will take over routing and DNS settings - _openfortivpn_ just handles the tunnel itself.

That said, we also need to update the Fedora packages to use _resolveconf_ again: https://bugzilla.redhat.com/show_bug.cgi?id=1777935#c29

And eventually we need to make _openfortivpn_ aware of _NetworkManager_ and _systemd-resolved_. However, I currently don't have the resources for that.