Re: Assigning static addresses based on Client ID?

[Shawn Mamros <[e-mail]>]

>It works either way.   If you want to match the client ID, declare the
>host as follows:
>
>host foo
>  option dhcp-client-identifier 1:8:0:2b:4c:29:5d  
>  fixed-address confusia-3.fugue.com;
>
>This assumes that the client identifier is an ethernet address
>declared according to the latest draft on DHCP options.   Older
>versions of FTP software's DHCP client use fairly long ASCII text
>client identifiers.   Unfortunately, these must also be entered as
>binary data.

Our DHCP client also allows one to specify their own custom client ID
string, one that doesn't have to be tied to the hardware address at all.
(Of course, you do need to make sure all your clients have their own
unique string...)

To handle one of these, you will have to translate the ASCII string
into the appropriate binary representation.  In other words, if you
had a client whose client ID was set to "Client-1", it would be
represented in the syntax above as:

host foo
  option dhcp-client-identifier 43:6c:69:65:6e:74:2d:31
  fixed-address dhcp-client-1.ftp.com;

(The conversion could probably be done using a script with your favorite
scripting language, if you like...)

If you don't set a custom client ID, then the "long ASCII text" string
which Ted refers to is an ASCII representation of the hardware address,
in the form "cid-02608CD88398" (replace 02608CD88398 with your own
hardware address).  Future releases will be changing this to the same
hardware type/binary hardware address format used by most other vendors.
(I had wanted to change our format some time ago, but couldn't due to
backwards compatibility problems with older versions of our own DHCP server.)

Hope this helps...

-Shawn Mamros
E-mail to: [e-mail]