| 28 Jul 2025 |
 emily | like, you can also have both networkd and NM enabled, and it is fine as long as you do not try to configure the same interface with both | 20:31:43 |
 @marcel:envs.net | they wonder why the changes do not apply and get overriden by ifstate, maybe even depeing on the order and between ifstate and networkd it could bing randomness demending which is faster | 20:31:49 |
| @marcel:envs.net | ifstate is nice, because it deconfigures everything not defined | 20:32:07 |
| @marcel:envs.net | its truly declarative | 20:32:13 |
| emily | ## ignore settings to ignore existing interface, ip addresses, … (optional)
# ignore: …
| 20:32:20 |
| emily | it looks like you can explicitly tell ifstate to ignore stuff you don't want it to manage | 20:32:28 |
| @marcel:envs.net | except for the ignore part | 20:32:30 |
| emily | I think it is okay not to try and guard against everything as long as the obvious things are covered | 20:32:49 |
| @marcel:envs.net | stuff like docker or libvirt managed interfaces should be there | 20:32:52 |
| emily | people can always run … some other random software that tries to tweak networking config :) | 20:32:55 |
| emily | and run into issues like that | 20:33:01 |
| emily | I would just assert on useDHCP and NetworkManager | 20:33:13 |
| @marcel:envs.net | ok | 20:33:18 |
| emily | you could get fancy with config.systemd.network.{networks,netdevs,links} but I think it is not worth it | 20:33:55 |
| @marcel:envs.net | but to do it corrently i also had to interpret the ignore section of ifstate | 20:34:21 |
| @marcel:envs.net | * | 20:34:31 |
| emily | like | 20:36:15 |
| emily | you are also not asserting on networking.interfaces.* | 20:36:25 |
