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#65644 - [NetworkManager-fortisslvpn] Peer DNS Does not work with OpenFortiVPN 1.11

Attached to Project: Community Packages
Opened by Ruben Van Boxem (rubenvb) - Thursday, 27 February 2020, 20:14 GMT
Last edited by Maxime Gauduin (Alucryd) - Wednesday, 01 March 2023, 15:43 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


Quoting DimitriPapadopoulos (
"A known issue with NetworkManager-fortisslvpn is that it currently forces --no-dns which is a synonym for --set-dns=0. The default in versions of openfortivpn prior to 1.11.0 was --pppd-use-peerdns=1, resulting implicitly in:
--set-dns=0 --pppd-use-peerdns=1
The default starting with openfortivpn 1.11.0 is --pppd-use-peerdns=0, resulting implicitly in:
--set-dns=0 --pppd-use-peerdns=0
The result is that /etc/resolv.conf is not updated when using the current version of NetworkManager-fortisslvpn with openfortivpn 1.11.0 and later."
It would be great if the below linked patch could be applied to the Arch package to fix the compatibility issue between the two sides involved.

Additional info:
* networkmanager-fortisslvpn-1.4rc1-1
* Issue on the NetworkManager-fortisslvpn issue tracker:
* For a patch as applied in Fedora/Redhat:
* The Redhat issue is located here:
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Wednesday, 01 March 2023, 15:43 GMT
Reason for closing:  Upstream
Additional comments about closing:  Looks like it was fixed upstream.
Comment by Ruben Van Boxem (rubenvb) - Monday, 16 March 2020, 17:20 GMT
I created an AUR package that applies the peerdns patch: