!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

908 Members
Declaratively manage your switching, routing, wireless, tunneling and more.263 Servers

Load older messages


SenderMessageTime
29 Jun 2025
@emilazy:matrix.orgemilythat openvswitch stuff is awful though :)02:28:10
@hexa:lossy.networkhexait feels like a code drop introducing technical debt for the most part 02:29:07
@hexa:lossy.networkhexathe awful part is that people will never migrate away from network.interfaces that way02:29:24
@hexa:lossy.networkhexa* the awful part is that people will never migrate away from networking.interfaces that way02:29:44
@hexa:lossy.networkhexa like, what would be so hard about just running networking.dhcpcd.enable with allowInterfaces = [ "eth0" ] instead of useDHCP? 02:30:35
@hexa:lossy.networkhexa and why the hell is it usedhcp? 02:30:59
@hexa:lossy.networkhexa * and why the hell is it useDHCP? 02:31:19
@emilazy:matrix.orgemilyI thought networkd didn't use dhcpcd02:31:29
@hexa:lossy.networkhexaand not network.interfaces.<name>dhcp.enable02:31:33
@hexa:lossy.networkhexait does not02:31:38
@emilazy:matrix.orgemilyI believe both exis?02:31:45
@emilazy:matrix.orgemily* I believe both exist?02:31:46
@hexa:lossy.networkhexaI don't want to force people onto networkd02:31:47
@hexa:lossy.networkhexa* I don't want to force people onto networkd specifically02:31:49
@hexa:lossy.networkhexaI want to force them off of scripted networking02:31:57
@emilazy:matrix.orgemily well, I think the idea of useNetworkd was precisely to be able to move everyone from scripted networking to networkd without having to break every single networking configuration in existence 02:32:17
@emilazy:matrix.orgemilyI think it's a lot easier to sell a flag day when it doesn't break the most basic networking config02:32:32
@emilazy:matrix.orgemilygradually deprecating the old stuff is going to be easier after everyone is already running an implementation backed by the migration path02:32:53
@hexa:lossy.networkhexait boils down to us being bad at deprecating interfaces02:32:56
@hexa:lossy.networkhexado you think we should support the old option interface indefinately then?02:33:21
@hexa:lossy.networkhexa* do you think we should support the old option interface indefinately then and just deprecated the backend?02:33:27
@emilazy:matrix.orgemilynot necessarily02:34:00
@hexa:lossy.networkhexabecause I would really hope that the average nixos user would arrive at a place where they can apply 7 lines of config for an interface02:34:02
@hexa:lossy.networkhexa* do you think we should support the old option interface indefinately then and just deprecate the backend?02:34:12
@hexa:lossy.networkhexahttps://wiki.nixos.org/wiki/Systemd-networkd#Examples already covers the basic use cases02:34:43
@emilazy:matrix.orgemilybut I think "ok, we're switching the backend, people have been using this for years but let us know if you run into any issues" → "ok, we're moving away from these options, you're already using networkd under the hood so you can migrate to an identical configuration" is easier to do as those two steps than if they have to switch both backend and migrate their config at the same time02:34:46
@hexa:lossy.networkhexathey will still have to map the configuration from a to b02:35:12
@emilazy:matrix.orgemilyyeah, but it will not risk behavioural changes at that point02:35:28
@emilazy:matrix.orgemilyit disentangles the two parts02:35:39
@hexa:lossy.networkhexathey will not understand the mapping02:35:45

Show newer messages


Back to Room ListRoom Version: 6