!tCyGickeVqkHsYjWnh:nixos.org

NixOS Networking

883 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.org251 Servers

Load older messages


SenderMessageTime
29 Jun 2025
@elvishjerricco:matrix.orgElvishJerricco All I'm saying is that we shouldn't change nixos-generate-config. Whether we remove parts of the interface is another matter 04:32:19
@elvishjerricco:matrix.orgElvishJerricco We want hardware-configuration.nix to use abstractions 04:32:27
@elvishjerricco:matrix.orgElvishJerriccothat's actively good for us as maintainers in the long run04:32:33
@emilazy:matrix.orgemilyit already does not really do a good job at that tbh04:33:42
@emilazy:matrix.orgemilynixos-facter might achieve it more04:33:51
@elvishjerricco:matrix.orgElvishJerriccoI mean sure but we're not also going to tack that onto the todo list for this04:34:06
@emilazy:matrix.orgemilyI don't think it is really bad to expose people to networkd config. that is what they are expected to write on Arch etc.04:35:01
@elvishjerricco:matrix.orgElvishJerriccoThat isn't the point04:35:10
@elvishjerricco:matrix.orgElvishJerriccoI don't care if users are exposed to it or not04:35:18
@elvishjerricco:matrix.orgElvishJerriccoI care that what we generated one day is something we can continue to maintain the next04:35:29
@emilazy:matrix.orgemilyNixOS can't be in the game of making its own complex abstraction layers for everything in the system04:35:32
@elvishjerricco:matrix.orgElvishJerriccowe can't make changes to generated configs04:35:33
@elvishjerricco:matrix.orgElvishJerriccowe can make changes to abstraction implementations04:35:38
@emilazy:matrix.orgemilyI still think hardware-configuration is a red herring here04:35:49
@hexa:lossy.networkhexa (clat on linux when)The users that use the unmaintained shit don't maintain the abstractions04:35:53
@elvishjerricco:matrix.orgElvishJerricco it's literally the only thing nixos-generate-config is about? 04:36:02
@emilazy:matrix.orgemily"I want DHCP by default" is configuration.nix not hardware-configuration.nix teritory04:36:04
@hexa:lossy.networkhexa (clat on linux when)Whatever we give as a configuration.nix is mutable by default04:36:14
@emilazy:matrix.orgemilyand there's no promise that configuration.nix never has to change04:36:15
@hexa:lossy.networkhexa (clat on linux when)And everyone manages to enable network manager on their laptop as well04:36:29
@hexa:lossy.networkhexa (clat on linux when)or not, idk04:36:32
@emilazy:matrix.orgemily
In reply to @elvishjerricco:matrix.org
it's literally the only thing nixos-generate-config is about?
it generates a configuration.nix too, does it not?
04:36:40
@emilazy:matrix.orgemilyI haven't actually run it in years04:36:46
@elvishjerricco:matrix.orgElvishJerricco I mean if you just want to move all networking stuff out of hardware-configuration.nix altogether that's a different thing. 04:36:52
@hexa:lossy.networkhexa (clat on linux when)Redacted or Malformed Event04:36:59
@hexa:lossy.networkhexa (clat on linux when)Redacted or Malformed Event04:37:02
@elvishjerricco:matrix.orgElvishJerricco networking.useDHCP = lib.mkDefault true; goes in hardware-configuration.nix 04:37:27
@hexa:lossy.networkhexa (clat on linux when)sorry, I might be wrong04:37:31
@hexa:lossy.networkhexa (clat on linux when) that's stupid to have in hardware parts 04:37:40
@emilazy:matrix.orgemilythings that aren't hardware config should certainly not be in there04:37:47

Show newer messages


Back to Room ListRoom Version: 6