netmasks(4) [osf1 man page]

netmasks(4)						     Kernel Interfaces Manual						       netmasks(4)

NAME

       netmasks - DHCP server database

DESCRIPTION

       The  netmasks  file  is employed by joind, the DHCP server, to inform it about any networks having non-standard subnet masks.  This file is
       only needed on those platforms which don't provide a netmasks database, either as a text file or as an NIS map.	Each network whose mask is
       other  than the standard A, B, or C mask should have an entry in this file.  Each entry has two fields: the network and the mask.  The net-
       work may be written with or without zeros. See join.ipaddresses(4) for details.

       This file also supports variable subnetting.  If each subnetwork is further divided into subnetworks with a variable mask, the  subnetworks
       can also appear on the LHS.

   FORMAT
       Blank  lines and lines beginning with "#" are ignored.  Entries are separated from one another by newlines.  Entries consist of two fields:
       the network number (expressed as an IP address), and the network mask expressed as an IP address.

RELATED INFORMATION

       Commands:  joind(8), join.ipaddresses(4).  delim off

																       netmasks(4)

nets(4) 						     Kernel Interfaces Manual							   nets(4)

NAME

       nets - JOIN DHCP server database

DESCRIPTION

       The  nets file is employed by joind, the JOIN DHCP server, to tell it which networks to administer and the ranges of IP addresses available
       for dynamic assignment on each of those networks.

   FORMAT
       Blank lines and lines beginning with the number sign (#) are ignored.  Entries are  separated  from  one  another  by  newline  characters.
       Entries	consist  of  three  fields: the network number (expressed as an IP address), the IP address or name of a host running joind, which
       dynamically configures clients on the network, and a range of available addresses for dynamic allocation to hosts on the net. The range	is
       expressed as a pair of IP addresses separated with a dash (-). There must be no whitespace separating the dash from the IP addresses.

       Several	servers  may  administer  a single network, and a single server may administer several networks. Each network-server pair may have
       several ranges of IP addresses available for dynamic allocation.  The network and server IP addresses do not have to be repeated  for  each
       entry.  A line containing a single field is assumed to be an IP range with the same server and network as the previous entry: a line of two
       fields is assumed to be a server address and IP range with the same network as the preceding entry.

       The ranges of addresses served by each cooperating server must be disjoint.  This condition is checked by the server on startup.

RELATED INFORMATION

       joind(8), join.ipaddresses(4) delim off

																	   nets(4)