FS#68891 - [networkmanager] reenable resolvconf support

Attached to Project: Arch Linux
Opened by nl6720 (nl6720) - Tuesday, 08 December 2020, 09:32 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 22 December 2020, 03:07 GMT
Task Type Feature Request
Category Packages: Testing
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
networkmanager 1.28.0-2 disabled resolvconf support with the reason that it does not work with systemd-resolvconf. But that can only happen if systemd-resolvconf is installed and NetworkManager cannot detect systemd-resolved, i.e. when /etc/resolv.conf is not symlinked to one of the recommended paths. If the symlink exists or if /etc/NetworkManager/conf.d/*.conf has main.dns=systemd-resolved, then resolvconf will not be used, this can be seen in the journal:

NetworkManager[384]: <info> [1607418846.0134] dns-mgr[0x55e8d490b220]: init: dns=systemd-resolved rc-manager=unmanaged (auto), plugin=systemd-resolved

If someone uses one of the more uncommon systemd-resolved's /etc/resolv.conf management modes that do not involve symlinking the file, then it should be reasonable to expect them to manually set main.dns=systemd-resolved in /etc/NetworkManager/conf.d/*.conf.
Please reenable resolvconf support so that the new "auto" mode of "rc-manager" properly falls back to resolvconf when systemd-resolved is not detected.

Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any
networkmanager 1.28.0-2

Steps to reproduce:
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Tuesday, 22 December 2020, 03:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.28.1dev+7
Comment by Antonio Rojas (arojas) - Monday, 14 December 2020, 16:41 GMT
It causes issues (as in no DNS) when you have systemd-resolvconf installed (simply because it provides resolvconf and you randomly chose it over the other provider) but resolved is not enabled.
Comment by nl6720 (nl6720) - Tuesday, 15 December 2020, 08:09 GMT
I don't think having systemd-resolvconf installed while not using systemd-resolved should be considered a supported use case. Other network management software that use resolvconf would have broken DNS resolution too.

Loading...