Print this page 
7388 Support DHCP Client FQDN. Allow IAID/DUID for all v4.
Split Close
Expand all
Collapse all
          --- old/usr/src/cmd/cmd-inet/sbin/dhcpagent/dhcpagent.dfl
          +++ new/usr/src/cmd/cmd-inet/sbin/dhcpagent/dhcpagent.dfl
↓ open down ↓ 14 lines elided ↑ open up ↑ 
  15   15  # If applicable, add the following below this CDDL HEADER, with the
  16   16  # fields enclosed by brackets "[]" replaced with your own identifying
  17   17  # information: Portions Copyright [yyyy] [name of copyright owner]
  18   18  #
  19   19  # CDDL HEADER END
  20   20  #
  21   21  
  22   22  #
  23   23  # Copyright 2009 Sun Microsystems, Inc.  All rights reserved.
  24   24  # Use is subject to license terms.
       25 +# Copyright (c) 2016, Chris Fraire <cfraire@me.com>.
  25   26  #
  26   27  
  27   28  #
  28   29  # This file contains tunable parameters for dhcpagent(1M).
  29   30  #
  30   31  
  31   32  # All parameters can be tuned for a specific interface by prepending
  32   33  # the interface name to the parameter name.  For example, to make
  33   34  # VERIFIED_LEASE_ONLY happen on all interfaces except hme0, specify:
  34   35  #
↓ open down ↓ 48 lines elided ↑ open up ↑ 
  83   84  # (and hence, the chaddr field is used by the DHCP server as the
  84   85  # client identifier.)  To make the DHCP agent send a client
  85   86  # identifier, set and uncomment the following parameter-value pair.
  86   87  # Note that by default this is treated as an NVT ASCII string.  To
  87   88  # specify a binary value, prepend "0x" to a sequence of hexadecimal
  88   89  # digits (for example, the value 0xAABBCC11 would set the client
  89   90  # identifier to the 4-byte binary sequence 0xAA 0xBB 0xCC 0x11).
  90   91  #
  91   92  # CLIENT_ID=
  92   93  
       94 +# By default, for an IPv4 interface that is not in an IP network
       95 +# multipathing (IPMP) group, that is not IP over InfiniBand (IPoIB), and
       96 +# that is not a logical interface, the DHCP agent will forgo sending a
       97 +# client identifier unless CLIENT_ID is defined.
       98 +#
       99 +# To use a system-managed, RFC 3315-style (i.e., DHCPv6-style) binding
      100 +# identifier as documented in RFC 4361, "Node-specific Client Identifiers
      101 +# for DHCPv4," for all IPv4 interfaces (unless CLIENT_ID is defined),
      102 +# uncomment the following line.
      103 +#
      104 +# V4_DEFAULT_IAID_DUID=yes
      105 +
      106 +# By default, the DHCP agent will try to request the Fully Qualified Domain
      107 +# Name (FQDN) currently associated with the interface performing DHCP.  The
      108 +# hostname is defined by using the -h,--reqhost option of ipadm(1M) or the
      109 +# ncu ip-reqhost property of nwamcfg(1M) or by flagging the interface as
      110 +# primary so that nodename(4) is used as the hostname.
      111 +#
      112 +# A defined hostname will be used as the FQDN if it is "rooted" (i.e., if
      113 +# it ends with a '.') or if it consists of at least three DNS labels (e.g.,
      114 +# srv.example.com).  If the hostname is not an FQDN, then either a defined
      115 +# defaultdomain(4) or a defined resolv.conf(4) domain will be appended to
      116 +# form an FQDN.  If no FQDN can be determined, the option will not be used.
      117 +#
      118 +# If this REQUEST_FQDN option is enabled, an FQDN will be sent in messages
      119 +# to the DHCP server along with RFC 4702 options to request that a
      120 +# collaborating DNS server perform DNS updates for A and PTR resource
      121 +# records.  To prevent sending FQDN and DNS options, uncomment the line
      122 +# below.
      123 +#
      124 +# If an FQDN is sent, REQUEST_HOSTNAME processing will not be done, per RFC
      125 +# 4702 (3.1):  "clients that send the Client FQDN option in their messages
      126 +# MUST NOT also send the Host Name."
      127 +#
      128 +# REQUEST_FQDN=no
      129 +
  93  130  # By default, the DHCP agent will try to request the hostname currently
  94  131  # associated with the interface performing DHCP.  If this option is
  95      -# enabled, the agent will attempt to find a host name in /etc/hostname.<if>,
  96      -# which must contain a line of the form
      132 +# enabled, the agent will attempt to use an -h,--reqhost option saved with
      133 +# ipadm(1M) or an ncu ip-reqhost property set with nwamcfg(1M); or else
      134 +# attempt to find a host name in /etc/hostname.<if>, which must contain a
      135 +# line of the form
  97  136  #
  98  137  #       inet name
  99  138  #
 100      -# where "name" is a single RFC 1101-compliant token.  If found, the token
 101      -# will be used to request that host name from the DHCP server.  To prevent
 102      -# this, uncomment the following line.
      139 +# where "name" is a single RFC 1101-compliant token; or else use
      140 +# nodename(4) for a DHCP interface flagged as primary.  If found in any of
      141 +# these configurations, the token will be used to request that host name
      142 +# from the DHCP server.  To prevent this, uncomment the following line.
 103  143  #
 104  144  # REQUEST_HOSTNAME=no
 105  145  
 106  146  # By default, a parameter request list requesting a subnet mask (1),
 107  147  # router (3), DNS server (6), hostname (12), DNS domain (15), broadcast
 108  148  # address (28), and encapsulated vendor options (43), is sent to the DHCP
 109  149  # server when the DHCP agent sends requests.  However, if desired, this
 110  150  # can be changed by altering the following parameter-value pair.  The
 111  151  # numbers correspond to the values defined in the IANA bootp-dhcp-parameters
 112  152  # registry at the time of this writing.  Site and standard option names from
↓ open down ↓ 18 lines elided ↑ open up ↑ 
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX