Sorry, your reply went to google's spam folder :/ I just install dropbear-initramfs with no configuration regarding network, this sets up a dhcp configuration with a script in init-premount:
[...] # On NFS mounts, wait until the network is configured. On local mounts, # configure the network in the background (in run_dropbear()) so someone # with console access can enter the passphrase immediately. (With the # default ip=dhcp, configure_networking hangs for 5mins or so when the # network is unavailable, for instance.) [ "$BOOT" != nfs ] || configure_networking [...] So it's not a kernel parameter because this delays the prompt when a console is attached. Kind regards, Axel Scheepers On Mon, Aug 9, 2021 at 7:13 PM Michael Biebl <bi...@debian.org> wrote: > Am 09.08.21 um 18:03 schrieb Axel Scheepers: > > Package: systemd > > Version: 247.3-6 > > Severity: normal > > > > Dear Maintainer, > > > > * What led up to the situation? > > > > Testing bullseye rc-3 install on remote server. > > > > > > > > * What exactly did you do (or not do) that was effective (or > > ineffective)? > > > > I used encrypted root and dropbear initramfs to remote unlock, also > setup systemd-networkd for > > both wireless and wired interfaces: > > How exactly do you configure your network in the initramfs? > systemd-networkd does not ship any hooks for that. > > >
