Dimitri Papadopoulos Orfanos

I tried the above pandoc command and the result does have some issues. Do you think they can be fixed with pandoc options or changes to the man page? 

There are other issues as well. No need to have something perfect from scratch, but we will have to address these and other issues.

I think it's best to keep systemd-resolved and try to use `resolveconf` instead: * Make sure openfortivpn is built with resolveconf support. * Make sure resolveconf is available in the...

> Note that I also had to upgrade `openfortivpn` to the version 1.21.0 and add the option `--pppd-accept-remote=1`. > The version shipped by Fedora 39 is broken (because of the...

> @DimitriPapadopoulos , i confirm in a clean installation of Fedora 38 and Ubuntu 22.04 with systemd-resolved, the DNS received via VPN does not resolve private names. Basically I install...

Ah, that's interesting. Right now, I don't know whether it means that `openfortivpn` does not call `resolvconf` correctly, or that `resolvconf` doesn't do the right thing on Fedora with systemd-resolved....

> Specifically on Fedora 39. It worked flawlessly before I upgraded to this version a couple of days ago (using `NetworkManager-fortisslvpn`). I'll be glad to help you debugging. To make...

Yes, I did expect 1.21 to fix some if not all issues, because it adds the `ipcp-accept-remote` pppd option that is required by pppd ≥ 2.5.0 but breaks pppd <...

I see. There are two ways openfortivpn can modify DNS settings: 1. The traditional ugly way, by directly modifying `/etc/resolv.conf`, still works more or less on many Linux platforms but...

@madrisan It might be that `resolvconf` does not work as expected, or that we don't pass proper arguments to it. In the first case, there is not much we can...