Where Does innernet Store Network State on Linux?
innernet keeps server state under /etc/innernet, with clients joining via single use invitation files.
Last updated
innernet state lives with the coordination server under /etc/innernet per its docs flow. The init wizard (innernet-server new) creates the network there, peers join with add-peer, and each invite becomes a one time TOML file you hand to the new machine.
Clients redeem invites with innernet install, which generates fresh keys and registers them. Guard invitation files like passwords in transit. Exact file layout under /etc/innernet can shift between releases, so confirm against the installed version before scripting backups.
Where innernet stores this, by platform
/etc/innernet (server state per network)
Created by innernet-server new. Back it up with the server stopped or snapshotted. File details vary by release, so copy the whole tree, not single files.
User chosen path (invitation .toml files)
Single use peer invites from add-peer. Transfer securely, delete after redeem. A used invite cannot initialize a second peer.
Frequently asked questions
How do I back up an innernet network?
Snapshot /etc/innernet on the coordination server plus a note of interface names and versions. Peers rejoin from new invites if the server is rebuilt, so keep admin access working.
Where do innernet logs go?
Through the service manager: journalctl for the innernet-server@ unit on systemd hosts. Run serve in foreground once when debugging fresh installs.
Notice an outdated path? Let us know.