| 29 Jun 2025 |
 ElvishJerricco | and it's not been a problem | 04:48:11 |
 hexa | we ship with networkd either way | 04:48:11 |
| hexa | and it will have no config files, so it will not match anything | 04:48:19 |
 emily | In reply to @hexa:lossy.network
we ship with networkd either way not enabled | 04:48:21 |
| emily | but fair | 04:48:26 |
| hexa | yeah, not sure about enable toggle, but it will be a noop | 04:48:40 |
| emily | In reply to @uep:matrix.org
usedhcp is a fine default for a generic system with wired interfaces, regardless of which dhcp mechanism delivers the implementation. On a server, maybe you want static on at least some interfaces, so sure, you add config for those.
The issue is wireless. If a wireless interface appears, adding a dhcp client gets in the way of whatever mechanism the user is going to use to set ssid and keys, and so it has to get out of the way I thought our useDHCP default for networkd was wired only | 04:50:23 |
| ElvishJerricco | nope | 04:50:29 |
| emily | ok, well | 04:50:40 |
| ElvishJerricco | https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/tasks/network-interfaces-systemd.nix#L56-L75 | 04:50:50 |
| emily | what if we just introduce systemd.network.dwim = true; that ships the sane file for doing that that I think upstream has | 04:51:11 |
| emily | and put that in configuration.nix | 04:51:22 |
| hexa | lolsob … manual metric tuning | 04:51:25 |
| hexa | networkmanager to the rescue | 04:51:28 |
