Antw: Re: Custom Options in /etc/dhcpd.conf

   *** From dhcp-server -- To unsubscribe, see the end of this message. ***


Hey,

We are also using PXE and had some Problems with old PXE Clients. They
didn't use the options about another TFTP server other then the DHCP
Server itself. So I am sending them the ServerIdentifier of my TFTP
Server and PXE is working.

rg
Tom

>>> ws+ml.dhcp-server@xxxxxxxxxxxxxxx 22.01.2003 12:12:53 >>>
   *** From dhcp-server -- To unsubscribe, see the end of this message.
***


> i'm encountering a problem specifying custom options 43, 60, 128,
129
> and 135 in ISC's dhcp-Server version 3.0pl1.
> 
> I'm going to boot clients with PXE-Prom intending to redirect them to
a
> BootP/TFTP Server.

[next time please put your problem in concrete terms]

Below you'll find an excerpt from our dhcpd.conf and what I did to
make things work.  With luck this will already solve your problem.
I don't know if this is the best way to configure the task at hand
but it's working at our site without problems.  We don't use '135'.

First of all, you have to declare the options needed in the
appropriate option spaces

site options:
-------------
option space PXE;
        site-option-space "PXE";
        option PXE.boot-control-reply code 128 = text;
        option PXE.boot-control-redirection code 129 = string;

vendor options:
---------------
option space PXEClient;
        vendor-option-space PXEClient;
        option PXEClient.vendor-specific-info code 43 = string;
        option PXEClient.class-identifier code 60 = text;

Then set values in scopes

 option PXEClient.vendor-specific-info
06:01:07:08:07:ff:f0:01:XX:XX:XX:XX:09:18:ff:f0:15:50:72:6f:64:61:63:74:61:20:42:6f:6f:74:20:43:6f:6e:74:72:6f:6c:0a:04:00:41:41:41:47:03:00:00:00:ff;
 option PXEClient.class-identifier "PXEClient";
 option PXE.boot-control-reply "BcReP2";

 option PXE.boot-control-redirection
42:63:53:72:56:XX:XX:XX:XX:07:d0:YY:YY:YY:YY;
OR
 option PXE.boot-control-redirection 42:63:53:72:56:XX:XX:XX:XX:07:d0;
 next-server ZZZ.ZZZ.ZZZ.ZZZ;
 filename "PXEDISK";

with ZZZ.ZZZ.ZZZ.ZZZ = OSD server IP address and XX.XX.XX.XX same in
hex
YY.YY.YY.YY gateway IP in hex (if client and server are in different
nets)

next-server and OSD server are the same at our place and I don't know
if it's possible to actually use different addresses.

Cheers, ws

-----------------------------------------------------------------------
List Archives : http://www.isc.org/ml-archives/dhcp-server/ 
Unsubscribe   : http://www.isc.org/dhcp-lists.html    
-or-          : mailto:dhcp-server-request@xxxxxxx?Subject=unsubscribe 

-----------------------------------------------------------------------


-----------------------------------------------------------------------
List Archives : http://www.isc.org/ml-archives/dhcp-server/
Unsubscribe   : http://www.isc.org/dhcp-lists.html    
-or-          : mailto:dhcp-server-request@xxxxxxx?Subject=unsubscribe  
-----------------------------------------------------------------------