Public bug reported:
[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
[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.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: systemd (Ubuntu Xenial)
Importance: Medium
Assignee: Dan Streetman (ddstreet)
Status: In Progress
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Xenial)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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:
In Progress
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
[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/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help : https://help.launchpad.net/ListHelp
