| 19 Jun 2026 |
K900 | But it's like | 12:54:33 |
K900 | Fine | 12:54:37 |
K900 | The scripted networking predates networkd and significantly predates networkd being usable | 12:54:53 |
K900 | And is in fact marked as kinda-deprecated already | 12:55:04 |
| @vengmark2:matrix.org left the room. | 12:55:30 |
matthewcroughan | Yeah, so when scripted networking is completely deprecated, you could also deprecate the networking.* modules altogether, and then people can just write networkd config, right? | 12:58:55 |
matthewcroughan | Or is the networking.* module doing more than I think? | 12:59:41 |
K900 | Yes | 13:00:42 |
Marcel | E.g. networking.ifstate is not part of scripted networking | 13:14:36 |
matthewcroughan | Is it actually possible to opt out of the networking module altogether? | 13:35:35 |
Marcel | I don't really know | 13:37:30 |
Marcel | disabledModules = [ "services/databases/postgresql.nix" ];
Could be working, one just needs to gather all scripted related modules
| 13:38:23 |
K900 | Not currently | 13:44:39 |
K900 | Probably a bad idea really | 13:44:47 |
K900 | There's stuff like networking.hostName in there | 13:45:16 |
matthewcroughan | Oh yeah true | 13:48:08 |
magic_rb | The only thing i dont like about ifstate that its daemon less. Id like for there to be a way to have it respond to netlink messages and ignore interfaces it cant find. Then when they show up, it should configure them correctly. | 14:42:53 |
magic_rb | Ik thats a very hard problem to solve ofc | 14:43:05 |
Marcel | I wondered if something like that would be possible with udev. So let udev run ifstate if udev detects a change in networking devices. Idk if something like that is possible | 18:27:56 |
magic_rb | Sure, also an option but with you dev you only get device added/removed i think. You wouldnt get things like up/down or config changes. | 18:37:20 |
Marcel | Probably right | 21:27:28 |
Marcel | On the other side, it's primary use case is on servers and not client devices | 21:27:59 |