Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #94158
| From | Troy Mitchell <me@troy-y.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#1146486: configure_networking: DHCP retries should be configurable / breaks remote unlocking |
| Date | 2026-09-21 12:00 +0200 |
| Message-ID | <NFIYx-V2p-7@gated-at.bofh.it> (permalink) |
| References | <NyRWV-eKKe-5@gated-at.bofh.it> <NyRWV-eKKe-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
> which means that if after all these retries, the DHCP server is still
> not available (it may take dozens of minutes after a power outage),
> remote unlocking the machine is impossible.
>
> The retries should be configurable. In particular, it should at least
> be possible to wait for an indefinite amount of time (without a large
> delay between the retries).
I've posted a fix here:
https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/203
It adds IPCONFIG_TIMEOUTS to configure the timeout sequence and
IPCONFIG_RETRY=y to keep retrying until dynamic configuration succeeds.
The defaults stay unchanged.
The package builds with sbuild. In QEMU, the client obtained an address
when DHCP became available after 20 seconds. I haven't tested the full
remote-unlock flow.
- Troy
Back to linux.debian.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Bug#1146486: configure_networking: DHCP retries should be configurable / breaks remote unlocking Vincent Lefevre <vincent@vinc17.net> - 2026-09-02 14:10 +0200 Bug#1146486: configure_networking: DHCP retries should be configurable / breaks remote unlocking Troy Mitchell <me@troy-y.org> - 2026-09-21 12:00 +0200
csiph-web