!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.org253 Servers

Load older messages


SenderMessageTime
29 Jun 2025
@emilazy:matrix.orgemilydoes that break using NM for wlan?04:53:46
@hexa:lossy.networkhexa (clat on linux when)yeah, you need to understand the networkd config logic04:53:50
@hexa:lossy.networkhexa (clat on linux when)that 99-* applies last for example04:53:59
@hexa:lossy.networkhexa (clat on linux when)and is a catchall04:54:02
@emilazy:matrix.orgemilyI think we can just only ship the wired thing04:54:08
@hexa:lossy.networkhexa (clat on linux when)* and is a catchall for ether/wlan station04:54:13
@hexa:lossy.networkhexa (clat on linux when)as an example?04:54:23
@emilazy:matrix.orgemilyas systemd.network.wiredDHCP or something to ship by default in configs04:54:44
@hexa:lossy.networkhexa (clat on linux when)in which case I'd probably ship an example for DHCP/RA and one for Static Addressing04:54:52
@emilazy:matrix.orgemilybecause WLAN users will turn on NM or else be in wpa_supplicant weeds and having exciting learning experiences anyway04:54:54
@hexa:lossy.networkhexa (clat on linux when)kindly, let's not scuff up that module, thanks04:55:07
@elvishjerricco:matrix.orgElvishJerriccoagain, I really don't think networkd is the right tool if you aren't specifying your interfaces04:55:14
@hexa:lossy.networkhexa (clat on linux when)I do want WLAN users to use NM tbh 04:55:19
@hexa:lossy.networkhexa (clat on linux when)we are talking examples to give to the user04:55:37
@hexa:lossy.networkhexa (clat on linux when)I'm not proposing enabling any networkd logic by default04:55:48
@hexa:lossy.networkhexa (clat on linux when) we agreed on NM earlier04:55:55
@hexa:lossy.networkhexa (clat on linux when)* we agreed on enabling NM earlier04:56:00
@hexa:lossy.networkhexa (clat on linux when)but if you deploy a server having an example config for static/dynamic interface configuration with network in the example configuration.nix will be helpful04:56:28
@emilazy:matrix.orgemily
In reply to @hexa:lossy.network
kindly, let's not scuff up that module, thanks
if the constraints are "no scary networkd details in default configs" and "plugging in an Ethernet cable out of the box works" and "networking.useDHCP is busted actually"...
04:56:36
@emilazy:matrix.orgemilythen it's either NM or we add an option to achieve the basic sane config for networkd04:56:52
@hexa:lossy.networkhexa (clat on linux when)we agreed on NM 😄 04:56:59
@hexa:lossy.networkhexa (clat on linux when)can we not walk that back?04:57:04
@hexa:lossy.networkhexa (clat on linux when)* can we not walk that back w/o a good reason?04:57:10
@emilazy:matrix.orgemily
In reply to @emilazy:matrix.org
because I feel like "oh yeah to declaratively configure that you want to turn off NM that the generated config has and switch to this" is maybe not actually better
well, ^
04:57:33
@emilazy:matrix.orgemilyit was more a flippant reaction to the no networkd config constraint04:57:52
@emilazy:matrix.orgemilyit's fine for desktop users at least04:58:06
@hexa:lossy.networkhexa (clat on linux when)that's why I proposed shipping with examples for a declarative networkd config, that matches an explicit interface and shows a dhcp/ra and static example04:58:07
@emilazy:matrix.orgemilyI don't know if it's the right onramp for servers04:58:16
@emilazy:matrix.orgemily
In reply to @hexa:lossy.network
that's why I proposed shipping with examples for a declarative networkd config, that matches an explicit interface and shows a dhcp/ra and static example
as in NM enabled but commented out networkd example?
04:58:30
@uep:matrix.orguepsure, even if it's commented out or wahtever04:58:33

Show newer messages


Back to Room ListRoom Version: 6