Dhcpd.conf File Example - Neoware e140 - Thin Client User Manual

DHCP Reference
dhcpd.conf File
Example
318 How Clients Locate the Image Manager Server
virtual disk to the client, the client tries to locate a running Neoware
Image Manager server module by scanning the next IP address and
port in the list sent in DHCP option #132. If the last server in the list
does not answer (or if this list is empty), the client tries to connect to
the IP address that is sent in
siaddrr of DHCP answer), using the default NVDD port UDP 2184.
The option is used by PXE to identify the TFTP server
next-server
that should send the network boot program
client.
Note: If you do not want the client to boot off Neoware Image Man-
ager virtual HDs served by the server that runs TFTP service, you
have to end the value of DHCP option #132 with an exclamation
mark (!). Refer to the chapter "The mPXELdr Configuration File"
on page 251 and to the DHCP Options section for details.
The DHCP option #60 should NOT be set in the DHCP replies. If
you do set this option, please make sure that your PXE server will be
able to serve the
mPXELdr.bin
do so, you may need to rename this file to
depending on your PXE server.
The following is an example
has the IP address: 192.168.0.23, and NVDD servers that have the
addresses: 192.168.0.4,192.168.0.9. (192.168.0.4 is tried first on
port 10000 for client e100-01, then 192.168.0.9 is tried on port 2184,
then 192.168.0.23 (TFTP server) is tried on port 2184).
option domain-name "neoware.com";
option domain-name-servers 192.168.0.12 ;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
option subnet-mask 255.255.255.0;
ddns-update-style ad-hoc;
use-host-decl-names on;
# option 132 is used to store a comma separated list of
# IP addresses that the clients will scan to find
# a running nvdd server module
option option-132 code 132 = text;
DHCP option #66 (field
next-server
mPXELdr.bin
file to your clients efficiently. If you
mPXELdr.0
file for a TFTP server that
dhcpd.conf
to the
(for example),