[pkg-dhcp-devel] Bug#800535: clients try to mount the nfsroot from dhcp-server instead of the next_server, dhclient does not write next-server option
Thomas Lange
lange at informatik.uni-koeln.de
Wed Sep 30 15:00:48 UTC 2015
Package: isc-dhcp-client
Version: 4.3.1-6
In some situations a client tries to mount the nfsroot from the DHCP
server instead of using next_server. This happens if the DHCP server
is not the same as the tftp server and the DHCP server sends the
dhcp_server_identifier. If the initrd was build with dracut, the
kernel tries to mount the nfsroot from the server which is defined by
dhcp_server_identifier.
This patch may be merged with #731244 or you can find more details on
this behaviour there.
The root cause is, that a dhclient does not receive the dhcp option
next-server. next-server is not a dhcp option but instead it is sent
in siaddr field of DHCP message (see RFC 1541).
There's a patch in CentOS which adds the next-server option to the
dhclient script (see https://bugzilla.redhat.com/show_bug.cgi?id=658855)
I would like to see this patch also added into Debian. It cleanly
applies to upstream/4.2.5-P1 but not to the master branch.
I've extracted the file dhcp-4.2.5-next-server.patch from
http://vault.centos.org/7.1.1503/os/Source/SPackages/dhcp-4.2.5-36.el7.centos.src.rpm
and attached it to this mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dhcp-4.2.5-next-server.patch
Type: application/octet-stream
Size: 2077 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-dhcp-devel/attachments/20150930/64653296/attachment.obj>
-------------- next part --------------
--
regards Thomas
More information about the pkg-dhcp-devel
mailing list