1# 2# CDDL HEADER START 3# 4# The contents of this file are subject to the terms of the 5# Common Development and Distribution License (the "License"). 6# You may not use this file except in compliance with the License. 7# 8# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE 9# or http://www.opensolaris.org/os/licensing. 10# See the License for the specific language governing permissions 11# and limitations under the License. 12# 13# When distributing Covered Code, include this CDDL HEADER in each 14# file and include the License file at usr/src/OPENSOLARIS.LICENSE. 15# If applicable, add the following below this CDDL HEADER, with the 16# fields enclosed by brackets "[]" replaced with your own identifying 17# information: Portions Copyright [yyyy] [name of copyright owner] 18# 19# CDDL HEADER END 20# 21 22# 23# Copyright 2009 Sun Microsystems, Inc. All rights reserved. 24# Use is subject to license terms. 25# 26 27# 28# This file contains tunable parameters for dhcpagent(1M). 29# 30 31# All parameters can be tuned for a specific interface by prepending 32# the interface name to the parameter name. For example, to make 33# VERIFIED_LEASE_ONLY happen on all interfaces except hme0, specify: 34# 35# hme0.VERIFIED_LEASE_ONLY=no 36# VERIFIED_LEASE_ONLY=yes 37# 38# An interface name alone specifies IPv4 DHCP. For DHCPv6, append ".v6". 39# Some examples: 40# 41# hme0.VERIFIED_LEASE_ONLY=no specify hme0 v4 behavior 42# hme0.v6.VERIFIED_LEASE_ONLY=no specify hme0 v6 behavior 43# VERIFIED_LEASE_ONLY=no match all v4 interfaces 44# .v6.VERIFIED_LEASE_ONLY=no match all v6 interfaces 45 46# By default, when the DHCP agent is sent a SIGTERM (typically when 47# the system is shut down), all managed addresses are dropped rather 48# than released. Dropping an address does not notify the DHCP server 49# that the address is no longer in use, leaving it possibly available 50# for subsequent use by the same client. If DHCP is later restarted 51# on the interface, the client will ask the server if it can continue 52# to use the address. If the server either grants the request, or 53# does not answer (and the lease has not yet expired), then the client 54# will use the original address. 55# 56# Similarly, when the system is suspended and then woken up or when 57# the link status transitions from down to up, DHCP will ask the server 58# to continue to use the managed address, in case the lease has changed. 59# 60# By uncommenting the following parameter-value pairs, all managed 61# addresses are released on SIGTERM instead, and any that may have been 62# saved but cannot be verified will not be used. When SIGTERM is 63# received, the DHCP server is notified that the address is available 64# for use, and the address will not be saved for a later restart. If 65# DHCP receives SIGTHAW or a link-up event, DHCP will attempt to verify 66# the previous lease, but if unable to do so, it will not attempt to 67# use that lease. This behavior is often preferred for roaming systems. 68# 69# VERIFIED_LEASE_ONLY=yes 70# .v6.VERIFIED_LEASE_ONLY=yes 71 72# By default, the DHCP agent waits 3 seconds to collect OFFER 73# responses to a DISCOVER. If it receives no OFFERs in this time, it 74# then waits for another 3 seconds, and so forth. To change this 75# behavior, set and uncomment the following parameter-value pair. 76# Note: this does not control the retransmission strategy for 77# DISCOVERs, which is formally specified in RFC 2131. This parameter 78# is specified in seconds. 79# 80# OFFER_WAIT= 81 82# By default, the DHCP agent does not send out a client identifier 83# (and hence, the chaddr field is used by the DHCP server as the 84# client identifier.) To make the DHCP agent send a client 85# identifier, set and uncomment the following parameter-value pair. 86# Note that by default this is treated as an NVT ASCII string. To 87# specify a binary value, prepend "0x" to a sequence of hexadecimal 88# digits (for example, the value 0xAABBCC11 would set the client 89# identifier to the 4-byte binary sequence 0xAA 0xBB 0xCC 0x11). 90# 91# CLIENT_ID= 92 93# By default, the DHCP agent will try to request the hostname currently 94# 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 97# 98# inet name 99# 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. 103# 104# REQUEST_HOSTNAME=no 105 106# By default, a parameter request list requesting a subnet mask (1), 107# router (3), DNS server (6), hostname (12), DNS domain (15), root path (17), 108# broadcast address (28), and encapsulated vendor options (43), is sent to the 109# DHCP server when the DHCP agent sends requests. However, if desired, this 110# can be changed by altering the following parameter-value pair. The 111# numbers correspond to the values defined in the IANA bootp-dhcp-parameters 112# registry at the time of this writing. Site and standard option names from 113# /etc/dhcp/inittab are also accepted. 114# 115PARAM_REQUEST_LIST=1,3,6,12,15,17,28,43 116 117# The default DHCPv6 parameter request list has preference (7), unicast (12), 118# DNS addresses (23), DNS search list (24), NIS addresses (27), and 119# NIS domain (29). This may be changed by altering the following parameter- 120# value pair. The numbers correspond to the values defined in the IANA 121# dhcpv6-parameters registry at the time of this writing. Site and standard 122# option names from /etc/dhcp/inittab6 are also accepted. 123.v6.PARAM_REQUEST_LIST=7,12,23,24,27,29 124 125# The parameter ignore list allows you to instruct the DHCP client to discard 126# optional parameters received from the DHCP server. The format is the same 127# as the request list above. When discarded, a parameter will not be acted 128# on by the DHCP client or returned to users via the dhcpinfo(1) command. 129PARAM_IGNORE_LIST= 130.v6.PARAM_IGNORE_LIST= 131