Option dhcp-client-identifier ignored?

[Leigh Porter]

Folks,

I seem to have a small issue that I hope somebody can help with.

I am running Internet Systems Consortium DHCP Server 4.1-ESV-R4 on Linux and would like to assign a static IP address by dhcp-client-identifier.

This should be easy, yeah? It works on a Mikrotik DHCP server just fine.

Incoming requests have this option 61 present:

          Vendor-rfc1048 Extensions
            Magic Cookie 0x63825363
            DHCP-Message Option 53, length 1: Request
            Client-ID Option 61, length 17: "234514613700286^@"

The logging options I have enabled log it (using binary-to-ascii so its all in decimal):

Sep 20 03:50:40 xen-test dhcpd: client id 0:50:51:52:53:49:52:54:49:51:55:48:48:50:56:54:0

But the DHCP server ignores this option and just assigns a dynamic IP address from the range.

Requests are unicast relayed from a relay server.

The config is below, you'll see a whole load of hosts defined in every possible way (and I tried others besides) just out of desperation ;-)


Here is the server config:

ddns-update-style none;

option domain-name "example.org";
option domain-name-servers ns1.example.org, ns2.example.org;

default-lease-time 600;
max-lease-time 7200;

log-facility local7;
subnet 80.90.100.0 netmask 255.255.255.248 {
}

subnet 82.102.32.0 netmask 255.255.255.0 {

log (info, concat ( "client id ", binary-to-ascii(10,8,":", option dhcp-client-identifier)));
log (info, concat ( "address request ",  binary-to-ascii(10,8,".",  option dhcp-requested-address)));
log (info, concat ( "server id ",  binary-to-ascii(10,8,".", option dhcp-server-identifier)));

log (info, option dhcp-client-identifier);
log (info, option domain-name-servers);
log (info, option dhcp-message-type);

range 82.102.32.2 82.102.32.254;

option domain-name-servers 81.91.192.253;


host leigh {
host-identifier option  dhcp-client-identifier 32:33:34:35:31:34:36:31:33:37:30:30:32:38:36:00;
fixed-address 82.102.32.100;
}

host leigh2 {
host-identifier option dhcp-client-identifier "234514613700286";
fixed-address 82.102.32.101;
}

host leigh21 {
host-identifier option dhcp-client-identifier "\\0234514613700286\\0";
fixed-address 82.102.32.104;
}
host leigh22 {
host-identifier option dhcp-client-identifier "\\0234514613700286";
fixed-address 82.102.32.105;
}
host leigh23 {
host-identifier option dhcp-client-identifier "234514613700286\\0";
fixed-address 82.102.32.106;
}


host leigh3 {
host-identifier option dhcp-client-identifier 0:32:33:34:35:31:34:36:31:33:37:30:30:32:38:36:0;
fixed-address 82.102.32.102;
}

host leigh8 {
host-identifier option dhcp-client-identifier "0:32:33:34:35:31:34:36:31:33:37:30:30:32:38:36:0";
fixed-address 82.102.32.107;
}

host leigh4 {
host-identifier option dhcp-client-identifier  0:50:51:52:53:49:52:54:49:51:55:48:48:50:56:54:0;
fixed-address 82.102.32.103;
}


host leigh41 {
host-identifier option dhcp-client-identifier  50:51:52:53:49:52:54:49:51:55:48:48:50:56:54:0;
fixed-address 82.102.32.108;
}
host leigh42 {
host-identifier option dhcp-client-identifier  0:50:51:52:53:49:52:54:49:51:55:48:48:50:56:54;
fixed-address 82.102.32.109;
}




}



______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20121127/99ef2b4f/attachment.html>