SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG
DONATE


YUM REPOSITORY

 
 

MAN page from Mandrake 9.X dhcp-server-3.0-1.rc12.2mdk.i586.rpm

dhcpd-options

Section: File Formats (5)
Index 

NAME

dhcp-options - Dynamic Host Configuration Protocol options 

DESCRIPTION

The Dynamic Host Configuration protocol allows the client to receiveoptionsfrom the DHCP server describing the network configuration and variousservices that are available on the network. When configuringdhcpd(8)ordhclient(8) ,options must often be declared. The syntax for declaring options,and the names and formats of the options that can be declared, aredocumented here. 

REFERENCE: OPTION STATEMENTS

DHCP option statements always start with the optionkeyword, followed by an option name, followed by option data. Theoption names and data formats are described below. It is notnecessary to exhaustively specify all DHCP options - only thoseoptions which are needed by clients must be specified.

Option data comes in a variety of formats, as defined below:

Theip-addressdata type can be entered either as an explicit IPaddress (e.g., 239.254.197.10) or as a domain name (e.g.,haagen.isc.org). When entering a domain name, be sure that thatdomain name resolves to a single IP address.

Theint32data type specifies a signed 32-bit integer. The uint32data type specifies an unsigned 32-bit integer. The int16anduint16data types specify signed and unsigned 16-bit integers. The int8anduint8data types specify signed and unsigned 8-bit integers.Unsigned 8-bit integers are also sometimes referred to as octets.

Thetextdata type specifies an NVT ASCII string, which must beenclosed in double quotes - for example, to specify a root-pathoption, the syntax would be

option root-path "10.0.1.4:/var/tmp/rootfs";

Thedomain-namedata type specifies a domain name, which must notenclosed in double quotes. This data type is not used for anyexisting DHCP options. The domain name is stored just as if it werea text option.

Theflagdata type specifies a boolean value. Booleans can be either true orfalse (or on or off, if that makes more sense to you).

Thestringdata type specifies either an NVT ASCII stringenclosed in double quotes, or a series of octets specified inhexadecimal, separated by colons. For example:

  option dhcp-client-identifier "CLIENT-FOO";or  option dhcp-client-identifier 43:4c:49:45:54:2d:46:4f:4f;
 

SETTING OPTION VALUES USING EXPRESSIONS

Sometimes it's helpful to be able to set the value of a DHCP optionbased on some value that the client has sent. To do this, you canuse expression evaluation. The dhcp-eval(5)manual page describes how to write expressions. To assign the resultof an evaluation to an option, define the option as follows:
  option my-option = expression ;

For example:

  option hostname = binary-to-ascii (16, 8, "-",                                     substring (hardware, 1, 6));
 

STANDARD DHCP OPTIONS

The documentation for the various options mentioned below is takenfrom the latest IETF draft document on DHCP options. Options notlisted below may not yet be implemented, but it is possible to usesuch options by defining them in the configuration file. Please seethe DEFINING NEW OPTIONS heading later in this document for moreinformation.

Some of the options documented here are automatically generated bythe DHCP server or by clients, and cannot be configured by the user.The value of such an option can be used in the configuration file ofthe receiving DHCP protocol agent (server or client), for example inconditional expressions. However, the value of the option cannot beused in the configuration file of the sending agent, because the valueis determined only after the configuration file has beenprocessed. In the following documentation, such options will be shownas "not user configurable"

The standard options are:

option all-subnets-local flag;

This option specifies whether or not the client may assume that allsubnets of the IP network to which the client is connected use thesame MTU as the subnet of that network to which the client isdirectly connected. A value of true indicates that all subnets sharethe same MTU. A value of false means that the client should assume thatsome subnets of the directly connected network may have smaller MTUs.

option arp-cache-timeout uint32;

This option specifies the timeout in seconds for ARP cache entries.

option bootfile-name text;

This option is used to identify a bootstrap file. If supported by theclient, it should have the same effect as the filenamedeclaration. BOOTP clients are unlikely to support this option. SomeDHCP clients will support it, and others actually require it.

option boot-size uint16;

This option specifies the length in 512-octet blocks of the defaultboot image for the client.

option broadcast-address ip-address;

This option specifies the broadcast address in use on the client'ssubnet. Legal values for broadcast addresses are specified insection 3.2.1.3 of STD 3 (RFC1122).

option cookie-servers ip-address [, ip-address...];

The cookie server option specifies a list of RFC 865 cookieservers available to the client. Servers should be listed in orderof preference.

option default-ip-ttl uint8;

This option specifies the default time-to-live that the client shoulduse on outgoing datagrams.

option default-tcp-ttl uint8;

This option specifies the default TTL that the client should use whensending TCP segments. The minimum value is 1.

option dhcp-client-identifier string;

This option can be used to specify the a DHCP client identifier in ahost declaration, so that dhcpd can find the host record by matchingagainst the client identifier.

Please be aware that some DHCP clients, when configured with clientidentifiers that are ASCII text, will prepend a zero to the ASCIItext. So you may need to write:

        option dhcp-client-identifier "\0foo";rather than:        option dhcp-client-identifier "foo";

option dhcp-lease-time uint32;

This option is used in a client request (DHCPDISCOVER or DHCPREQUEST)to allow the client to request a lease time for the IP address. In aserver reply (DHCPOFFER), a DHCP server uses this option to specifythe lease time it is willing to offer.

This option is not directly user configurable in the server; refer to themax-lease-time and default-lease-time server options indhcpd.conf(5).

option dhcp-max-message-size uint16;

This option, when sent by the client, specifies the maximum size ofany response that the server sends to the client. When specified onthe server, if the client did not send a dhcp-max-message-size option,the size specified on the server is used. This works for BOOTP aswell as DHCP responses.

option dhcp-message text;

This option is used by a DHCP server to provide an error message to aDHCP client in a DHCPNAK message in the event of a failure. A clientmay use this option in a DHCPDECLINE message to indicate why theclient declined the offered parameters.

This option is not user configurable.

option dhcp-message-type uint8;

This option, sent by both client and server, specifies the type of DHCPmessage contained in the DHCP packet. Possible values (taken directly fromRFC2132) are:

             1     DHCPDISCOVER             2     DHCPOFFER             3     DHCPREQUEST             4     DHCPDECLINE             5     DHCPACK             6     DHCPNAK             7     DHCPRELEASE             8     DHCPINFORM               

This option is not user configurable.

option dhcp-option-overload uint8;

This option is used to indicate that the DHCP 'sname' or 'file'fields are being overloaded by using them to carry DHCP options. ADHCP server inserts this option if the returned parameters willexceed the usual space allotted for options.

If this option is present, the client interprets the specifiedadditional fields after it concludes interpretation of the standardoption fields.

Legal values for this option are:

             1     the 'file' field is used to hold options             2     the 'sname' field is used to hold options             3     both fields are used to hold options                        

This option is not user configurable.

option dhcp-parameter-request-list uint16;

This option, when sent by the client, specifies which options theclient wishes the server to return. Normally, in the ISC DHCPclient, this is done using the request statement. If thisoption is not specified by the client, the DHCP server will normallyreturn every option that is valid in scope and that fits into thereply. When this option is specified on the server, the serverreturns the specified options. This can be used to force a client totake options that it hasn't requested, and it can also be used totailor the response of the DHCP server for clients that may need amore limited set of options than those the server would normallyreturn.

option dhcp-rebinding-time uint32;

This option specifies the number of seconds from the time a client getsan address until the client transitions to the REBINDING state.

This option is not user configurable.

option dhcp-renewal-time uint32;

This option specifies the number of seconds from the time a client getsan address until the client transitions to the RENEWING state.

This option is not user configurable.

option dhcp-requested-address ip-address;

This option is used by the client in a DHCPDISCOVER torequest that a particular IP address be assigned.

This option is not user configurable.

option dhcp-server-identifier ip-address;

This option is used in DHCPOFFER and DHCPREQUEST messages, and mayoptionally be included in the DHCPACK and DHCPNAK messages. DHCPservers include this option in the DHCPOFFER in order to allow theclient to distinguish between lease offers. DHCP clients use thecontents of the 'server identifier' field as the destination addressfor any DHCP messages unicast to the DHCP server. DHCP clients alsoindicate which of several lease offers is being accepted by includingthis option in a DHCPREQUEST message.

The value of this option is the IP address of the server.

This option is not directly user configurable. See the server-identifier server option indhcpd.conf(5).

option domain-name text;

This option specifies the domain name that client should use whenresolving hostnames via the Domain Name System.

option domain-name-servers ip-address [, ip-address...];

The domain-name-servers option specifies a list of Domain Name System(STD 13, RFC 1035) name servers available to the client. Serversshould be listed in order of preference.

option extensions-path text;

This option specifies the name of a file containing additional optionsto be interpreted according to the DHCP option format as specified inRFC2132.

option finger-server ip-address [,ip-address... ];

The Finger server option specifies a list of Finger available to theclient. Servers should be listed in order of preference.

option font-servers ip-address [, ip-address...];

This option specifies a list of X Window System Font servers availableto the client. Servers should be listed in order of preference.

option host-name string;

This option specifies the name of the client. The name may or maynot be qualified with the local domain name (it is preferable to usethe domain-name option to specify the domain name). See RFC 1035 forcharacter set restrictions. This option is only honored bydhclient-script(8)if the hostname for the client machine is not set.

option ieee802-3-encapsulation flag;

This option specifies whether or not the client should use EthernetVersion 2 (RFC 894) or IEEE 802.3 (RFC 1042) encapsulation if theinterface is an Ethernet. A value of false indicates that the clientshould use RFC 894 encapsulation. A value of true means that the clientshould use RFC 1042 encapsulation.

option ien116-name-servers ip-address [, ip-address...];

The ien116-name-servers option specifies a list of IEN 116 name serversavailable to the client. Servers should be listed in order ofpreference.

option impress-servers ip-address [, ip-address...];

The impress-server option specifies a list of Imagen Impress serversavailable to the client. Servers should be listed in order ofpreference.

option interface-mtu uint16;

This option specifies the MTU to use on this interface. The minimumlegal value for the MTU is 68.

option ip-forwarding flag;

This option specifies whether the client should configure its IPlayer for packet forwarding. A value of false means disable IPforwarding, and a value of true means enable IP forwarding.

option irc-server ip-address [,ip-address... ];

The IRC server option specifies a list of IRC available to theclient. Servers should be listed in order of preference.

option log-servers ip-address [, ip-address...];

The log-server option specifies a list of MIT-LCS UDP log serversavailable to the client. Servers should be listed in order ofpreference.

option lpr-servers ip-address [, ip-address...];

The LPR server option specifies a list of RFC 1179 line printerservers available to the client. Servers should be listed in orderof preference.

option mask-supplier flag;

This option specifies whether or not the client should respond tosubnet mask requests using ICMP. A value of false indicates that theclient should not respond. A value of true means that the client shouldrespond.

option max-dgram-reassembly uint16;

This option specifies the maximum size datagram that the clientshould be prepared to reassemble. The minimum legal value is576.

option merit-dump text;

This option specifies the path-name of a file to which the client'score image should be dumped in the event the client crashes. Thepath is formatted as a character string consisting of characters fromthe NVT ASCII character set.

option mobile-ip-home-agent ip-address [, ip-address... ];

This option specifies a list of IP addresses indicating mobile IPhome agents available to the client. Agents should be listed inorder of preference, although normally there will be only one suchagent.

option nds-context string;

The nds-context option specifies the name of the initial NetwareDirectory Service for an NDS client.

option nds-servers ip-address [, ip-address... ];

The nds-servers option specifies a list of IP addresses of NDS servers.

option nds-tree-name string;

The nds-tree-name option specifies NDS tree name that the NDS clientshould use.

option netbios-dd-server ip-address [, ip-address...];

The NetBIOS datagram distribution server (NBDD) option specifies alist of RFC 1001/1002 NBDD servers listed in order of preference.

option netbios-name-servers ip-address [, ip-address...];

The NetBIOS name server (NBNS) option specifies a list of RFC1001/1002 NBNS name servers listed in order of preference. NetBIOSName Service is currently more commonly referred to as WINS. WINSservers can be specified using the netbios-name-servers option.

option netbios-node-type uint8;

The NetBIOS node type option allows NetBIOS over TCP/IP clients whichare configurable to be configured as described in RFC 1001/1002. Thevalue is specified as a single octet which identifies the client type.

Possible node types are:

1
B-node: Broadcast - no WINS
2
P-node: Peer - WINS only.
4
M-node: Mixed - broadcast, then WINS
8
H-node: Hybrid - WINS, then broadcast

option netbios-scope string;

The NetBIOS scope option specifies the NetBIOS over TCP/IP scopeparameter for the client as specified in RFC 1001/1002. See RFC1001,RFC1002, and RFC1035 for character-set restrictions.

option nis-domain text;

This option specifies the name of the client's NIS (Sun NetworkInformation Services) domain. The domain is formatted as a characterstring consisting of characters from the NVT ASCII character set.

option nis-servers ip-address [, ip-address...];

This option specifies a list of IP addresses indicating NIS serversavailable to the client. Servers should be listed in order ofpreference.

option nisplus-domain text;

This option specifies the name of the client's NIS+ domain. Thedomain is formatted as a character string consisting of charactersfrom the NVT ASCII character set.

option nisplus-servers ip-address [, ip-address...];

This option specifies a list of IP addresses indicating NIS+ serversavailable to the client. Servers should be listed in order ofpreference.

option nntp-server ip-address [,ip-address... ];

The NNTP server option specifies a list of NNTP available to theclient. Servers should be listed in order of preference.

option non-local-source-routing flag;

This option specifies whether the client should configure its IPlayer to allow forwarding of datagrams with non-local source routes(see Section 3.3.5 of [4] for a discussion of this topic). A valueof false means disallow forwarding of such datagrams, and a value of truemeans allow forwarding.

option ntp-servers ip-address [, ip-address...];

This option specifies a list of IP addresses indicating NTP (RFC 1035)servers available to the client. Servers should be listed in orderof preference.

option nwip-domain string;

The name of the NetWare/IP domain that a NetWare/IP client shoulduse.

option nwip-suboptions string;

A sequence of suboptions for NetWare/IP clients - see RFC2242 fordetails. Normally this option is set by specifying specificNetWare/IP suboptions - see the NETWARE/IP SUBOPTIONS section for moreinformation.

option path-mtu-aging-timeout uint32;

This option specifies the timeout (in seconds) to use when aging PathMTU values discovered by the mechanism defined in RFC 1191.

option path-mtu-plateau-table uint16 [, uint16...];

This option specifies a table of MTU sizes to use when performingPath MTU Discovery as defined in RFC 1191. The table is formatted asa list of 16-bit unsigned integers, ordered from smallest to largest.The minimum MTU value cannot be smaller than 68.

option perform-mask-discovery flag;

This option specifies whether or not the client should perform subnetmask discovery using ICMP. A value of false indicates that the clientshould not perform mask discovery. A value of true means that theclient should perform mask discovery.

option policy-filter ip-address ip-address                  [, ip-address ip-address...];

This option specifies policy filters for non-local source routing.The filters consist of a list of IP addresses and masks which specifydestination/mask pairs with which to filter incoming source routes.

Any source routed datagram whose next-hop address does not match oneof the filters should be discarded by the client.

See STD 3 (RFC1122) for further information.

option pop-server ip-address [, ip-address... ];

The POP3 server option specifies a list of POP3 available to theclient. Servers should be listed in order of preference.

option resource-location-servers ip-address
                              [ip-address...];

This option specifies a list of RFC 887 Resource Locationservers available to the client. Servers should be listed in orderof preference.

option root-path text;

This option specifies the path-name that contains the client's rootdisk. The path is formatted as a character string consisting ofcharacters from the NVT ASCII character set.

option router-discovery flag;

This option specifies whether or not the client should solicitrouters using the Router Discovery mechanism defined in RFC 1256.A value of false indicates that the client should not performrouter discovery. A value of true means that the client should performrouter discovery.

option router-solicitation-address ip-address;

This option specifies the address to which the client should transmitrouter solicitation requests.

option routers ip-address [, ip-address...];

The routers option specifies a list of IP addresses for routers on theclient's subnet. Routers should be listed in order of preference.

option slp-directory-agent boolean ip-address[, ip-address... ];

This option specifies two things: the IP addresses of one or moreService Location Protocol Directory Agents, and whether the use ofthese addresses is mandatory. If the initial boolean value is true,the SLP agent should just use the IP addresses given. If the valueis false, the SLP agent may additionally do active or passivemulticast discovery of SLP agents (see RFC2165 for details).

Please note that in this option and the slp-service-scope option, theterm "SLP Agent" is being used to refer to a Service Location Protocolagent running on a machine that is being configured using the DHCPprotocol.

Also, please be aware that some companies may refer to SLP as NDS.If you have an NDS directory agent whose address you need toconfigure, the slp-directory-agent option should work.

option slp-service-scope boolean text;

The Service Location Protocol Service Scope Option specifies twothings: a list of service scopes for SLP, and whether the use of thislist is mandatory. If the initial boolean value is true, the SLPagent should only use the list of scopes provided in this option;otherwise, it may use its own static configuration in preference tothe list provided in this option.

The text string should be a comma-separated list of scopes that theSLP agent should use. It may be omitted, in which case the SLP Agentwill use the aggregated list of scopes of all directory agents knownto the SLP agent.

option smtp-server ip-address [,ip-address... ];

The SMTP server option specifies a list of SMTP servers available tothe client. Servers should be listed in order of preference.

option static-routes ip-address ip-address                  [, ip-address ip-address...];

This option specifies a list of static routes that the client shouldinstall in its routing cache. If multiple routes to the samedestination are specified, they are listed in descending order ofpriority.

The routes consist of a list of IP address pairs. The first addressis the destination address, and the second address is the router forthe destination.

The default route (0.0.0.0) is an illegal destination for a staticroute. To specify the default route, use theroutersoption. Also, please note that this option is not intended forclassless IP routing - it does not include a subnet mask. Sinceclassless IP routing is now the most widely deployed routing standard,this option is virtually useless, and is not implemented by any of thepopular DHCP clients, for example the Microsoft DHCP client.

option streettalk-directory-assistance-server ip-address                                           [, ip-address...];

The StreetTalk Directory Assistance (STDA) server option specifies alist of STDA servers available to the client. Servers should belisted in order of preference.

option streettalk-server ip-address [, ip-address... ];

The StreetTalk server option specifies a list of StreetTalk serversavailable to the client. Servers should be listed in order ofpreference.

option subnet-mask ip-address;

The subnet mask option specifies the client's subnet mask as per RFC950. If no subnet mask option is provided anywhere in scope, as alast resort dhcpd will use the subnet mask from the subnet declarationfor the network on which an address is being assigned. However,anysubnet-mask option declaration that is in scope for the address beingassigned will override the subnet mask specified in the subnetdeclaration.

option subnet-selection string;

Sent by the client if an address is required in a subnet other than the onethat would normally be selected (based on the relaying address of theconnected subnet the request is obtained from). See RFC3011. Note that theoption number used by this server is 118; this has not always been thedefined number, and some clients may use a different value. Use of thisoption should be regarded as slightly experimental!

This option is not user configurable in the server.

option swap-server ip-address;

This specifies the IP address of the client's swap server.

option tcp-keepalive-garbage flag;

This option specifies the whether or not the client should send TCPkeepalive messages with a octet of garbage for compatibility witholder implementations. A value of false indicates that a garbage octetshould not be sent. A value of true indicates that a garbage octetshould be sent.

option tcp-keepalive-interval uint32;

This option specifies the interval (in seconds) that the client TCPshould wait before sending a keepalive message on a TCP connection.The time is specified as a 32-bit unsigned integer. A value of zeroindicates that the client should not generate keepalive messages onconnections unless specifically requested by an application.

option tftp-server-name text;

This option is used to identify a TFTP server and, if supported by theclient, should have the same effect as the server-namedeclaration. BOOTP clients are unlikely to support this option.Some DHCP clients will support it, and others actually require it.

option time-offset int32;

The time-offset option specifies the offset of the client's subnet inseconds from Coordinated Universal Time (UTC).

option time-servers ip-address [, ip-address...];

The time-server option specifies a list of RFC 868 time serversavailable to the client. Servers should be listed in order ofpreference.

option trailer-encapsulation flag;

This option specifies whether or not the client should negotiate theuse of trailers (RFC 893 [14]) when using the ARP protocol. A valueof false indicates that the client should not attempt to use trailers. Avalue of true means that the client should attempt to use trailers.

option uap-servers text;

This option specifies a list of URLs, each pointing to a userauthentication service that is capable of processing authenticationrequests encapsulated in the User Authentication Protocol (UAP). UAPservers can accept either HTTP 1.1 or SSLv3 connections. If the listincludes a URL that does not contain a port component, the normaldefault port is assumed (i.e., port 80 for http and port 443 forhttps). If the list includes a URL that does not contain a pathcomponent, the path /uap is assumed. If more than one URL isspecified in this list, the URLs are separated by spaces.

option user-class string;

This option is used by some DHCP clients as a way for users tospecify identifying information to the client. This can be used in asimilar way to the vendor-class-identifier option, but the value ofthe option is specified by the user, not the vendor. Most recentDHCP clients have a way in the user interface to specify the value forthis identifier, usually as a text string.

option vendor-class-identifier string;

This option is used by some DHCP clients to identify the vendortype and possibly the configuration of a DHCP client. The informationis a string of bytes whose contents are specific to the vendor and arenot specified in a standard. To see what vendor class identifier aclients are sending, you can write the following in your DHCP serverconfiguration file:

set vendor-class option vendor-class-identifier;

This will result in all entries in the DHCP server lease database filefor clients that sent vendor-class-identifier options having a setstatement that looks something like this:

set vendor-class "SUNW.Ultra-5_10";

The vendor-class-identifier option is normally used by the DHCP serverto determine the options that are returned in thevendor-encapsulated-optionsoption. Please see the VENDOR ENCAPSULATED OPTIONS section of thedhcpd.conf manual page for further information.

option vendor-encapsulated-options string;

The vendor-encapsulated-options option can contain either asingle vendor-specific value or one or more vendor-specificsuboptions. This option is not normally specified in the DHCP serverconfiguration file - instead, a vendor class is defined for eachvendor, vendor class suboptions are defined, values for thosesuboptions are defined, and the DHCP server makes up a response onthat basis.

Some default behaviours for well-known DHCP client vendors (currently,the Microsoft Windows 2000 DHCP client) are configured automatically,but otherwise this must be configured manually - see the VENDORENCAPSULATED OPTIONS section of the dhcpd.conf manual page fordetails.

option www-server ip-address [,ip-address... ];

The WWW server option specifies a list of WWW available to theclient. Servers should be listed in order of preference.

option x-display-manager ip-address [, ip-address...];

This option specifies a list of systems that are running the X WindowSystem Display Manager and are available to the client. Addressesshould be listed in order of preference.

 

RELAY AGENT INFORMATION OPTION

An IETF draft, draft-ietf-dhc-agent-options-11.txt, defines a seriesof encapsulated options that a relay agent can add to a DHCP packetwhen relaying it to the DHCP server. The server can then makeaddress allocation decisions (or whatever other decisions it wants)based on these options. The server also returns these options in anyreplies it sends through the relay agent, so that the relay agent canuse the information in these options for delivery or accountingpurposes.

The current draft defines two options. To referencethese options in the dhcp server, specify the option space name,"agent", followed by a period, followed by the option name. It isnot normally useful to define values for these options in the server,although it is permissible. These options are not supported in theclient.

option agent.circuit-id string;

The circuit-id suboption encodes an agent-local identifier of thecircuit from which a DHCP client-to-server packet was received. It isintended for use by agents in relaying DHCP responses back to theproper circuit. The format of this option is currently defined to bevendor-dependent, and will probably remain that way, although thecurrent draft allows for for the possibility of standardizing theformat in the future.

option agent.remote-id string;

The remote-id suboption encodes information about the remote host endof a circuit. Examples of what it might contain include caller IDinformation, username information, remote ATM address, cable modem ID,and similar things. In principal, the meaning is not well-specified,and it should generally be assumed to be an opaque object that isadministratively guaranteed to be unique to a particular remote end ofa circuit.

 

THE CLIENT FQDN SUBOPTIONS

The Client FQDN option, currently defined in the Internet Draftdraft-ietf-dhc-fqdn-option-00.txt is not a standard yet, but is insufficiently wide use already that we have implemented it. Due tothe complexity of the option format, we have implemented it as asuboption space rather than a single option. In general thisoption should not be configured by the user - instead it should beused as part of an automatic DNS update system.

option fqdn.no-client-update flag;

When the client sends this, if it is true, it means the client will notattempt to update its A record. When sent by the server to the client,it means that the client should not update its own A record.

option fqdn.server-update flag;

When the client sends this to the server, it is requesting that the serverupdate its A record. When sent by the server, it means that the serverhas updated (or is about to update) the client's A record.

option fqdn.encoded flag;

If true, this indicates that the domain name included in the option isencoded in DNS wire format, rather than as plain ASCII text. The clientnormally sets this to false if it doesn't support DNS wire format in theFQDN option. The server should always send back the same value that theclient sent. When this value is set on the configuration side, it controlsthe format in which the fqdn.fqdn suboption is encoded.

option fqdn.rcode1 flag;

option fqdn.rcode2 flag;

These options specify the result of the updates of the A and PTR records,respectively, and are only sent by the DHCP server to the DHCP client.The values of these fields are those defined in the DNS protocol specification.

option fqdn.fqdn text;

Specifies the domain name that the client wishes to use. This can be afully-qualified domain name, or a single label. If there is no trailinggenerally update that name in some locally-defined domain.

option fqdn.hostname --never set--;

This option should never be set, but it can be read back using the optionand config-option operators in an expression, in which case it returnsthe first label in the fqdn.fqdn suboption - for example, ifthe value of fqdn.fqdn is "foo.example.com.", then fqdn.hostnamewill be "foo".

option fqdn.domainname --never set--;

This option should never be set, but it can be read back using the optionand config-option operators in an expression, in which case it returnsall labels after the first label in the fqdn.fqdn suboption - forexample, if the value of fqdn.fqdn is "foo.example.com.",then fqdn.hostname will be "example.com.". If this suboption valueis not set, it means that an unqualified name was sent in the fqdn option,or that no fqdn option was sent at all.

If you wish to use any of these suboptions, we strongly recommend that yourefer to the Client FQDN option draft (or standard, when it becomes astandard) - the documentation here is sketchy and incomplete in comparison,and is just intended for reference by people who already understand theClient FQDN option specification. 

THE NETWARE/IP SUBOPTIONS

RFC2242 defines a set of encapsulated options for Novell NetWare/IPclients. To use these options in the dhcp server, specify the optionspace name, "nwip", followed by a period, followed by the option name.The following options can be specified:

option nwip.nsq-broadcast flag;

If true, the client should use the NetWare Nearest Server Query tolocate a NetWare/IP server. The behaviour of the Novell client ifthis suboption is false, or is not present, is not specified.

option nwip.preferred-dss ip-address [, ip-address... ];

This suboption specifies a list of up to five IP addresses, each ofwhich should be the IP address of a NetWare Domain SAP/RIP server(DSS).

option nwip.nearest-nwip-server ip-address
                             [, ip-address...];

This suboption specifies a list of up to five IP addresses, each ofwhich should be the IP address of a Nearest NetWare IP server.

option nwip.autoretries uint8;

Specifies the number of times that a NetWare/IP client should attemptto communicate with a given DSS server at startup.

option nwip.autoretry-secs uint8;

Specifies the number of seconds that a Netware/IP client should waitbetween retries when attempting to establish communications with a DSSserver at startup.

option nwip.nwip-1-1 uint8;

If true, the NetWare/IP client should support NetWare/IP version 1.1compatibility. This is only needed if the client will be contactingNetware/IP version 1.1 servers.

option nwip.primary-dss ip-address;

Specifies the IP address of the Primary Domain SAP/RIP Service server(DSS) for this NetWare/IP domain. The NetWare/IP administrationutility uses this value as Primary DSS server when configuring asecondary DSS server.

 

DEFINING NEW OPTIONS

The Internet Software Consortium DHCP client and server provide thecapability to define new options. Each DHCP option has a name, acode, and a structure. The name is used by you to refer to theoption. The code is a number, used by the DHCP server and client torefer to an option. The structure describes what the contents of anoption looks like.

To define a new option, you need to choose a name for it that is notin use for some other option - for example, you can't use "host-name"because the DHCP protocol already defines a host-name option, which isdocumented earlier in this manual page. If an option name doesn'tappear in this manual page, you can use it, but it's probably a goodidea to put some kind of unique string at the beginning so you can besure that future options don't take your name. For example, youmight define an option, "local-host-name", feeling some confidencethat no official DHCP option name will ever start with "local".

Once you have chosen a name, you must choose a code. For site-localoptions, all codes between 128 and 254 are reserved for DHCP options,so you can pick any one of these. In practice, some vendors haveinterpreted the protocol rather loosely and have used option codevalues greater than 128 themselves. There's no real way to avoidthis problem, but it's not likely to cause too much trouble inpractice.

The structure of an option is simply the format in which the optiondata appears. The ISC DHCP server currently supports a few simpletypes, like integers, booleans, strings and IP addresses, and it alsosupports the ability to define arrays of single types or arrays offixed sequences of types.

New options are declared as follows:

optionnew-namecodenew-code=definition;

The values ofnew-nameandnew-codeshould be the name you have chosen for the new option and the code youhave chosen. Thedefinitionshould be the definition of the structure of the option.

The following simple option type definitions are supported:

BOOLEAN

optionnew-namecodenew-code=boolean;

An option of type boolean is a flag with a value of either on or off(or true or false). So an example use of the boolean type would be:

option use-zephyr code 180 = boolean;option use-zephyr on;
INTEGER

optionnew-namecodenew-code=signintegerwidth;

The sign token should either be blank, unsignedor signed. The width can be either 8, 16 or 32, and refers tothe number of bits in the integer. So for example, the following twolines show a definition of the sql-connection-max option and its use:

option sql-connection-max code 192 = unsigned integer 16;option sql-connection-max 1536;
IP-ADDRESS

optionnew-namecodenew-code=ip-address;

An option whose structure is an IP address can be expressed either asa domain name or as a dotted quad. So the following is an example useof the ip-address type:

option sql-server-address code 193 = ip-address;option sql-server-address sql.example.com;

TEXT

optionnew-namecodenew-code=text;

An option whose type is text will encode an ASCII text string. Forexample:

option sql-default-connection-name code 194 = text;option sql-default-connection-name "PRODZA";

DATA STRING

optionnew-namecodenew-code=string;

An option whose type is a data string is essentially just a collectionof bytes, and can be specified either as quoted text, like the texttype, or as a list of hexadecimal contents separated by colons whosevalues must be between 0 and FF. For example:

option sql-identification-token code 195 = string;option sql-identification-token 17:23:19:a6:42:ea:99:7c:22;

ENCAPSULATION

optionnew-namecodenew-code=encapsulateidentifier;

An option whose type is encapsulate will encapsulate thecontents of the option space specified in identifier. Examplesof encapsulated options in the DHCP protocol as it currently existsinclude the vendor-encapsulated-options option, the netware-suboptionsoption and the relay-agent-information option.

option space local;option local.demo code 1 = text;option local-encapsulation code 197 = encapsulate local;option local.demo "demo";

ARRAYS

Options can contain arrays of any of the above types except for thetext and data string types, which aren't currently supported inarrays. An example of an array definition is as follows:

option kerberos-servers code 200 = array of ip-address;option kerberos-servers 10.20.10.1, 10.20.11.1;
RECORDS

Options can also contain data structures consisting of a sequence ofdata types, which is sometimes called a record type. For example:

option contrived-001 code 201 = { boolean, integer 32, text };option contrived-001 on 1772 "contrivance";
It's also possible to have options that are arrays of records, forexample:
option new-static-routes code 201 = array of {        ip-address, ip-address, ip-address, integer 8 };option static-routes        10.0.0.0 255.255.255.0 net-0-rtr.example.com 1,        10.0.1.0 255.255.255.0 net-1-rtr.example.com 1,        10.2.0.0 255.255.224.0 net-2-0-rtr.example.com 3;
 

VENDOR ENCAPSULATED OPTIONS

The DHCP protocol defines the vendor-encapsulated-optionsoption, which allows vendors to define their own options that will besent encapsulated in a standard DHCP option. The format of thevendor-encapsulated-optionsoption is either a series of bytes whose format is not specified, ora sequence of options, each of which consists of a single-bytevendor-specific option code, followed by a single-byte length,followed by as many bytes of data as are specified in the length (thelength does not include itself or the option code).

The value of this option can be set in one of two ways. The firstway is to simply specify the data directly, using a text string or acolon-separated list of hexadecimal values. For example:

option vendor-encapsulated-options    2:4:AC:11:41:1:    3:12:73:75:6e:64:68:63:70:2d:73:65:72:76:65:72:31:37:2d:31:    4:12:2f:65:78:70:6f:72:74:2f:72:6f:6f:74:2f:69:38:36:70:63;

The second way of setting the value of this option is to have the DHCPserver generate a vendor-specific option buffer. To do this, youmust do four things: define an option space, define some options inthat option space, provide values for them, and specify that that option space should be used to generate thevendor-encapsulated-optionsoption.

To define a new option space in which vendor options can be stored,use the option space statement:

optionspacename;

The name can then be used in option definitions, as described earlier inthis document. For example:

option space SUNW;option SUNW.server-address code 2 = ip-address;option SUNW.server-name code 3 = text;option SUNW.root-path code 4 = text;
Once you have defined an option space and the format of some options,you can set up scopes that define values for those options, and youcan say when to use them. For example, suppose you want to handletwo different classes of clients. Using the option space definitionshown in the previous example, you can send different option values todifferent clients based on the vendor-class-identifier option that theclients send, as follows:

class "vendor-classes" {  match option vendor-class-identifier;}option SUNW.server-address 172.17.65.1;option SUNW.server-name "sundhcp-server17-1";subclass "vendor-classes" "SUNW.Ultra-5_10" {  vendor-option-space SUNW;  option SUNW.root-path "/export/root/sparc";}subclass "vendor-classes" "SUNW.i86pc" {  vendor-option-space SUNW;  option SUNW.root-path "/export/root/i86pc";}

As you can see in the preceding example, regular scoping rules apply,so you can define values that are global in the global scope, and onlydefine values that are specific to a particular class in the localscope. The vendor-option-space declaration tells the DHCPserver to use options in the SUNW option space to construct thevendor-encapsulated-optionsoption. 

SEE ALSO

dhcpd.conf(5), dhcpd.leases(5), dhclient.conf(5), dhcp-eval(5), dhcpd(8),dhclient(8), RFC2132, RFC2131, draft-ietf-dhc-agent-options-??.txt. 

AUTHOR

The Internet Software Consortium DHCP Distribution was written by TedLemon under a contract with Vixie Labs. Funding forthis project was provided through the Internet Software Consortium.Information about the Internet Software Consortium can be found athttp://www.isc.org.


 

Index

NAME
DESCRIPTION
REFERENCE: OPTION STATEMENTS
SETTING OPTION VALUES USING EXPRESSIONS
STANDARD DHCP OPTIONS
RELAY AGENT INFORMATION OPTION
THE CLIENT FQDN SUBOPTIONS
THE NETWARE/IP SUBOPTIONS
DEFINING NEW OPTIONS
VENDOR ENCAPSULATED OPTIONS
SEE ALSO
AUTHOR

This document was created byman2html,using the manual pages.