NixOS Networking - Public Room Timeline

	NixOS Networking	876 Members
	Declaratively manage your switching, routing, wireless, tunneling and more. \| Don't rely on `networking.*` for interface and routing setup, use systemd-networkd, ifstate or NetworkManager instead. \| Set `SYSTEMD_LOG_LEVEL=debug` to debug networking issues with networkd \| No bad nft puns, please. \| Room recommendations: #sysops:nixos.org	256 Servers

Sender	Message	Time
28 Jul 2025
magic_rb	I personally gave up, i put k3s (containerd) into a separate network namespace and do the firewalling on the outside	13:39:17
@marcel:envs.net	Ifstate is not in the release phase for V2 so I am preparing to upstream the nix module to nixpkgs. The question is if the options should be under networking.ifstate or services.ifstate or somewhere different? That's hot it's currently done in my flake: https://search.nüschtos.de/?scope=IfState.nix	16:01:33
@marcel:envs.net	*	16:01:58
@marcel:envs.net	*	16:02:08
@marcel:envs.net	*	16:02:33
@marcel:envs.net	* Ifstate is now in the release candidate phase for V2 so I am preparing to upstream the nix module to nixpkgs. The question is if the options should be under networking.ifstate or services.ifstate or somewhere different? That's how it's currently done in my flake: https://search.nüschtos.de/?scope=IfState.nix Services.ifstate might not be optimal because it's not a daemon and only runs on boot or rebuild	16:03:46
adamcstephens	`networking.ifstate` seems reasonable to me	16:06:06