Könnte das sein, dass da ein "override" distributionsseitig (Bunsenlabs) stattfindet?gambit hat geschrieben: Den NetworkManger.service hatte ich aber nicht wieder aktiviert:Code: Alles auswählen
# systemctl status NetworkManager.service systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; disabled) Active: inactive (dead)
Ich bin über den link von habakug https://www.freedesktop.org/software/sy ... %20Options auf die Idee gekommen:
The .network files are read from the files located in the system network directory /usr/lib/systemd/network, the volatile runtime network directory /run/systemd/network and the local administration network directory /etc/systemd/network. All configuration files are collectively sorted and processed in lexical order, regardless of the directories in which they live. However, files with identical filenames replace each other. Files in /etc have the highest priority, files in /run take precedence over files with the same name in /usr/lib. This can be used to override a system-supplied configuration file with a local file if needed. As a special case, an empty file (file size 0) or symlink with the same name pointing to /dev/null disables the configuration file entirely (it is "masked").
