Bug#866812: dropbear-initramfs: DHCP request from InitRAMFS with Dropbear doesn't send hostname anymore

Thanks for the information, Guilhem. I got myself a solution/workaround by implementing an initramfs hook that dynamically sets the hostname without the need of setting the kernel cmd line: /etc/initramfs-tools/hooks/set_separate_ip_parameter.sh (attached) The reason that it was working with

Bug#866812: dropbear-initramfs: DHCP request from InitRAMFS with Dropbear doesn't send hostname anymore

Hi, On Sun, 02 Jul 2017 at 03:08:48 +0200, M. Buecher wrote: > when using Dropbear in an Debian 9.0 Stretch InitRAMFS for remotely unlocking > an encrypted root file system via SSH, then the network setup via DHCP does > provide the host name as it was with Debian 8.0 Jessie. > > This avoids

Bug#866812: dropbear-initramfs: DHCP request from InitRAMFS with Dropbear doesn't send hostname anymore

Sorry, of course it must be "does *not* provide the host name" in the bug report.

Bug#866812: dropbear-initramfs: DHCP request from InitRAMFS with Dropbear doesn't send hostname anymore

Package: dropbear-initramfs Version: 2016.74-5 Severity: important Dear Maintainer, when using Dropbear in an Debian 9.0 Stretch InitRAMFS for remotely unlocking an encrypted root file system via SSH, then the network setup via DHCP does provide the host name as it was with Debian 8.0 Jessie.