4 ms·
Cockpit uses hostnamed, networkmanager, and other services for configuration, not 'ip' or 'hostname'. Everything you can see is persistent.
by evol262 9y ago
Cockpit uses hostnamed, networkmanager, and other services for configuration, not 'ip' or 'hostname'.
Everything you can see is persistent.
- sgeisler 9y agoThank you very much for clearing this up. Since I'm not familiar with networkmanager in combination with other config: what happens if I configure some network interface using Cockpit that is already defined in /etc/network/interfaces.d/*? Will it just throw an error or could it bring my system into a broken/undefined state so that it wouldn't be reachable after the next reboot? If the latter is the case it would probably be unwise to install/use Cockpit on an already configured system.
- evol262 9y agoNetworkManager handles the config file management on its own. Debian appears to require a flag to enable this on its own: https://wiki.debian.org/NetworkManager#Enabling_Interface_Management https://wiki.debian.org/NetworkManager#Enabling_Interface_Ma... If it's enabled, networkmanager will parse out the files and present them over dbus, nmcli, etc. Changes with nmcli, gnome-network (which also uses NM), or other tooling will update the config files. The same ones in /etc/network/interfaces.d/ So, hypothetically: auto eth0 iface eth0 inet static address 192.168.40.112 netmask 255.255.255.0 gateway 192.168.40.1 dns-nameservers 8.8.8.8 NM/Cockpit will show all of this information. If you change the address to 192.168.40.113, the config file will be updated (but otherwise unchanged), and the address will change on the running interface. If it's not enabled, Cockpit will not see the interfaces at all.