| 24 Nov 2025 |
|  hexa 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 |
