I would like to request added features for DHCP.
In enviroments where there are diskless clients/thin clients, it would be nice if one could add some fing like this:
#set of parameters specific to one particular host
host client.test.net {
hardware ethernet CC:CC:CC:CC:CC:CC;
fixed-address 192.168.1.10;
option host-name "client"; #name of the host (if the fixed address
#doesn't resolve to a simple name)
filename "ofwboot.xcf"; #name of the bootloader or kernel to
#download via tftp
next-server tftpserver.test.net; #which machine to tftp filename from
option root-path "/export/client/root"; #the path on the NFS server.
#typically the client assumes the
#nfsserver = tftpserver
#always-reply-rfc1048 true; #this is needed if your client isn't
#getting the options you set and
#the log says "(non-rfc1048)"
#next68k machines require this to be
#set false
}
#you may paste another "host" entry here for additional clients on this network
so it is possible to boot thin clients with the aid of the DHCP server in the Monowall.
I hope others also find this feature worth including. At the moment we need to have DHCP running on another server in order be able to boot thin clients that need directives to find a server to boot from.
/Klaus
|
Topic: DHCP feature