| 22 Nov 2025 |
 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 |
| 25 Nov 2025 |
|  @steeringwheelrules:tchncs.de left the room. | 18:12:14 |
| 29 Nov 2025 |
 thoth | Is the useNetworkd option problematic ? | 11:28:43 |
| K900 | Not particularly, but it's kind of a weird kludge that tries to map scripted networking options to networkd | 11:32:53 |
 jappie | ah so it's best to leave networking.useNetworkd on false when using system.network? | 11:52:17 |
| jappie | * ah so it's best to leave networking.useNetworkd on false when using systemd.network? | 11:52:36 |
| K900 | It should not matter if you have no other networking.* options | 11:55:00 |
| 2 Dec 2025 |
 kdn | is there a reasonable way to force custom-built install-iso to use only one (first?) of the plugged in ethernet interfaces? | 12:23:01 |
| kdn | * is there a reasonable way to force custom-built install-iso to use only one (first?) of the plugged in ethernet interfaces without telling it which one should it be? | 12:23:10 |
| kdn | I have devices with 4 ports and I can only access it through one of those with the highest default route metric | 12:23:41 |
 Sandro 🐧 | first as in the one with highest default route, as first doesn't make much sense otherwise | 14:47:25 |
| K900 | Do you control the route metrics? | 14:48:56 |
| K900 | You can just push the correct metric over DHCP | 14:49:22 |
| K900 | If you control the DHCP | 14:49:30 |
| K900 | (you probably should do that anyway) | 14:49:41 |
