!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

893 Members
Declaratively manage your switching, routing, wireless, tunneling and more.261 Servers

Load older messages


SenderMessageTime
28 Jul 2025
@emilazy:matrix.orgemily (admittedly the boot.initrd.* hierarchy is a bit of a mess currently) 17:52:06
@marcel:envs.netMarcel
In reply to @emilazy:matrix.org
I would personally probably go for services.ifstate.* IMO, it's comparable to services.network-manager.* in that you have a systemd service managing the config, but I'm ambivalent
you are still with services.ifstate? in your last message you used networking.ifstate?
19:16:08
@emilazy:matrix.orgemily I have no consistent opinion 😅 NM is under networking.* right? 19:16:59
@emilazy:matrix.orgemilyI'd match NM19:17:01
@marcel:envs.netMarcelyeah19:17:21
@marcel:envs.netMarcelallrigh19:17:23
@marcel:envs.netMarcelshoult the initrd options then be unser boot.initrd.network.ifstate?19:17:43
@sandro:supersandro.deSandro 🐧that's what we are doing in the hackspace. Marcel knows that part, too.19:19:42
@emilazy:matrix.orgemily 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
@emilazy:matrix.orgemily ideally boot.initrd would mirror the top level hierarchy 19:20:04
@emilazy:matrix.orgemilybut alas :)19:20:07
@marcel:envs.netMarcel so boot.initrd.networking? ;D 19:20:22
@emilazy:matrix.orgemilyyeah, but it's probably too confusing to do that19:20:37
@marcel:envs.netMarcelyeah unserstand that19:20:42
@marcel:envs.netMarceli'll use networking19:20:49
@marcel:envs.netMarcel * 19:20:54
@marcel:envs.netMarcel

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:lossy.networkhexaplease bring ifstate upstream20:27:00
@hexa:lossy.networkhexait's one more thing we can point people to, to escape scripted networking20:27:10
@elvishjerricco:matrix.orgElvishJerricco hexa (clat on linux when): (that is what they're working on :P) 20:27:23
@hexa:lossy.networkhexaand e.g. if they require network namespaces20:27:24
@marcel:envs.netMarcel
In reply to @hexa:lossy.network
please bring ifstate upstream
I am currenlty in the process ;D
20:27:25
@hexa:lossy.networkhexawas only aware of the flake 🙂 20:27:33
@hexa:lossy.networkhexabacklog is hard20:27:40
@elvishjerricco:matrix.orgElvishJerricco the networkmanager module just sets it to false 20:28:05
@emilazy:matrix.orgemily tbh, I hate overriding useDHCP from another module like that, but it's what NM and connman do, so it's probably the way to go 20:28:06
@emilazy:matrix.orgemily (I guess, mostly I dislike networking.useDHCP being on by default) 20:28:21
@emilazy:matrix.orgemilyassertion is still good to have as a backstop20:28:31
@marcel:envs.netMarcel
In reply to @emilazy:matrix.org
assertion is still good to have as a backstop
i've also done them for networkd and all the others
20:28:46
@emilazy:matrix.orgemily networking.useNetworkd will likely be on by default as well soon, FWIW 20:29:10

Show newer messages


Back to Room ListRoom Version: 6