-
-
Notifications
You must be signed in to change notification settings - Fork 464
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
Pi drops IPv4 address after DHCP lease expires #611
Comments
No updates required (I'm on Bullseye on this machine still... need to upgrade it entirely. Maybe migrate to Pi 5 too ha!). Maybe I can try manually forcing a DHCP renewal? Will try that later as I have other things to get to this morning. |
Ah... from Stack Overflow:
Supposedly the fix is to add the following to the end of
Then restart dhcpcd:
...this wouldn't apply to Bookworm, so at some point I just need to bite the bullet and upgrade my main network Pi :) I will try this solution and see if it works after 24h. |
Solution was originally posted here: raspberrypi/linux#4092 (comment) And only found relevant info once I looked at journal entries for
|
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! Please read this blog post to see the reasons why I mark issues as stale. |
After updating to the latest versions of Pi OS, Docker, etc. sometime in the last week or two, my Internet Pi seems to entirely drop its wired network connection after my network DHCP lease is up (literally 24h after boot). The only way to recover is a hard reboot (since this is a headless Pi).
In the syslog, I see:
Initially I thought the network stack could be buggy, but after reading through Every 24h, network connectivity ceases, I'm beginning to think Docker's at fault, considering the interesting container networking layout that makes Internet Pi work...
I'll try to debug the problem in this issue, in case anyone else runs into it. First step, will try running a full upgrade today.
The text was updated successfully, but these errors were encountered: