-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dhcpcd: Failed to set DNS configuration #76969
Comments
I'm also seeing this. |
I have the same problem. In my case, I did a bit of bisecting of the nixpkgs repo, and it seems that it is caused by this commit: cdf79db. Previous commits that I checked, up to dad49d0 (so just one before cdf79db) seem to work fine. HEAD of Can you check if it is your case as well? Pinging @infinisil, maybe he has some insight to it. My
On
Metadata:
|
Thanks for the ping, I'll take a look |
@karolchmist Can you run
This will show exactly what ended up being different for that commit |
Can reproduce, so I should be able to run this too |
Found the culprit! While it does start failing since #75031, the actual mistake is not in that PR, it merely exposes it. In that PR I'm mentioning:
And that is indeed what happened for dhcpcd: the ordering of packages in nixpkgs/nixos/modules/system/boot/systemd.nix Lines 242 to 249 in 00c813a
However for dhcpcd that's a problem, because both I'll submit a PR that fixes this by explicitly putting systemd's packages after others. |
This fixes the dhcpcd issue in NixOS#76969, which was exposed by NixOS#75031 introducing changes in the module ordering and therefore option ordering too. The dhcpcd issue would also be fixable by explicitly putting dhcpcd's paths before others, however it makes more sense for systemd's default paths to be after all others by default, since they should only be a fallback, which is how binary finding will work if they come after.
See above PR |
This fixes the dhcpcd issue in NixOS#76969, which was exposed by NixOS#75031 introducing changes in the module ordering and therefore option ordering too. The dhcpcd issue would also be fixable by explicitly putting dhcpcd's paths before others, however it makes more sense for systemd's default paths to be after all others by default, since they should only be a fallback, which is how binary finding will work if they come after. (cherry picked from commit 9327e1c)
I confirm that 9327e1c fixes this issue. |
Describe the bug
/etc/resolv.conf
doesn't have a name server.journal:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
/etc/resolv.conf
should have a nameserver field with my router address.Screenshots
Additional context
The machine is Raspberry Pi 3B.
nixos-rebuild switch
upgraded dhcpcd from 8.1.2 to 8.1.4 and linux kernel from 5.4.6 to 5.4.7.Metadata
The text was updated successfully, but these errors were encountered: