
On 12. 12. 22, 13:38, Jiri Slaby wrote:
On 12. 12. 22, 11:46, Thorsten Kukuk wrote:
The move from wicked to NetworkManager as default for everything during the last months revealed some (welcomed) side effects: since several weeks sysconfig-netconfig is no longer installed on a fresh default installation.
\o/ and thanks for the effort.
Last time (3 weeks ago) I uninstalled sysconfig-netconfig, the system (VM) didn't come up. I am using NM on all my systems. Let me retry.
Ah, so netconfig is apparently no longer called for some weeks. Good. So the system works and: rm -f /etc/resolv.conf systemctl restart NetworkManager was needed to fix the resolver. BTW is this OK from NM log? dns-mgr: init: dns=default,systemd-resolved rc-manager=netconfig (auto) -> rc-manager=netconfig, in particular
thanks,-- js suse labs