home / swappables / network tools
How your network gets managed. Your call.
The network stack has as many opinions attached as the init system. Keru applies the same rule: pick the manager you want, and it's built into your system — nothing wireless-by-default imposed, no "just use the standard one."
The default. Just NetworkManager's terminal user interface — connect wires and Wi-Fi without a full manager on your system.
The full NetworkManager — daemon, D-Bus API, nmcli, handles wired, wireless, VPN, and more.
Intel's connection manager — light, D-Bus bus–independent, designed for embedded and minimal systems.
systemd's network configuration daemon — declarative unit-based config, pairs with systemd/udev.
The default is nmtui — the interface, not the daemon — which is the lean choice: you get the easy nmtui workflow during install without committing yourself to running NetworkManager's daemon afterward. If you want the full manager, it's one selection away.
If you chose systemd as your init, systemd-networkd pairs naturally. If you're on runit or s6, a standalone manager (or just nmtui) fits the picture. The installer offers the pieces; you assemble them.
nmtui itself (the installer runs it when you need to connect) — independent of what you pick as your system's eventual network tool. The install-time network flow.