network <name> <number> <mask> <access> [<ip> <mask> <ip> <mask>...]

This keyword defines a pool of ip addresses and accosites them with a name.
You can optionally define a gateway using this keyword as well. The access
field determines to what type of clients ip addresses are automatically
allocated to. By applying the mask to the network number, the dhcp server
will then look, incrementally, at each possible address. It will use a
hash table to look up the ip address in the bootptab file and check is the
"dy" flag exists for this entry. If the flag does not exist, the server will
not add the ip address to the pool of availible dynamic ip addresses.

<name> = the text name this pool of ip addresses are associated with.
<number> = a 32-bit network number.
<mask> = the mask to match with the network number.
<access> = flags seperated by |'s with NO spaces. Possible flags are:
        bootp = Only allocate ip addresses in this pool to bootp clients.
        dhcp  = Only allocate ip addresses in this pool to dhcp clients.
        both  = Allows both bootp and dhcp clients to access ip addresses in
                this pool. (bootp,dhcp,both, and mutually exclusive)
        registered = Only allocate ip addresses in this pool to clients whose
                MAC address or client identifier exists in the bootptab.
        roaming = Only allocate ip addresses in this pool to clients who are
                not only in the booptab, but also have a "ro" flag set.
<ip> = ip address of a bootp relay agent, or the ip address of the dhcp
        server which is reading this file.
<mask> = the mask of the bootp relay agent or the dhcp server.


agent <ip> <mask> [<pool1> <pool2>......]

This keyword defines a bootp relay agent or the dhcp server reading the
this configuration file. When sending responses to bootp/dhcp clients, a
comparison is made using the specified mask with the ip address of the client 
and the ip address of the bootp relay agent (or dhcp server). If the 
comparison fails, the server will try to dynamically assign an ip address.
If the server cannot assign a dynamic ip address, the server will fail.
You can also associate pools of dynamic ip addresses with the relay agent 
(or dhcp server) with this keyword. If you wish the server to dynamically
allocate ip addresses to bootp/dhcp clients who exist in the same broadcast
domain (or same wire), then you must use this keyword to associate a pool
of dynamic ip addresses with the server.

<ip> = ip address of the dhcp server or bootp relay agent.
<mask> = mask of the dhcp server or the bootp relay agent.
<poolN> = the name of a pool of dynamic ip addresses that the server can
        dynamically allocate ip addresses from. This name is the same as
        the <name> field from the "network" keyword.


proxy <relay ip> <network1> <mask1>  [<network2> <mask2>.....]

Sometimes relay agents forward bootp/dhcp requests for multiple networks.
This keyword allows you to associate networks in addition to the network
which is implicitly defined with the "agent" keyword.

<relay ip> = ip address of a relay agent or the dhcp server which is reading
        this file. This ip address must have already have been specified
        with the either the "network" keyword, or the "agent" keyword.
<networkN> = the network number of the additional network
<maskN> = The mask of the additional netowrk


flushinterval <seconds>
flushitems <items>

The server saves information to "/etc/bindings"  directory in case the server
restarts. The server will do a flush based on two conditions. The number of
seconds elapsed since the last disk flush, or the number of items which need
to be flushed to disk.

<seconds> = number of seconds
<items> = each client has an entry in the server's database. It is considered
        an "item" which is needed to be flush to disk when ever the 
        information about the client changes (such as, ip address,
        last reply,....).
        Note: If information about the client has changed more than once 
        before a flush to disk. Then it is still considered just 1 item.


garbagecollect <seconds>

The server will periodically walk the table of existing dhcp leases and
and currently allocated dynamic ip addresses. It will check the expiration
of all the ip addresses in the table, and if they have expired  they will
be removed from the table. If the expired address was dynamically allocated,
the server will reinsert the ip address into a LRU list. This keyword 
specifies the number of seconds between the intervals where the server will
check the table.