+++ This bug was initially created as a clone of Bug #1058674 +++

Description of problem:

Intel Boot Agent:

sends option number 97 and not 61 as UUID in DHCPDISCOVER packet, which leads not to recognizing host declaration with 'fixed-address' according to 'dhcp-client-identifier' parameter (in case we don't want to filter according to mac address, resp. 'hardware ethernet <mac>' parameter):

host bla {
...
option dhcp-client-identifier <UUID>;
}


Actual results:

filtering according to UUID/'dhcp-client-identifier' sent by bootp clients doesn't work in case the boot agent's pxe code doesn't set option number 61, but only 97


Expected results:

dhcpd should support beside option 61 also 97 according to RFC specifications (see more info/links to related RFCs in 'Additional info' section)


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RFCs for individual options:

http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-parameters.xhtml

related rfc and text to option # 97:

http://tools.ietf.org/html/rfc4578#section-2.3
http://tools.ietf.org/html/rfc4578#section-4

related rfc to option #61:

http://tools.ietf.org/html/rfc2132#page-30

pxe specification:

http://www.pix.net/software/pxeboot/archive/pxespec.pdf

you can find there a table with all pxe options, where 61 and 97 are mentioned as "Client machine identifier (UUID)":

2.3 DHCP Tags used for PXE Protocol ..........................................................................................18

There is a mention under the table:

"The Client UUID field specifies a universally unique ID (UUID), retrieved from the client system. The client must have a UUID and must report it in tag #97 and #61."

Also see:

"Table 2-2 DHCPDISCOVER Packet to DHCP/Proxy DHCP Server"

which mentions the option # 97 in dhcpdiscover packet.


--- Additional comment from Jiri Popelka on 2014-12-16 19:13:27 CET ---

Testing should be as simple as putting for example
send pxe-client-id = 0:4f:6c:98:cc:74:d5:e2:11:80:28:0:0:50:be:c8:4b;
into /etc/dhcp/dhclient.conf and running dhclient.

Once the server provides a address to client and writes the lease into
/var/lib/dhcpd/dhcpd.leases
you can see that the lease in that file contains
uid "\000Ol\230\314t\325\342\021\200(\000\000P\276\310J";
which is the specified pxe-client-id (see string description in dhcp-eval for the \xxx explanation).

You can also define a 'fixed address' for the client with (dhcpd.conf):
host pixi {
  option pxe-client-id 0 4f:6c:98:cc:74:d5:e2:11:80:28:0:0:50:be:c8:4b;
  fixed-address 1.2.3.123;
}

--- Additional comment from Jiri Popelka on 2014-12-17 13:45:42 CET ---

http://pkgs.devel.redhat.com/cgit/rpms/dhcp/commit/?h=rhel-6.7&id=d32f9427a422c8d4e8740afe07b7c518b8e5b183