Your message dated Wed, 2 Sep 2026 13:36:54 +0200
with message-id <[email protected]>
and subject line Re: Bug#1146482: dropbear-initramfs: When DHCP server isn't
available immediately, remote unlocking is impossible: no search or nameservers
found in...
has caused the Debian Bug report #1146482,
regarding dropbear-initramfs: When DHCP server isn't available immediately,
remote unlocking is impossible: no search or nameservers found in...
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1146482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1146482
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dropbear-initramfs
Version: 2026.94-1
Severity: normal
When the DHCP server isn't available immediately (which typically
occurs after a power outage), I get several lines
IP-Config: no response after xxx secs - giving up
which is normal, but after a few minutes, I get the following error:
no search or nameservers found in /run/net-.conf /run/net-*.conf
and it is impossible to unlock the machine remotely!
-- System Information:
Debian Release: forky/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'),
(500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 7.1.12+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dropbear-initramfs depends on:
ii busybox 1:1.38.0-3+b1
ii dropbear-bin 2026.94-1
ii initramfs-tools 0.151
ii udev 261.2-1
Versions of packages dropbear-initramfs recommends:
ii cryptsetup-initramfs 2:2.8.7-1
dropbear-initramfs suggests no packages.
-- Configuration Files:
/etc/dropbear/initramfs/dropbear.conf changed:
DROPBEAR_SHUTDOWN_TIMEOUT=10
-- no debconf information
--
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
On Wed, 02 Sep 2026 at 12:35:13 +0200, Vincent Lefevre wrote:
> When the DHCP server isn't available immediately (which typically
> occurs after a power outage), I get several lines
>
> IP-Config: no response after xxx secs - giving up
>
> which is normal, but after a few minutes, I get the following error:
>
> no search or nameservers found in /run/net-.conf /run/net-*.conf
These messages come from
initramfs-tools/scripts/functions:configure_networking() not
src:dropbear.
> and it is impossible to unlock the machine remotely!
dropbear-initramfs doesn't configure the network on its own. It calls
configure_networking().
Sounds like it should be a wishlist bug for initramfs-tools-core to make
the delay configurable or not give up so easily.
In principle dropbear-initramfs could add some network detection checks
and call configure_networking() over and over untill the networks is up,
but that logic doesn't belong to dropbear-initramfs IMHO, hence closing
this.
As a workaround, you could add a `sleep 300` or so delay in a custom
init-premount script (make sure it starts before dropbear though). This
might be OK as long as you don't reboot the machine too often.
--
Guilhem.
signature.asc
Description: PGP signature
--- End Message ---
