Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#69898 - [openfortivpn] use-resolvconf=1 does not work properly

Attached to Project: Community Packages
Opened by Radoslav Georgiev (maximaman) - Saturday, 06 March 2021, 21:39 GMT
Last edited by Maxime Gauduin (Alucryd) - Wednesday, 17 March 2021, 08:12 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



With the current build settings in the PKGBUILD (more specifically, the --enable-resolvconf configure flag), openfortivpn should try to use resolvconf(8) to add DNS servers to /etc/resolv.conf by default (even if the use-resolvconf=1 setting is not explicitly assigned either in the config file or on the command line). However, this does not happen exactly as described in the manual page: openfortivpn still uses the fallback mechanism for adding DNS servers (i.e. by directly writing to /etc/resolv.conf), even though this should not happen if the invocation of resolvconf(8) is successful. This has the effect of the DNS servers not being updated in the systemd-resolved(8) configuration on my machine.

Strangely enough, when I download the PKGBUILD and build the package myself, openfortivpn seems to invoke resolvconf(8) properly because the systemd-resolved(8) config gets updated immediately. Even more strange is my observation that resolvconf(8) is invoked in both cases (I checked using `sudo strace --follow-forks -e trace=execve openfortivpn`). It seems, however, that the invocation only succeeds when I'm using my build.

All of this suggests to me that the build currently in the repositories is somehow broken in this regard.

Additional info:
* package version(s):
* openfortivpn: 1.16.0-1

Steps to reproduce:
1. Install the openfortivpn package.
2. Setup a VPN configuration for openfortivpn.
3. Start openfortivpn (it does not matter whether --use-resolvconf=1 is passed as an argument).
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Wednesday, 17 March 2021, 08:12 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.16.0-2
Comment by Maxime Gauduin (Alucryd) - Wednesday, 17 March 2021, 08:12 GMT
Thanks for the heads up. It should be resolved 1.16.0-2, systemd was missing from the build chroot.