Logging and matching dhcp-client-identifier

[Ragnar Kjørstad]

Hi

I'd like to configure host entries that match dhcp-client-identifiers
instead of hardware addresses. I've been testing the following
configuration:
host node1 { 
	option dhcp-client-identifier 11:9a:4d:56:34:ea:49:c3:c6:65:47:f2:21:d4:02:00; 
    fixed-address node1; 
    filename "linux-install/pxelinux.0";
}

But with this configuration the dhcp server does not respond to the dhcp
requests, so I guess I got the client identifier wrong. So, next I try
to configure dhcp to reply based on hardware address and then log the
dhcp-client-identifier with the following global statement:

  if exists dhcp-client-identifier {
    log (info, binary-to-ascii (16, 8, ".", option dhcp-client-identifier));
  } else {
    log (info, "No client identifier");
  }

But the server just logs "No client identifier". However, using
tethereal to dump the network traffic I can see that the requests
includes the dhcp-client-identifier:
    Option 97: UUID/GUID-based Client Identifier
        Client Identifier (UUID): 119a4d56-34ea-49c3-c665-47f221d49200


I'm using dhcp-3.0.1-58 from RHEL4U4. I've see there are plenty of
references to dhcp-client-identifier in the mailinglist archive, but yet
no resolution to my problem.

-- 
Ragnar Kjørstad
Software Engineer
Scali - http://www.scali.com
Scaling the Linux Datacenter