NixOS Networking - Public Room Timeline

	NixOS Networking	884 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	253 Servers

Sender	Message	Time
28 Jul 2025
Marcel	yeah	19:17:21
Marcel	allrigh	19:17:23
Marcel	shoult the initrd options then be unser boot.initrd.network.ifstate?	19:17:43
Sandro 🐧	that's what we are doing in the hackspace. Marcel knows that part, too.	19:19:42
emily	I'm not totally sure as it is possible (but not guaranteed) that we will deprecate that hierarchy. I'd say `boot.initrd.network.ifstate` or `boot.initrd.ifstate` are both fine	19:19:46
emily	ideally `boot.initrd` would mirror the top level hierarchy	19:20:04
emily	but alas :)	19:20:07
Marcel	so boot.initrd.networking? ;D	19:20:22
emily	yeah, but it's probably too confusing to do that	19:20:37
Marcel	yeah unserstand that	19:20:42
Marcel	i'll use networking	19:20:49
Marcel	*	19:20:54
Marcel	I've build an assertion like this: `IfState and networking.useDHCP cannot be used at the same time, as both configure the network. Please look into IfState hooks to integrate DHCP: https://codeberg.org/liske/ifstate/issues/111` The problem is that useDHCP is per default set to true. That means that every user first using ifstate gets this error, is this bad? Should ifstate set useDHCP to false?	20:25:45
hexa (clat on linux when)	please bring ifstate upstream	20:27:00
hexa (clat on linux when)	it's one more thing we can point people to, to escape scripted networking	20:27:10