DHCPDB.POOL(5)

NAME
dhcpdb.pool - Database of DHCP address pool

DESCRIPTION
dhcpdb.pool is a database which includes parameters managed by DHCP (Dynamic Host Configuration Protocol) server such as IP address and subnet mask and so on. When the server receives request for a new address assignment, it searches this database to select an IP address. If you use manual (static) allocation, you have to specify the Client-id in the address entry.

The server also maintains another database dhcpdb.bind which manages bindings. It is used to keep the combination of a Client-id and an entry of address pool database.

There is an only one entry per line in dhcpdb.pool. But putting backslash(\) means that the entry continues to the next line. And each entry is the set of fields seperated by colon(:).

The first field of the line is an index string, and it appears in the last field of dhcpdb.bind. Meanings of other fields are describe in the next CAPABILITIES.

CAPABILITIES

  Types of Capabilities
There are following types:

bool
    These take "true" or "false". If you specify other value, it means false. (ex. ipfd=true)

str These take string as a value. If string includes a character like colon, it should be put in double quatation marks. (ex. hstn="clapton")

octet
    Integer (8 bit). (cf. 8, -1, 070, 0xff)

short
    Integer (16 bit).

long
    Integer (32 bit).

ip  These take an IP address as its value. Format should be one of a.b.c.d, a.b.c or a.b. (ex. ipad=10.0.0.1)

iplist
    These take list of IP addresses. Each IP address are separated by space. (ex. rout=133.4.31.1 133.4.31.2 133.4.31.3)

ippairs
    These take list of pairs of IP addresses. Each IP address are separated by space and handled in pairs. (ex. strt=133.4.27.0 133.4.31.1 133.4.36.0 133.4.31.1)

mtpt
    These take list of integers (16 bit). Each integer are separated by space. (ex. mtpt=1 2 3 4 6 8)

clid
    These take a client identifier as a value. They have a format like "type:data". "type" is an integer from 0 to 255, which is defined by IANA. "data" is a list of a hexadecimal of 2 figures. Usually, it is MAC address. (ex. clid="1:0x08004600e5d5")

  Codes
Codes are option numbers defined in RFC2132. Refer to RFC2132. If the code '-' means that its field is not option defined in RFC2132.

  Quotation from Other Entry
The rule of quotation from previous entry are following:

•   If a value is not defined yet, it becomes value of the referred entry. If a value is already defined, it is not overwritten.

•   Also a value quoted from other entry is not overwritten. It implies that multiple quotation is permitted. But we recommend not to use same value in multiple quotations to avoid confusion.

•   It is possible to disable quoted value by using "@" mark. Also it seems better not to use many "@" marks to avoid confusion. (ex. snmk@)

FILES
/etc/dhcpdb.bind
    Database about bindings (/var/db/dhcpdb.bind for BSD/OS)
/etc/dhcpdb.pool
    Address Pool database
/etc/dhcpdb.relay
    Database which lists relay agents
/tmp/addrpool_dump
    Dump of the address pool database
/var/run/dhcps.pid
    File which includes process ID (/var/tmp/dhcps.pid for NEWSOS)

SEE ALSO
dhcps(8)

dhcpdb.relay(5)

R. Droms, Dynamic Host Configuration Protocol, RFC2131.

W. Wimer, Clarifications and Extensions for the Bootstrap Protocol, RFC1542.

S. Alexander, R. Droms, DHCP Options and BOOTP Vendor Extensions, RFC2132.

R. Droms, Interoperation Between DHCP and BOOTP, RFC1534.

AUTHOR
Akihiro Tominaga <tomy@sfc.wide.ad.jp>