2 ms·
It’s the fate of every config generator, yes, although I find NixOS better than average in that respect (between Arch and Debian in how easy it is to figure out
by mananaysiempre 4y ago
It’s the fate of every config generator, yes, although I find NixOS better than average in that respect (between Arch and Debian in how easy it is to figure out what the hell it’s doing to the underlying software).
Troubleshooting guides for NixOS are non-existent, but the system itself is not all that difficult to inspect: two things you can do is `nixos-rebuild build` without switching and meditate on ./result/; and inspect `(builtins.getFlake(toString ./.).nixosConfigurations` in `nix repl` (use import etc. if not using flakes) as that will include every derived setting down to the text of generated config files, not only those you specified explicitly.
But you might’ve just nerd-sniped me, we’ll see.
ETA: Looks like it’s indeed systemd-networkd’s doing[1]. For a static interface, setting `networking.interfaces.${NAME}.macAddress`[2] to the desired value should work.
[1] https://freedesktop.org/software/systemd/man/systemd.netdev.html https://freedesktop.org/software/systemd/man/systemd.netdev...., see the description for MACAddress.
[2] https://search.nixos.org/options?show=networking.interfaces.%3Cname%3E.macAddress&query=macAddress https://search.nixos.org/options?show=networking.interfaces....