xenial:
ubuntu@a123456789b123456789c123456789d123456789e123456789f123456789g123:~$ dpkg
-l systemd|grep systemd
ii systemd 229-4ubuntu21.28 amd64 system and service manager
ubuntu@a123456789b123456789c123456789d123456789e123456789f123456789g123:~$
journalctl -b -u systemd-networkd | grep 'DHCP error'
Sep 09 18:30:30
a123456789b123456789c123456789d123456789e123456789f123456789g123
systemd-networkd[732]: ens3: DHCP error: Client failed: Invalid argument
ubuntu@a123456789b123456789c123456789d123456789e123456789f123456789g123:~$ dpkg
-l systemd|grep systemd
ii systemd 229-4ubuntu21.29 amd64 system and service manager
ubuntu@a123456789b123456789c123456789d123456789e123456789f123456789g123:~$
journalctl -b -u systemd-networkd | grep 'DHCP error'
and did get a dhcp address:
ubuntu@a123456789b123456789c123456789d123456789e123456789f123456789g123:~$ ip a
show ens3
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP
group default qlen 1000
link/ether 52:54:00:e1:a8:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.122.102/24 brd 192.168.122.255 scope global dynamic ens3
valid_lft 3566sec preferred_lft 3566sec
inet6 fe80::5054:ff:fee1:a83f/64 scope link
valid_lft forever preferred_lft forever
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1877176
Title:
64-char hostname causes dhcp server to reject lease
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Fix Committed
Bug description:
[impact]
a systemd with a 64-character hostname (the maximum hostname length
for Linux) will cause a dhcp server to reject its dhcp lease due to
passing the invalid hostname in the dhcp lease request.
[test case]
$ cat /etc/systemd/network/10-ens3.network
[Match]
Name=ens3
[Network]
DHCP=yes
set hostname to 64-char name, e.g.:
$ sudo hostnamectl set-hostname
a123456789b123456789c123456789d123456789e123456789f123456789g123
restart networkd:
$ sudo systemctl restart systemd-networkd
check logs:
root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~#
journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error'
May 06 19:01:30
a123456789b123456789c123456789d123456789e123456789f123456789g123
systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument
[regression potential]
Any regression would likely result in failure configuring/processing
dhcpv4 server response, or rejection from the dhcpv4 server.
[scope]
this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which
is included in Bionic and later. This is needed only for Xenial.
[other info]
this is a follow on to bug 1862232, which corrected sd-dhcp-client.c
to continue networkd dhcp even if the hostname is invalid, however the
older code in Xenial doesn't correctly detect the invalid hostname, so
this additional patch is needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877176/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
