Network configuration tools compared: nmcli, netplan, systemd-networkd and their Windows and macOS equivalents

What it is

Task	NetworkManager (nmcli)	Ubuntu netplan	systemd-networkd	ifupdown	Windows	macOS	FreeBSD
Read current config	nmcli connection show NAME	inspect the YAML under /etc/netplan/, or netplan get	networkctl status IFACE	read /etc/network/interfaces	Get-NetIPConfiguration	networksetup -getinfo "Wi-Fi" (or the relevant service name)	read /etc/rc.conf's ifconfig_IFACE lines
Set a static address	nmcli connection modify NAME ipv4.addresses 192.0.2.10/24 ipv4.gateway 192.0.2.1 ipv4.method manual, then nmcli connection up NAME to apply	edit the YAML (addresses: under the interface, dhcp4: false), then netplan apply	edit a .network file's [Network]/[Address] sections, then networkctl reload (systemd 244 and later) or restart systemd-networkd	edit the iface IFACE inet static block in /etc/network/interfaces; applied by ifdown/ifup of that interface	New-NetIPAddress -InterfaceAlias NAME -IPAddress 192.0.2.10 -PrefixLength 24 -DefaultGateway 192.0.2.1 (takes effect immediately)	networksetup -setmanual "Wi-Fi" 192.0.2.10 255.255.255.0 192.0.2.1	sysrc ifconfig_IFACE="inet 192.0.2.10 netmask 255.255.255.0", then service netif restart IFACE
Set DNS servers	nmcli connection modify NAME ipv4.dns "1.1.1.1 9.9.9.9" (add ipv4.ignore-auto-dns yes to drop DHCP-supplied servers)	add nameservers: {addresses: [...]} to the YAML	set DNS= in the .network file's [Network] section	add a dns-nameservers line to the interface stanza (needs the resolvconf package)	Set-DnsClientServerAddress -InterfaceAlias NAME -ServerAddresses 1.1.1.1,9.9.9.9	networksetup -setdnsservers "Wi-Fi" 1.1.1.1 9.9.9.9	set resolv.conf directly, or via DHCP client configuration

Why it matters

Two mistakes recur across all of these: forgetting to apply a staged change (netplan apply, nmcli connection up, networkctl reload), and applying a change over the very connection used to reach the host, cutting the session before the command finishes. A YAML or config-file-based tool (netplan, ifupdown, FreeBSD's rc.conf, systemd-networkd) also has a syntax-validity gap that nmcli and the PowerShell cmdlets do not: a malformed file may not error until the service tries to reload it, sometimes at the next boot.

How to apply

• On netplan, run netplan try before netplan apply; it reverts automatically unless confirmed within 120 seconds, protecting against a lockout. The Linux, FreeBSD and Windows commands need root or an elevated shell, and networksetup changes need admin rights.
• On any file-based tool, keep a copy of the working configuration before editing, and validate syntax (where a validator exists, e.g. netplan generate for a dry parse) before applying.
• Confirm a change from the running state (ip addr, resolvectl status, ifconfig, Get-NetIPConfiguration), not by re-reading the file you edited.
• Change one property at a time (address, then DNS), especially on hosts reached only over the network you are reconfiguring.

Pitfalls

• Editing /etc/network/interfaces on Ubuntu 17.10 or later, which uses netplan; unless ifupdown was installed deliberately, the file is ignored and the change has no effect.
• Setting a static address with nmcli without also setting ipv4.method manual; with the method left at auto, DHCP keeps running and the static address is only added next to the leased one.
• Assuming Set-DnsClientServerAddress changes name resolution globally; it is per interface, so other adapters (VPN, second NIC) keep their own servers. Check with Get-DnsClientServerAddress; -ResetServerAddresses returns to DHCP-supplied servers.