/* Define this if you want to see the requests and replies between the
DHCP code and the DNS library code. */
-
/* #define DEBUG_DNS_UPDATES */
/* Define this if you want to debug the host part of the inform processing */
/* #define DEBUG_INFORM_HOST */
+/* Define this if you want to debug the binary leases (lease_chain) code */
+/* #define DEBUG_BINARY_LEASES */
+
+/* Define this if you want to debug checksum calculations */
+/* #define DEBUG_CHECKSUM */
+
+/* Define this if you want to verbosely debug checksum calculations */
+/* #define DEBUG_CHECKSUM_VERBOSE */
+
+
/* Define this if you want DHCP failover protocol support in the DHCP
server. */
/* #define USE_RAW_SOCKETS */
+/* Define this to keep the old program name (e.g., "dhcpd" for
+ the DHCP server) in place of the (base) name the program was
+ invoked with. */
+
+/* #define OLD_LOG_NAME */
+
/* Define this to change the logging facility used by dhcpd. */
/* #define DHCPD_LOG_FACILITY LOG_DAEMON */
#define ACCEPT_LIST_IN_DOMAIN_NAME
-/* In RFC3315 section 17.2.2 stated that if the server was not going
- to be able to assign any addresses to any IAs in a subsequent Request
- from a client that the server should not include any IAs. This
- requirement was removed in an errata from August 2010. Define the
- following if you want the pre-errata version.
- You should only enable this option if you have clients that
- require the original functionality. */
-
-/* #define RFC3315_PRE_ERRATA_2010_08 */
-
/* In previous versions of the code when the server generates a NAK
it doesn't attempt to determine if the configuration included a
server ID for that client. Defining this option causes the server
#define SERVER_ID_FOR_NAK
-/* When processing a request do a simple check to compare the
- server id the client sent with the one the server would send.
- In order to minimize the complexity of the code the server
- only checks for a server id option in the global and subnet
- scopes. Complicated configurations may result in differnet
- server ids for this check and when the server id for a reply
- packet is determined, which would prohibit the server from
- responding.
-
- The primary use for this option is when a client broadcasts
- a request but requires the response to come from one of the
- failover peers. An example of this would be when a client
- reboots while its lease is still active - in this case both
- servers will normally respond. Most of the time the client
- won't check the server id and can use either of the responses.
- However if the client does check the server id it may reject
- the response if it came from the wrong peer. If the timing
- is such that the "wrong" peer responds first most of the time
- the client may not get an address for some time.
-
- Currently this option is only available when failover is in
- use.
-
- Care should be taken before enabling this option. */
-
-/* #define SERVER_ID_CHECK */
+/* NOTE: SERVER_ID_CHECK switch has been removed. Enabling server id
+ * checking is now done via the server-id-check statement. Please refer
+ * to the dhcpd manpage (server/dhcpd.conf.5) */
/* Include code to do a slow transition of DDNS records
from the interim to the standard version, or backwards.
entail updating all the records at once, probably at start
up. */
#define DDNS_UPDATE_SLOW_TRANSITION
-
+
+/* Define the default prefix length passed from the client to
+ the script when modifying an IPv6 IA_NA or IA_TA address.
+ The two most useful values are 128 which is what the current
+ specifications call for or 64 which is what has been used in
+ the past. For most OSes 128 will indicate that the address
+ is a host address and doesn't include any on-link information.
+ 64 indicates that the first 64 bits are the subnet or on-link
+ prefix. */
+#define DHCLIENT_DEFAULT_PREFIX_LEN 128
+
+/* Enable the gentle shutdown signal handling. Currently this
+ means that on SIGINT or SIGTERM a client will release its
+ address and a server in a failover pair will go through
+ partner down. Both of which can be undesireable in some
+ situations. We plan to revisit this feature and may
+ make non-backwards compatible changes including the
+ removal of this define. Use at your own risk. */
+/* #define ENABLE_GENTLE_SHUTDOWN */
+
+/* Include old error codes. This is provided in case you
+ are building an external program similar to omshell for
+ which you need the ISC_R_* error codes. You should switch
+ to DHCP_R_* error codes for those that have been defined
+ (see includes/omapip/result.h). The extra defines and
+ this option will be removed at some time. */
+/* #define INCLUDE_OLD_DHCP_ISC_ERROR_CODES */
+
+/* Use the older factors for scoring a lease in the v6 client code.
+ The new factors cause the client to choose more bindings (IAs)
+ over more addresse within a binding. Most uses will get a
+ single address in a single binding and only get an adverstise
+ from a single server and there won't be a difference. */
+/* #define USE_ORIGINAL_CLIENT_LEASE_WEIGHTS */
+
+/* Print out specific error messages for dhclient, dhcpd
+ or dhcrelay when processing an incorrect command line. This
+ is included for those that might require the exact error
+ messages, as we don't expect that is necessary it is on by
+ default. */
+#define PRINT_SPECIFIC_CL_ERRORS
+
+/* Limit the value of a file descriptor the serve will use
+ when accepting a connecting request. This can be used to
+ limit the number of TCP connections that the server will
+ allow at one time. A value of 0 means there is no limit.*/
+#define MAX_FD_VALUE 200
+
+/* Enable EUI-64 Address assignment policy. Instructs the server
+ * to use EUI-64 addressing instead of dynamic address allocation
+ * for IA_NA pools, if the parameter use-eui-64 is true for the
+ * pool. Can be at all scopes down to the pool level. Not
+ * supported by the configure script. */
+/* #define EUI_64 */
+
+/* Enable enforcement of the require option statement as documented
+ * in man page. Instructs the dhclient, when in -6 mode, to discard
+ * offered leases that do not contain all options specified as required
+ * in the client's configuration file. The client already enforces this
+ * in -4 mode. */
+#define ENFORCE_DHCPV6_CLIENT_REQUIRE
+
+/* Enable the invocation of the client script with a FAIL state code
+ * by dhclient when running in one-try mode (-T) and the attempt to
+ * obtain the desired lease(s) fails. Applies to IPv4 mode only. */
+/* #define CALL_SCRIPT_ON_ONETRY_FAIL */
+
/* Include definitions for various options. In general these
should be left as is, but if you have already defined one
- of these and prefer your definition you can comment the
+ of these and prefer your definition you can comment the
RFC define out to avoid conflicts */
+#define RFC2563_OPTIONS
#define RFC2937_OPTIONS
#define RFC4776_OPTIONS
+#define RFC4578_OPTIONS
#define RFC4833_OPTIONS
#define RFC4994_OPTIONS
+#define RFC5071_OPTIONS
#define RFC5192_OPTIONS
#define RFC5223_OPTIONS
#define RFC5417_OPTIONS
#define RFC5460_OPTIONS
+#define RFC5859_OPTIONS
#define RFC5969_OPTIONS
#define RFC5970_OPTIONS
#define RFC5986_OPTIONS
#define RFC6011_OPTIONS
+#define RFC6011_OPTIONS
+#define RFC6153_OPTIONS
#define RFC6334_OPTIONS
#define RFC6440_OPTIONS
#define RFC6731_OPTIONS
#define RFC6939_OPTIONS
#define RFC6977_OPTIONS
#define RFC7083_OPTIONS
-
+#define RFC7341_OPTIONS
+#define RFC7618_OPTIONS
+#define RFC7710_OPTIONS
+#define RFC8925_OPTIONS
projects / thirdparty / dhcp.git / blobdiff