!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

885 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.org254 Servers

Load older messages


SenderMessageTime
29 Jun 2025
@zhaofeng:zhaofeng.liZhaofeng Liit's also an escape hatch in case you end up hating ifstate and want to go back02:20:46
@hexa:lossy.networkhexa (clat on linux when)I get the appeal, but these are APIs we will not be able to deprecate02:21:37
@hexa:lossy.networkhexa (clat on linux when)even if they are bad02:21:40
@hexa:lossy.networkhexa (clat on linux when)like network.interfaces 😄 02:21:43
@emilazy:matrix.orgemily is it that bad in the useNetworkd form? 02:22:17
@emilazy:matrix.orgemilyah, I guess you said as much02:22:33
@hexa:lossy.networkhexa (clat on linux when)there was something weird about that option that I don't remember anymore02:22:44
@emilazy:matrix.orgemilypretty much guaranteed to end up hellish due to impedance mismatches for API surfaces that big02:23:03
@hexa:lossy.networkhexa (clat on linux when)

Note that this option is experimental, enable at your own risk.

02:23:08
@hexa:lossy.networkhexa (clat on linux when)for useNetworkd 😄 02:23:14
@hexa:lossy.networkhexa (clat on linux when)thanks linus02:23:17
@emilazy:matrix.orgemilyI think it was very near "switched on by default" stage at some point?02:23:49
@emilazy:matrix.orgemilyand then that just didn't happen02:23:55
@emilazy:matrix.orgemilyshim code for the options is certainly better than keeping scripted networking around indefinitely I think02:24:19
@emilazy:matrix.orgemily I think probably most people using networkd are using it through useNetworkd 02:24:44
@hexa:lossy.networkhexa (clat on linux when)https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/tasks/network-interfaces-systemd.nix02:25:59
@hexa:lossy.networkhexa (clat on linux when)basically an implementation that needs to be worked at for changes on both sides02:26:34
@hexa:lossy.networkhexa (clat on linux when)frankly, I don't get why people hate networking so much02:26:44
@hexa:lossy.networkhexa (clat on linux when)most boxes have just a wan interface and throwing static addresses and a gateway on it isn't hard02:27:07
@hexa:lossy.networkhexa (clat on linux when)or do dhc02:27:13
@hexa:lossy.networkhexa (clat on linux when)* or do dhcp02:27:14
@emilazy:matrix.orgemily I think useDHCP is a sufficient compatibility shim for probably the majority of NixOS boxes in existence 02:27:32
@emilazy:matrix.orgemily but in the absence of scripted networking I don't think this file is too bad either, it is mostly just simple option mapping 02:28:03
@emilazy:matrix.orgemilythat openvswitch stuff is awful though :)02:28:10
@hexa:lossy.networkhexa (clat on linux when)it feels like a code drop introducing technical debt for the most part 02:29:07
@hexa:lossy.networkhexa (clat on linux when)the awful part is that people will never migrate away from network.interfaces that way02:29:24
@hexa:lossy.networkhexa (clat on linux when)* the awful part is that people will never migrate away from networking.interfaces that way02:29:44
@hexa:lossy.networkhexa (clat on linux when) like, what would be so hard about just running networking.dhcpcd.enable with allowInterfaces = [ "eth0" ] instead of useDHCP? 02:30:35
@hexa:lossy.networkhexa (clat on linux when) and why the hell is it usedhcp? 02:30:59
@hexa:lossy.networkhexa (clat on linux when) * and why the hell is it useDHCP? 02:31:19

Show newer messages


Back to Room ListRoom Version: 6