Network setup

Why networking is mandatory

The ISO carries only the installer — there's no prebuilt base image on the disk. Your entire system (toolchain, kernel, init, libc, filesystem tooling, tools) is fetched from the network and compiled during installation. So the installer treats a connection as a hard gate: no network, no install. It won't pretend otherwise.

The flow, exactly

1. Probe. The installer checks connectivity against several hosts (1.1.1.1, github.com) using ping, falling back to a TCP connect via nc if needed.
2. If connected: a simple [ keru ] network: connected and it moves straight to crafting your system.
3. If not connected: you're told, and asked — Connect to the network now (runs nmtui)? [Y/n].
4. Say yes: nmtui opens. Connect to your network, press okay.
5. Saying no: the installer exits with a network connection is required to install Keru.
6. Re-check. After nmtui closes, connectivity is probed again. If you're online, you continue. If not, it asks again — it never fakes success.

[ keru ] warning: network: not connected
Connect to the network now (runs nmtui)? [Y/n] y
(nmtui opens — pick your network, connect, press ok)
[ keru ] network: connected

Details that matter

• Wired is the path of least resistance. A physical Ethernet connection with DHCP typically just works — the probe succeeds and you skip straight to choosing.
• Wireless goes through nmtui. The NetworkManager TUI handles Wi-Fi selection, WPA credentials, and the rest. The installer doesn't guess; it hands you the tool.
• Loop, don't lie. If you run nmtui but never connect, the installer loops back to the prompt rather than proceeding on a "trust me, it worked" basis.

Walkthrough · Requirements