common/dhcp-options.cat5

   1
   2
   3
   4 dhcpd-options(5)                                 dhcpd-options(5)
   5
   6
   7 N\bNA\bAM\bME\bE
   8        dhcp-options - Dynamic Host Configuration Protocol options
   9
  10 D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
  11        The Dynamic Host Configuration protocol allows the  client
  12        to  receive  o\bop\bpt\bti\bio\bon\bns\bs  from  the DHCP server describing the
  13        network configuration and various services that are avail
  14        able  on  the  network.    When  configuring  d\bdh\bhc\bcp\bpd\bd(\b(8\b8)\b)  or
  15        d\bdh\bhc\bcl\bli\bie\ben\bnt\bt(\b(8\b8)\b) ,\b, options must often be declared.   The syntax
  16        for  declaring  options,  and the names and formats of the
  17        options that can be declared, are documented here.
  18
  19 R\bRE\bEF\bFE\bER\bRE\bEN\bNC\bCE\bE:\b: O\bOP\bPT\bTI\bIO\bON\bN S\bST\bTA\bAT\bTE\bEM\bME\bEN\bNT\bTS\bS
  20        DHCP _\bo_\bp_\bt_\bi_\bo_\bn statements always start with the  _\bo_\bp_\bt_\bi_\bo_\bn  key
  21        word, followed by an option name, followed by option data.
  22        The option names and data  formats  are  described  below.
  23        It  is  not  necessary  to  exhaustively  specify all DHCP
  24        options - only those options which are needed  by  clients
  25        must be specified.
  26
  27        Option  data  comes  in  a  variety of formats, as defined
  28        below:
  29
  30        The i\bip\bp-\b-a\bad\bdd\bdr\bre\bes\bss\bs data type  can  be  entered  either  as  an
  31        explicit  IP address (e.g., 239.254.197.10) or as a domain
  32        name (e.g., haagen.isc.org).  When entering a domain name,
  33        be  sure  that  that  domain  name resolves to a single IP
  34        address.
  35
  36        The i\bin\bnt\bt3\b32\b2 data type specifies  a  signed  32-bit  integer.
  37        The u\bui\bin\bnt\bt3\b32\b2 data type specifies an unsigned 32-bit integer.
  38        The  i\bin\bnt\bt1\b16\b6  and  u\bui\bin\bnt\bt1\b16\b6  data  types  specify  signed  and
  39        unsigned  16-bit integers.   The i\bin\bnt\bt8\b8 and u\bui\bin\bnt\bt8\b8 data types
  40        specify signed  and  unsigned  8-bit  integers.   Unsigned
  41        8-bit integers are also sometimes referred to as octets.
  42
  43        The  s\bst\btr\bri\bin\bng\bg data type specifies an NVT ASCII string, which
  44        must be enclosed in double quotes - for example, to  spec
  45        ify a domain-name option, the syntax would be
  46
  47             option domain-name "isc.org";
  48
  49        The  f\bfl\bla\bag\bg  data type specifies a boolean value.   Booleans
  50        can be either true or false (or on or off, if  that  makes
  51        more sense to you).
  52
  53        The  d\bda\bat\bta\ba-\b-s\bst\btr\bri\bin\bng\bg  data  type specifies either an NVT ASCII
  54        string enclosed in double quotes, or a  series  of  octets
  55        specified in hexadecimal, seperated by colons.   For exam
  56        ple:
  57
  58             option client-identifier "CLIENT-FOO";
  59        or
  60             option client-identifier 43:4c:49:45:54:2d:46:4f:4f;
  61
  62
  63
  64                                                                 1
  65
  66
  67
  68
  69
  70 dhcpd-options(5)                                 dhcpd-options(5)
  71
  72
  73        The documentation for the various options mentioned  below
  74        is  taken  from  the  latest  IETF  draft document on DHCP
  75        options.   Options which are not listed  by  name  may  be
  76        defined  by  the name option-_\bn_\bn_\bn, where _\bn_\bn_\bn _\bi_\bs _\bt_\bh_\be _\bd_\be_\bc_\bi_\bm_\ba_\bl
  77        _\bn_\bu_\bm_\bb_\be_\br _\bo_\bf _\bt_\bh_\be _\bo_\bp_\bt_\bi_\bo_\bn _\bc_\bo_\bd_\be_\b.   _\bT_\bh_\be_\bs_\be _\bo_\bp_\bt_\bi_\bo_\bn_\bs _\bm_\ba_\by _\bb_\be _\bf_\bo_\bl_\bl_\bo_\bw_\be_\bd
  78        _\be_\bi_\bt_\bh_\be_\br  _\bb_\by _\ba _\bs_\bt_\br_\bi_\bn_\bg_\b, _\be_\bn_\bc_\bl_\bo_\bs_\be_\bd _\bi_\bn _\bq_\bu_\bo_\bt_\be_\bs_\b, _\bo_\br _\bb_\by _\ba _\bs_\be_\br_\bi_\be_\bs _\bo_\bf
  79        _\bo_\bc_\bt_\be_\bt_\bs_\b, _\be_\bx_\bp_\br_\be_\bs_\bs_\be_\bd _\ba_\bs _\bt_\bw_\bo_\b-_\bd_\bi_\bg_\bi_\bt _\bh_\be_\bx_\ba_\bd_\be_\bc_\bi_\bm_\ba_\bl _\bn_\bu_\bm_\bb_\be_\br_\bs  _\bs_\be_\bp_\be_\br_\b
  80        _\ba_\bt_\be_\bd _\bb_\by _\bc_\bo_\bl_\bo_\bn_\bs_\b.   _\bF_\bo_\br _\be_\bx_\ba_\bm_\bp_\bl_\be_\b:
  81
  82             option option-133 "my-option-133-text";
  83             option option-129 1:54:c9:2b:47;
  84
  85        Because  dhcpd does not know the format of these undefined
  86        option codes, no checking is done to ensure  the  correct
  87        ness of the entered data.
  88
  89        The standard options are:
  90
  91        o\bop\bpt\bti\bio\bon\bn s\bsu\bub\bbn\bne\bet\bt-\b-m\bma\bas\bsk\bk _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
  92
  93           The  subnet  mask  option specifies the client's subnet
  94           mask as per RFC 950.  If no subnet mask option is  pro
  95           vided  anywhere  in  scope, as a last resort dhcpd will
  96           use the subnet mask from the subnet declaration for the
  97           network  on  which  an address is being assigned.  How
  98           ever, _\ba_\bn_\by subnet-mask option  declaration  that  is  in
  99           scope  for the address being assigned will override the
 100           subnet mask specified in the subnet declaration.
 101
 102        o\bop\bpt\bti\bio\bon\bn t\bti\bim\bme\be-\b-o\bof\bff\bfs\bse\bet\bt _\bi_\bn_\bt_\b3_\b2;\b;
 103
 104           The time-offset option  specifies  the  offset  of  the
 105           client's  subnet  in seconds from Coordinated Universal
 106           Time (UTC).
 107
 108        o\bop\bpt\bti\bio\bon\bn r\bro\bou\but\bte\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 109
 110           The routers option specifies a list of IP addresses for
 111           routers  on  the  client's  subnet.   Routers should be
 112           listed in order of preference.
 113
 114        o\bop\bpt\bti\bio\bon\bn t\bti\bim\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 115
 116           The time-server option specifies a list of RFC 868 time
 117           servers  available  to  the  client.  Servers should be
 118           listed in order of preference.
 119
 120        o\bop\bpt\bti\bio\bon\bn i\bie\ben\bn1\b11\b16\b6-\b-n\bna\bam\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];
 121
 122           The  ien116-name-servers option specifies a list of IEN
 123           116 name servers  available  to  the  client.   Servers
 124           should be listed in order of preference.
 125
 126        o\bop\bpt\bti\bio\bon\bn d\bdo\bom\bma\bai\bin\bn-\b-n\bna\bam\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 127
 128
 129
 130                                                                 2
 131
 132
 133
 134
 135
 136 dhcpd-options(5)                                 dhcpd-options(5)
 137
 138
 139           The domain-name-servers  option  specifies  a  list  of
 140           Domain  Name  System  (STD  13,  RFC 1035) name servers
 141           available to the client.  Servers should be  listed  in
 142           order of preference.
 143
 144        o\bop\bpt\bti\bio\bon\bn l\blo\bog\bg-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 145
 146           The  log-server  option specifies a list of MIT-LCS UDP
 147           log servers available to the client.  Servers should be
 148           listed in order of preference.
 149
 150        o\bop\bpt\bti\bio\bon\bn c\bco\boo\bok\bki\bie\be-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 151
 152           The  cookie  server  option specifies a list of RFC 865
 153           cookie servers available to the client.  Servers should
 154           be listed in order of preference.
 155
 156        o\bop\bpt\bti\bio\bon\bn l\blp\bpr\br-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs  [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 157
 158           The LPR server option specifies a list of RFC 1179 line
 159           printer  servers  available  to  the  client.   Servers
 160           should be listed in order of preference.
 161
 162        o\bop\bpt\bti\bio\bon\bn i\bim\bmp\bpr\bre\bes\bss\bs-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 163
 164           The  impress-server  option  specifies a list of Imagen
 165           Impress  servers  available  to  the  client.   Servers
 166           should be listed in order of preference.
 167
 168        o\bop\bpt\bti\bio\bon\bn   r\bre\bes\bso\bou\bur\brc\bce\be-\b-l\blo\boc\bca\bat\bti\bio\bon\bn-\b-s\bse\ber\brv\bve\ber\brs\bs   _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs   [,\b,   _\bi_\bp_\b-
 169        _\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 170
 171           This option specifies a list of RFC 887 Resource  Loca
 172           tion  servers  available to the client.  Servers should
 173           be listed in order of preference.
 174
 175        o\bop\bpt\bti\bio\bon\bn h\bho\bos\bst\bt-\b-n\bna\bam\bme\be _\bs_\bt_\br_\bi_\bn_\bg;\b;
 176
 177           This option specifies the name of the client.  The name
 178           may  or may not be qualified with the local domain name
 179           (it is preferable to  use  the  domain-name  option  to
 180           specify  the  domain name).  See RFC 1035 for character
 181           set restrictions.
 182
 183        o\bop\bpt\bti\bio\bon\bn b\bbo\boo\bot\bt-\b-s\bsi\biz\bze\be _\bu_\bi_\bn_\bt_\b1_\b6;\b;
 184
 185           This option specifies the length in 512-octet blocks of
 186           the default boot image for the client.
 187
 188        o\bop\bpt\bti\bio\bon\bn m\bme\ber\bri\bit\bt-\b-d\bdu\bum\bmp\bp _\bs_\bt_\br_\bi_\bn_\bg;\b;
 189
 190           This  option specifies the path-name of a file to which
 191           the client's core image should be dumped in  the  event
 192           the  client  crashes.   The  path  is  formatted  as  a
 193
 194
 195
 196                                                                 3
 197
 198
 199
 200
 201
 202 dhcpd-options(5)                                 dhcpd-options(5)
 203
 204
 205           character string consisting of characters from the  NVT
 206           ASCII character set.
 207
 208        o\bop\bpt\bti\bio\bon\bn d\bdo\bom\bma\bai\bin\bn-\b-n\bna\bam\bme\be _\bs_\bt_\br_\bi_\bn_\bg;\b;
 209
 210           This  option  specifies  the  domain  name  that client
 211           should use when resolving hostnames via the Domain Name
 212           System.
 213
 214        o\bop\bpt\bti\bio\bon\bn s\bsw\bwa\bap\bp-\b-s\bse\ber\brv\bve\ber\br _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
 215
 216           This  specifies  the  IP  address  of the client's swap
 217           server.
 218
 219        o\bop\bpt\bti\bio\bon\bn r\bro\boo\bot\bt-\b-p\bpa\bat\bth\bh _\bs_\bt_\br_\bi_\bn_\bg;\b;
 220
 221           This option specifies the path-name that  contains  the
 222           client's root disk.  The path is formatted as a charac
 223           ter string consisting of characters from the NVT  ASCII
 224           character set.
 225
 226        o\bop\bpt\bti\bio\bon\bn i\bip\bp-\b-f\bfo\bor\brw\bwa\bar\brd\bdi\bin\bng\bg _\bf_\bl_\ba_\bg;\b;
 227
 228           This option specifies whether the client should config
 229           ure its IP layer for packet forwarding.  A value  of  0
 230           means  disable  IP  forwarding,  and a value of 1 means
 231           enable IP forwarding.
 232
 233        o\bop\bpt\bti\bio\bon\bn n\bno\bon\bn-\b-l\blo\boc\bca\bal\bl-\b-s\bso\bou\bur\brc\bce\be-\b-r\bro\bou\but\bti\bin\bng\bg _\bf_\bl_\ba_\bg;\b;
 234
 235           This option specifies whether the client should config
 236           ure  its IP layer to allow forwarding of datagrams with
 237           non-local source routes (see Section 3.3.5 of [4] for a
 238           discussion of this topic).  A value of 0 means disallow
 239           forwarding of such datagrams, and a value  of  1  means
 240           allow forwarding.
 241
 242        o\bop\bpt\bti\bio\bon\bn  p\bpo\bol\bli\bic\bcy\by-\b-f\bfi\bil\blt\bte\ber\br  _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
 243        _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 244
 245           This option  specifies  policy  filters  for  non-local
 246           source  routing.   The  filters consist of a list of IP
 247           addresses  and  masks  which  specify  destination/mask
 248           pairs with which to filter incoming source routes.
 249
 250           Any  source routed datagram whose next-hop address does
 251           not match one of the filters should be discarded by the
 252           client.
 253
 254           See STD 3 (RFC1122) for further information.
 255
 256        o\bop\bpt\bti\bio\bon\bn m\bma\bax\bx-\b-d\bdg\bgr\bra\bam\bm-\b-r\bre\bea\bas\bss\bse\bem\bmb\bbl\bly\by _\bu_\bi_\bn_\bt_\b1_\b6;\b;
 257
 258           This  option  specifies  the maximum size datagram that
 259
 260
 261
 262                                                                 4
 263
 264
 265
 266
 267
 268 dhcpd-options(5)                                 dhcpd-options(5)
 269
 270
 271           the client should be prepared to reassemble.  The mini
 272           mum value legal value is 576.
 273
 274        o\bop\bpt\bti\bio\bon\bn d\bde\bef\bfa\bau\bul\blt\bt-\b-i\bip\bp-\b-t\btt\btl\bl _\bu_\bi_\bn_\bt_\b8_\b;
 275
 276           This option specifies the default time-to-live that the
 277           client should use on outgoing datagrams.
 278
 279        o\bop\bpt\bti\bio\bon\bn p\bpa\bat\bth\bh-\b-m\bmt\btu\bu-\b-a\bag\bgi\bin\bng\bg-\b-t\bti\bim\bme\beo\bou\but\bt _\bu_\bi_\bn_\bt_\b3_\b2;\b;
 280
 281           This option specifies the timeout (in seconds)  to  use
 282           when  aging Path MTU values discovered by the mechanism
 283           defined in RFC 1191.
 284
 285        o\bop\bpt\bti\bio\bon\bn p\bpa\bat\bth\bh-\b-m\bmt\btu\bu-\b-p\bpl\bla\bat\bte\bea\bau\bu-\b-t\bta\bab\bbl\ble\be _\bu_\bi_\bn_\bt_\b1_\b6 [,\b, _\bu_\bi_\bn_\bt_\b1_\b6...  ];\b;
 286
 287           This option specifies a table of MTU sizes to use  when
 288           performing  Path  MTU Discovery as defined in RFC 1191.
 289           The table is formatted as a  list  of  16-bit  unsigned
 290           integers,  ordered from smallest to largest.  The mini
 291           mum MTU value cannot be smaller than 68.
 292
 293        o\bop\bpt\bti\bio\bon\bn i\bin\bnt\bte\ber\brf\bfa\bac\bce\be-\b-m\bmt\btu\bu _\bu_\bi_\bn_\bt_\b1_\b6;\b;
 294
 295           This option specifies the MTU to use on this interface.
 296           The minimum legal value for the MTU is 68.
 297
 298        o\bop\bpt\bti\bio\bon\bn a\bal\bll\bl-\b-s\bsu\bub\bbn\bne\bet\bts\bs-\b-l\blo\boc\bca\bal\bl _\bf_\bl_\ba_\bg;\b;
 299
 300           This  option  specifies  whether  or not the client may
 301           assume that all subnets of the IP network to which  the
 302           client  is  connected use the same MTU as the subnet of
 303           that network to which the client is directly connected.
 304           A  value of 1 indicates that all subnets share the same
 305           MTU.  A value of 0 means that the client should  assume
 306           that some subnets of the directly connected network may
 307           have smaller MTUs.
 308
 309        o\bop\bpt\bti\bio\bon\bn b\bbr\bro\boa\bad\bdc\bca\bas\bst\bt-\b-a\bad\bdd\bdr\bre\bes\bss\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
 310
 311           This option specifies the broadcast address in  use  on
 312           the   client's  subnet.   Legal  values  for  broadcast
 313           addresses are specified in section  3.2.1.3  of  STD  3
 314           (RFC1122).
 315
 316        o\bop\bpt\bti\bio\bon\bn p\bpe\ber\brf\bfo\bor\brm\bm-\b-m\bma\bas\bsk\bk-\b-d\bdi\bis\bsc\bco\bov\bve\ber\bry\by _\bf_\bl_\ba_\bg;\b;
 317
 318           This  option specifies whether or not the client should
 319           perform subnet mask discovery using ICMP.  A value of 0
 320           indicates  that the client should not perform mask dis
 321           covery.  A value of 1 means that the client should per
 322           form mask discovery.
 323
 324        o\bop\bpt\bti\bio\bon\bn m\bma\bas\bsk\bk-\b-s\bsu\bup\bpp\bpl\bli\bie\ber\br _\bf_\bl_\ba_\bg;\b;
 325
 326
 327
 328                                                                 5
 329
 330
 331
 332
 333
 334 dhcpd-options(5)                                 dhcpd-options(5)
 335
 336
 337           This  option specifies whether or not the client should
 338           respond to subnet mask requests using ICMP.  A value of
 339           0  indicates  that  the  client  should not respond.  A
 340           value of 1 means that the client should respond.
 341
 342        o\bop\bpt\bti\bio\bon\bn r\bro\bou\but\bte\ber\br-\b-d\bdi\bis\bsc\bco\bov\bve\ber\bry\by _\bf_\bl_\ba_\bg;\b;
 343
 344           This option specifies whether or not the client  should
 345           solicit  routers  using  the Router Discovery mechanism
 346           defined in RFC 1256.  A value of 0 indicates  that  the
 347           client should not perform router discovery.  A value of
 348           1 means that the client should perform  router  discov
 349           ery.
 350
 351        o\bop\bpt\bti\bio\bon\bn r\bro\bou\but\bte\ber\br-\b-s\bso\bol\bli\bic\bci\bit\bta\bat\bti\bio\bon\bn-\b-a\bad\bdd\bdr\bre\bes\bss\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs;\b;
 352
 353           This  option  specifies the address to which the client
 354           should transmit router solicitation requests.
 355
 356        o\bop\bpt\bti\bio\bon\bn s\bst\bta\bat\bti\bic\bc-\b-r\bro\bou\but\bte\bes\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs  [,\b,  _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs
 357        _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 358
 359           This  option specifies a list of static routes that the
 360           client should install in its routing cache.  If  multi
 361           ple  routes to the same destination are specified, they
 362           are listed in descending order of priority.
 363
 364           The routes consist of a list of IP address pairs.   The
 365           first  address is the destination address, and the sec
 366           ond address is the router for the destination.
 367
 368           The default route (0.0.0.0) is an  illegal  destination
 369           for  a static route.  To specify the default route, use
 370           the r\bro\bou\but\bte\ber\brs\bs option.
 371
 372        o\bop\bpt\bti\bio\bon\bn t\btr\bra\bai\bil\ble\ber\br-\b-e\ben\bnc\bca\bap\bps\bsu\bul\bla\bat\bti\bio\bon\bn _\bf_\bl_\ba_\bg;\b;
 373
 374           This option specifies whether or not the client  should
 375           negotiate the use of trailers (RFC 893 [14]) when using
 376           the ARP protocol.  A value  of  0  indicates  that  the
 377           client  should not attempt to use trailers.  A value of
 378           1 means that the client should attempt to use trailers.
 379
 380        o\bop\bpt\bti\bio\bon\bn a\bar\brp\bp-\b-c\bca\bac\bch\bhe\be-\b-t\bti\bim\bme\beo\bou\but\bt _\bu_\bi_\bn_\bt_\b3_\b2;\b;
 381
 382           This  option  specifies  the timeout in seconds for ARP
 383           cache entries.
 384
 385        o\bop\bpt\bti\bio\bon\bn i\bie\bee\bee\be8\b80\b02\b2-\b-3\b3-\b-e\ben\bnc\bca\bap\bps\bsu\bul\bla\bat\bti\bio\bon\bn _\bf_\bl_\ba_\bg;\b;
 386
 387           This option specifies whether or not the client  should
 388           use  Ethernet  Version  2  (RFC 894) or IEEE 802.3 (RFC
 389           1042) encapsulation if the interface is an Ethernet.  A
 390           value of 0 indicates that the client should use RFC 894
 391
 392
 393
 394                                                                 6
 395
 396
 397
 398
 399
 400 dhcpd-options(5)                                 dhcpd-options(5)
 401
 402
 403           encapsulation.  A value of  1  means  that  the  client
 404           should use RFC 1042 encapsulation.
 405
 406        o\bop\bpt\bti\bio\bon\bn d\bde\bef\bfa\bau\bul\blt\bt-\b-t\btc\bcp\bp-\b-t\btt\btl\bl _\bu_\bi_\bn_\bt_\b8;\b;
 407
 408           This  option  specifies the default TTL that the client
 409           should use when  sending  TCP  segments.   The  minimum
 410           value is 1.
 411
 412        o\bop\bpt\bti\bio\bon\bn t\btc\bcp\bp-\b-k\bke\bee\bep\bpa\bal\bli\biv\bve\be-\b-i\bin\bnt\bte\ber\brv\bva\bal\bl _\bu_\bi_\bn_\bt_\b3_\b2;\b;
 413
 414           This  option  specifies  the interval (in seconds) that
 415           the client TCP should wait before sending  a  keepalive
 416           message  on a TCP connection.  The time is specified as
 417           a 32-bit unsigned integer.  A value of  zero  indicates
 418           that  the client should not generate keepalive messages
 419           on connections  unless  specifically  requested  by  an
 420           application.
 421
 422        o\bop\bpt\bti\bio\bon\bn t\btc\bcp\bp-\b-k\bke\bee\bep\bpa\bal\bli\biv\bve\be-\b-g\bga\bar\brb\bba\bag\bge\be _\bf_\bl_\ba_\bg;\b;
 423
 424           This  option  specifies  the  whether or not the client
 425           should send TCP keepalive  messages  with  a  octet  of
 426           garbage  for  compatibility with older implementations.
 427           A value of 0 indicates that a garbage octet should  not
 428           be  sent.  A  value of 1 indicates that a garbage octet
 429           should be sent.
 430
 431        o\bop\bpt\bti\bio\bon\bn n\bni\bis\bs-\b-d\bdo\bom\bma\bai\bin\bn _\bs_\bt_\br_\bi_\bn_\bg;\b;
 432
 433           This option specifies the name of the client's NIS (Sun
 434           Network  Information  Services)  domain.  The domain is
 435           formatted as a character string consisting  of  charac
 436           ters from the NVT ASCII character set.
 437
 438        o\bop\bpt\bti\bio\bon\bn n\bni\bis\bs-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 439
 440           This option specifies a list of IP addresses indicating
 441           NIS servers available to the client.  Servers should be
 442           listed in order of preference.
 443
 444        o\bop\bpt\bti\bio\bon\bn n\bnt\btp\bp-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 445
 446           This option specifies a list of IP addresses indicating
 447           NTP  (RFC  1035)  servers  available  to  the   client.
 448           Servers should be listed in order of preference.
 449
 450        o\bop\bpt\bti\bio\bon\bn  n\bne\bet\btb\bbi\bio\bos\bs-\b-n\bna\bam\bme\be-\b-s\bse\ber\brv\bve\ber\brs\bs  _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs  [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...
 451        ];\b;
 452
 453           The NetBIOS name server (NBNS) option specifies a  list
 454           of  RFC  1001/1002 NBNS name servers listed in order of
 455           preference.   NetBIOS Name Service  is  currently  more
 456           commonly  referred  to  as  WINS.   WINS servers can be
 457
 458
 459
 460                                                                 7
 461
 462
 463
 464
 465
 466 dhcpd-options(5)                                 dhcpd-options(5)
 467
 468
 469           specified using the netbios-name-servers option.
 470
 471        o\bop\bpt\bti\bio\bon\bn n\bne\bet\btb\bbi\bio\bos\bs-\b-d\bdd\bd-\b-s\bse\ber\brv\bve\ber\br _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 472
 473           The NetBIOS datagram distribution server (NBDD)  option
 474           specifies  a  list of RFC 1001/1002 NBDD servers listed
 475           in order of preference.
 476
 477        o\bop\bpt\bti\bio\bon\bn n\bne\bet\btb\bbi\bio\bos\bs-\b-n\bno\bod\bde\be-\b-t\bty\byp\bpe\be _\bu_\bi_\bn_\bt_\b8;\b;
 478
 479           The NetBIOS node type option allows NetBIOS over TCP/IP
 480           clients  which  are  configurable  to  be configured as
 481           described in RFC 1001/1002.  The value is specified  as
 482           a single octet which identifies the client type.
 483
 484           Possible node types are:
 485
 486
 487           _\b1    B-node: Broadcast - no WINS
 488
 489           _\b2    P-node: Peer - WINS only.
 490
 491           _\b4    M-node: Mixed - broadcast, then WINS
 492
 493           _\b8    H-node: Hybrid - WINS, then broadcast
 494
 495        o\bop\bpt\bti\bio\bon\bn n\bne\bet\btb\bbi\bio\bos\bs-\b-s\bsc\bco\bop\bpe\be _\bs_\bt_\br_\bi_\bn_\bg;\b;
 496
 497           The  NetBIOS  scope  option  specifies the NetBIOS over
 498           TCP/IP scope parameter for the client as  specified  in
 499           RFC  1001/1002.  See  RFC1001, RFC1002, and RFC1035 for
 500           character-set restrictions.
 501
 502        o\bop\bpt\bti\bio\bon\bn f\bfo\bon\bnt\bt-\b-s\bse\ber\brv\bve\ber\brs\bs _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 503
 504           This option specifies a list of X  Window  System  Font
 505           servers  available  to  the  client.  Servers should be
 506           listed in order of preference.
 507
 508        o\bop\bpt\bti\bio\bon\bn x\bx-\b-d\bdi\bis\bsp\bpl\bla\bay\by-\b-m\bma\ban\bna\bag\bge\ber\br _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs [,\b, _\bi_\bp_\b-_\ba_\bd_\bd_\br_\be_\bs_\bs...  ];\b;
 509
 510           This option specifies a list of systems that  are  run
 511           ning the X Window System Display Manager and are avail
 512           able to the client.   Addresses  should  be  listed  in
 513           order of preference.
 514
 515        o\bop\bpt\bti\bio\bon\bn d\bdh\bhc\bcp\bp-\b-c\bcl\bli\bie\ben\bnt\bt-\b-i\bid\bde\ben\bnt\bti\bif\bfi\bie\ber\br _\bd_\ba_\bt_\ba_\b-_\bs_\bt_\br_\bi_\bn_\bg;\b;
 516
 517           This  option  can  be used to specify the a DHCP client
 518           identifier in a host declaration,  so  that  dhcpd  can
 519           find  the  host  record  by matching against the client
 520           identifier.
 521
 522
 523
 524
 525
 526                                                                 8
 527
 528
 529
 530
 531
 532 dhcpd-options(5)                                 dhcpd-options(5)
 533
 534
 535 S\bSE\bEE\bE A\bAL\bLS\bSO\bO
 536        dhcpd.conf(5),     dhcpd.leases(5),      dhclient.conf(5),
 537        dhcpd(8), dhclient(8), RFC2132, RFC2131.
 538
 539 A\bAU\bUT\bTH\bHO\bOR\bR
 540        d\bdh\bhc\bcp\bpd\bd(\b(8\b8)\b) was written by Ted Lemon <mellon@vix.com> under a
 541        contract with Vixie Labs.   Funding for this  project  was
 542        provided  by  the Internet Software Corporation.  Informa
 543        tion about the Internet Software Consortium can  be  found
 544        at h\bht\btt\btp\bp:\b:/\b//\b/w\bww\bww\bw.\b.i\bis\bsc\bc.\b.o\bor\brg\bg/\b/i\bis\bsc\bc.\b.
 545
 546
 547
 548
 549
 550
 551
 552
 553
 554
 555
 556
 557
 558
 559
 560
 561
 562
 563
 564
 565
 566
 567
 568
 569
 570
 571
 572
 573
 574
 575
 576
 577
 578
 579
 580
 581
 582
 583
 584
 585
 586
 587
 588
 589
 590
 591
 592                                                                 9
 593
 594