[systemd-devel] systemd and hostname supplied by DHCP
Alessio Igor Bogani
alessioigorbogani at gmail.com
Tue Sep 29 04:53:04 PDT 2015
Hi David,
On 28 September 2015 at 16:05, David Timothy Strauss
<david at davidstrauss.net> wrote:
> On Mon, Sep 28, 2015 at 1:19 AM Alessio Igor Bogani
> <alessioigorbogani at gmail.com> wrote:
[...]
>> The systemd 219 brought with Yocto "Fido" can't set hostname supplied
>> by DHCP on my Beaglebone:
[...]
> "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.
This doesn't seem the case:
ssh root at gallinella
root at gallinella's password:
localhost:~# ping gallinella
PING gallinella.elettra.trieste.it (192.168.205.87) 56(84) bytes of data.
64 bytes from gallinella.elettra.trieste.it (192.168.205.87):
icmp_seq=1 ttl=64 time=0.255 ms
64 bytes from gallinella.elettra.trieste.it (192.168.205.87):
icmp_seq=2 ttl=64 time=0.237 ms
64 bytes from gallinella.elettra.trieste.it (192.168.205.87):
icmp_seq=3 ttl=64 time=0.218 ms
^C
--- gallinella.elettra.trieste.it ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 0.218/0.236/0.255/0.023 ms
localhost:~# cat /etc/resolv.conf
# This file is managed by systemd-resolved(8). Do not edit.
#
# Third party programs must not access this file directly, but
# only through the symlink at /etc/resolv.conf. To manage
# resolv.conf(5) in a different way, replace the symlink by a
# static file or a different symlink.
nameserver 140.105.4.3
nameserver 140.105.2.5
nameserver 140.105.8.3
search elettra.trieste.it
localhost:~# hostnamectl
Static hostname: n/a
Transient hostname: localhost
Icon name: computer
Machine ID: c3f437527c6e4f62a27ec7725dbdef6d
Boot ID: d74e8174075b458ebe9105d93c83a029
Operating System: FLOP pre0.5 (fido)
Kernel: Linux 3.14.39ltsi-rt37-yocto-preempt-rt
Architecture: arm
localhost:~# journalctl -u systemd-networkd.service
-- Logs begin at Tue 2015-09-29 13:32:00 CEST, end at Tue 2015-09-29
13:33:54 CEST. --
Sep 29 13:32:07 localhost systemd[1]: Starting Network Service...
Sep 29 13:32:07 localhost systemd-networkd[231]: Enumeration completed
Sep 29 13:32:07 localhost systemd[1]: Started Network Service.
Sep 29 13:32:08 localhost systemd-networkd[231]: eth0 :
eth0 : could not bring up interface: Invalid argument
Sep 29 13:32:11 localhost systemd-networkd[231]: eth0 :
gained carrier
Sep 29 13:32:11 localhost systemd-networkd[231]: eth0 :
DHCPv4 address 192.168.205.87/24 via 192.168.205.1
Sep 29 13:32:11 localhost systemd-networkd[231]: eth0 :
link configured
Sep 29 13:32:12 localhost systemd-networkd[231]: eth0 :
Could not set hostname: No route to host
Thanks a lot anyway!
Saluti,
Alessio
More information about the systemd-devel
mailing list