| 22 Nov 2025 |
 raboof | Neat, never seen it before. Yeah I thought "I'll just throw something together real fast". A blackbox-exporter patch, autossh conflicting with nixos-rebuilder-ng and this rp thing later it didn't quite turn out like that, but still enjoying the learning 😊 | 18:40:48 |
 elisaado | the topic mentions "do not rely on networking.*", why is that? networking. options are so comfy :( | 23:02:45 |
 Tom | From my understanding: networking.* (without the networking.useNetworkd Option which is problematic in itself) is a bunch of scripts and systemd services which try to configure networking. It's just not the way to do it and networkd and networkmanager will be more robust. | 23:27:26 |
 hexa (clat on linux when) | nobody really maintains those scripts | 23:28:51 |
| hexa (clat on linux when) | and they don't keep pace with the network management tools out there | 23:29:04 |
| hexa (clat on linux when) | and in fact no other reasonable distro does this | 23:30:26 |
| hexa (clat on linux when) | debian did this with ifupdown, but that's largely a legacy project | 23:30:33 |
| hexa (clat on linux when) | and ubuntu doubled down on another abstraction layer with netplan | 23:30:43 |
| hexa (clat on linux when) | for headless setups we have networkd and ifstate | 23:31:13 |
| hexa (clat on linux when) | and for headful ones the only reasonable contender is networkmanager | 23:31:31 |
| hexa (clat on linux when) | mellanox did develop ifupdown2, which provided ifreload for gradual migrations between old and new config, really neat | 23:32:03 |
| hexa (clat on linux when) | * cumulus did develop ifupdown2, which provided ifreload for gradual migrations between old and new config, really neat | 23:32:13 |
| hexa (clat on linux when) | not sure how well maintained it is these days, but it builds upon the config format established by ifupdown itself, which is … not so nice | 23:33:01 |
| hexa (clat on linux when) | https://github.com/CumulusNetworks/ifupdown2 | 23:33:02 |
| hexa (clat on linux when) | and of course there is ifupdown-ng (e.g. provided on alpine) in that ifupdown lineage https://github.com/ifupdown-ng/ifupdown-ng | 23:34:00 |
| hexa (clat on linux when) | I haven't seen anyone ask for the last two tbh | 23:34:12 |
| hexa (clat on linux when) | https://github.com/NixOS/nixpkgs/issues/238159 | 23:34:35 |
| hexa (clat on linux when) | oh, someone requested ifupdown-ng, my mistake 🙂 | 23:34:43 |
| 23 Nov 2025 |
|  @easel:matrix.org left the room. | 01:49:36 |
|  elden joined the room. | 10:14:15 |
| elisaado | ah I see | 12:07:55 |
| elisaado | yeah fair enough | 12:08:12 |
| elisaado | makes sense, thank you both :) | 12:08:16 |
 debtquity | since we shouldn't use the networking.* options, is there an recommendation for networking.firewall.* options? | 23:50:52 |
| 24 Nov 2025 |
| elisaado | I guess networking.nftables.tables.<name>.content, though that falls under networking.* as well strictly speaking :P | 00:27:02 |
 K900 | Those are fine | 04:32:47 |
| hexa (clat on linux when) changed the room topic to "Declaratively manage your switching, routing, wireless, tunneling and more. | Don't rely on `networking.*` for interface and routing setup, use systemd-networkd and NetworkManager instead. | Set `SYSTEMD_LOG_LEVEL=debug` to debug networking issues with networkd | No bad nft puns, please. | Room recommendations: #sysops:nixos.org" from "Declaratively manage your switching, routing, wireless, tunneling and more. | Don't rely on `networking.*` use systemd-networkd and NetworkManager instead. | Set `SYSTEMD_LOG_LEVEL=debug` to debug networking issues with networkd | No bad nft puns, please. | Room recommendations: #sysops:nixos.org". | 11:14:02 |
 Nico | 😂 | 12:06:15 |
| Nico | We could also mention ifstate in the description, which is being added in 25.11 | 12:06:43 |
| hexa (clat on linux when) changed the room topic to "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.org" from "Declaratively manage your switching, routing, wireless, tunneling and more. | Don't rely on `networking.*` for interface and routing setup, use systemd-networkd and NetworkManager instead. | Set `SYSTEMD_LOG_LEVEL=debug` to debug networking issues with networkd | No bad nft puns, please. | Room recommendations: #sysops:nixos.org". | 12:09:10 |
