On Mon, Sep 28, 2015 at 1:19 AM Alessio Igor Bogani < alessioigorbog...@gmail.com> wrote:
> Hi systemd developers and users, > > The systemd 219 brought with Yocto "Fido" can't set hostname supplied > by DHCP on my Beaglebone: > > eth0 : eth0 : could not bring up interface: > Invalid argument > eth0 : gained carrier > eth0 : DHCPv4 address 192.168.205.87/24 via 192.168.205.1 > eth0 : link configured > eth0 : Could not set hostname: No route to host > "Could not set hostname: No route to host" sounds like systemd is trying to resolve and ping the provided hostname. But, it's failing, and so systemd is deciding that it's not a usable hostname. Doesn't seem related to the DHCP protocol implementation at all.
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel