📄 dhcp-options.5
字号:
.B option routers \fIip-address\fR [\fB,\fR \fIip-address\fR...]\fB;\fR.RS 0.25i.PPThe routers option specifies a list of IP addresses for routers on theclient's subnet. Routers should be listed in order of preference..RE.PP.B option slp-directory-agent \fIboolean ip-address[\fB,\fR \fIip-address\fR... ]\fB;\fR.RS 0.25i.PPThis 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)..PPPlease 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..PPAlso, 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..RE.PP.B option slp-service-scope \fIboolean text\fR\fB;\fR.RS 0.25i.PPThe 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..PPThe 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..RE.PP.B option \fBsmtp-server\fR \fIip-address\fR [\fB,\fR\fIip-address\fR... ]\fB;\fR.RS 0.25i.PPThe SMTP server option specifies a list of SMTP servers available tothe client. Servers should be listed in order of preference..RE.PP.nf.B option \fBstatic-routes\fR \fIip-address ip-address\fR [\fB,\fR \fIip-address ip-address\fR...]\fB;\fR.fi.RS 0.25i.PPThis 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..PPThe routes consist of a list of IP address pairs. The first addressis the destination address, and the second address is the router forthe destination..PPThe default route (0.0.0.0) is an illegal destination for a staticroute. To specify the default route, use the.B routersoption. 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..RE.PP.nf.B option \fBstreettalk-directory-assistance-server\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...]\fB;\fR.fi.RS 0.25i.PPThe StreetTalk Directory Assistance (STDA) server option specifies alist of STDA servers available to the client. Servers should belisted in order of preference..RE.PP.B option \fBstreettalk-server\fR \fIip-address\fR [\fB,\fR \fIip-address\fR... ]\fB;\fR.RS 0.25i.PPThe StreetTalk server option specifies a list of StreetTalk serversavailable to the client. Servers should be listed in order ofpreference..RE.PP.B option subnet-mask \fIip-address\fR\fB;\fR.RS 0.25i.PPThe 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,.I anysubnet-mask option declaration that is in scope for the address beingassigned will override the subnet mask specified in the subnetdeclaration..RE.PP.B option \fBsubnet-selection\fR \fIstring\fR\fB;\fR.RS 0.25i.PPSent 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!.RE.PPThis option is not user configurable in the server..PP.PP.B option \fBswap-server\fR \fIip-address\fR\fB;\fR.RS 0.25i.PPThis specifies the IP address of the client's swap server..RE.PP.B option \fBtcp-keepalive-garbage\fR \fIflag\fR\fB;\fR.RS 0.25i.PPThis option specifies whether or not the client should send TCPkeepalive messages with an 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..RE.PP.B option \fBtcp-keepalive-interval\fR \fIuint32\fR\fB;\fR.RS 0.25i.PPThis 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..RE.PP.B option \fBtftp-server-name\fR \fItext\fR\fB;\fR.RS 0.25i.PPThis option is used to identify a TFTP server and, if supported by theclient, should have the same effect as the \fBserver-name\fRdeclaration. BOOTP clients are unlikely to support this option.Some DHCP clients will support it, and others actually require it..RE.PP.B option time-offset \fIint32\fR\fB;\fR.RS 0.25i.PPThe time-offset option specifies the offset of the client's subnet inseconds from Coordinated Universal Time (UTC)..RE.PP.B option time-servers \fIip-address\fR [, \fIip-address\fR...]\fB;\fR.RS 0.25i.PPThe time-server option specifies a list of RFC 868 time serversavailable to the client. Servers should be listed in order ofpreference..RE.PP.B option \fBtrailer-encapsulation\fR \fIflag\fR\fB;\fR.RS 0.25i.PPThis 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..RE.PP.B option \fBuap-servers\fR \fItext\fR\fB;\fR.RS 0.25i.PPThis 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..RE.PP.B option \fBuser-class\fR \fIstring\fR\fB;\fR.RS 0.25i.PPThis 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..PP.B option \fBvendor-class-identifier\fR \fIstring\fR\fB;\fR.RS 0.25i.PPThis 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:.nf.PPset vendor-class option vendor-class-identifier;.fi.PPThis 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:.nf.PPset vendor-class "SUNW.Ultra-5_10";.fi.PPThe vendor-class-identifier option is normally used by the DHCP serverto determine the options that are returned in the.B vendor-encapsulated-optionsoption. Please see the VENDOR ENCAPSULATED OPTIONS section of thedhcpd.conf manual page for further information..RE.PP.B option \fBvendor-encapsulated-options\fR \fIstring\fR\fB;\fR.RS 0.25i.PPThe \fBvendor-encapsulated-options\fR 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..PPSome 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 \fIdhcpd.conf\fI manual page fordetails..RE.PP.B option \fBwww-server\fR \fIip-address\fR [\fB,\fR\fIip-address\fR... ]\fB;\fR.RS 0.25i.PPThe WWW server option specifies a list of WWW servers availableto the client. Servers should be listed in order of preference..RE.PP.B option \fBx-display-manager\fR \fIip-address\fR [\fB,\fR \fIip-address\fR...]\fB;\fR.RS 0.25i.PPThis 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..RE.SH RELAY AGENT INFORMATION OPTIONAn 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..PPThe 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..PP.B option \fBagent.circuit-id\fR \fIstring\fR\fB;\fR.RS 0.25i.PPThe 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..RE.PP.B option \fBagent.remote-id\fR \fIstring\fR\fB;\fR.RS 0.25i.PPThe 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..RE.SH THE CLIENT FQDN SUBOPTIONSThe 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..PP.B option fqdn.no-client-update \fIflag\fB;.RS 0.25i.PPWhen 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 \fIshould not\fR update its own A record..RE.PP.B option fqdn.server-update \fIflag\fB;.RS 0.25i.PPWhen 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..RE.PP.B option fqdn.encoded \fIflag\fB;.RS 0.25i.PPIf 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 \fIfqdn.fqdn\fR suboption is encoded..RE.PP.B option fqdn.rcode1 \fIflag\fB;.PP.B option fqdn.rcode2 \fIflag\fB;.RS 0.25i.PPThese 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..RE.PP.B option fqdn.fqdn \fItext\fB;.RS 0.25i.PPSpecifies the domain name that the client wishes to use. This can be afully-qualified domain name, or a single label. If there is no trailing'.' character in the name, it is not fully-qualified, and the server willgenerally update that name in some locally-defined domain..RE.PP.B option fqdn.hostname \fI--never set--\fB;.RS 0.25i.PPThis option should never be set, but it can be read back using the \fBoption\fRand \fBconfig-option\fR operators in an expression, in which case it returnsthe first label in the \fBfqdn.fqdn\fR suboption - for example, ifthe value of \fBfqdn.fqdn\fR is "foo.example.com.", then \fBfqdn.hostname\fRwill be "foo"..RE.PP.B option fqdn.domainname \fI--never set--\fB;.RS 0.25i.PPThis option should never be set, but it can be read back using the \fBoption\fR
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -