-
Notifications
You must be signed in to change notification settings - Fork 102
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
requires 'dhcpcd -k' to aquire a good ipv4 lease #298
Comments
Building from master branch |
let me add that building from master branch fixes the issue with openwrt router (but not with eduroam, see above).
|
Sorry for the late reply, but I have been thinking this over. I'll need logging with debug enabled in dhcpcd.conf please. |
Thanks for looking at this, and for maintaining dhcpcd.
The log with debug enabled:
The etc/dhcpcd.conf file:
|
Well, there's nothing that stands out as wrong in your logs. |
And thanks for the thanks :) |
Sure. The Void Linux package already creates a system account |
The directory itself doesn't matter as long as it exists. |
Building with privsep
produces the log
The template that Void Linux uses to build BTW, you might be interested in upstreaming the |
I now suspect this may be related to |
However, after suspending for a few minutes, the same issue comes back:
|
Since today, I'm unable to reproduce this. |
After suspending, or upon reboot, dhcpcd seems stuck, either with no carrier or with the ipv4all ip address.
This is on Void Linux, which has dhcpcd-10.0.5 managed through a runit service:
It happens both on my home network (openwrt) as well as on enterprise network (eduroam at a university).
Issuing
dhcpcd -k
usually solves it, as seen in the log.The config file is rather standard (if I add
noipv4all
, then it gets stuck at waiting for a carrier):An excerpt from the log (I redacted a bunch of addresses, let me know if they're needed. Also, for some reason, the logs appear twice as info and as notice, which I removed by hand to avoid clutter. Not sure if it's a mistake in the runit service though.):
Do you see anything out of place? Thanks.
The text was updated successfully, but these errors were encountered: