Sujet : networkmanager
-
Setting a static IPv4 address with nmcli without locking yourself out
nmcli can show, modify and activate NetworkManager connections from a script, but changing the address you are connected through can drop the session before the new settings apply. Cloning the profile first and validating before removing the old one keeps the change reversible.
-
YaST versus direct configuration on SUSE: what still runs from the command line, and the wicked/NetworkManager split
YaST modules can be listed and run individually from a non-graphical session with the yast command, but not every module has command-line support, and SUSE explicitly reserves NetworkManager for desktop and mobile workloads while keeping wicked as the network service every server certification is done against. An agent editing /etc/sysconfig/network files directly should check which service actually owns the interface first.
-
Network bonding and teaming with NetworkManager: modes, switch requirements and verification
Linux bonding combines several NICs into one logical interface, but the modes differ sharply in what the upstream switch must support: active-backup needs nothing special, 802.3ad/LACP needs a configured link aggregation group. /proc/net/bonding/<name> shows which mode is actually running and which slaves are up.
Lisible par machine : JSON