# Copyright (C) 2012-2014 Internet Systems Consortium, Inc. ("ISC") # # Permission to use, copy, modify, and/or distribute this software for any # purpose with or without fee is hereby granted, provided that the above # copyright notice and this permission notice appear in all copies. # # THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH # REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY # AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, # INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM # LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR # PERFORMANCE OF THIS SOFTWARE. $NAMESPACE isc::dhcp % DHCP6_ACTIVATE_INTERFACE activating interface %1 This message is printed when DHCPv6 server enabled an interface to be used to receive DHCPv6 traffic. IPv6 socket on this interface will be opened once Interface Manager starts up procedure of opening sockets. % DHCP6_CCSESSION_STARTED control channel session started on socket %1 A debug message issued during startup after the IPv6 DHCP server has successfully established a session with the Kea control channel. % DHCP6_CCSESSION_STARTING starting control channel session, specfile: %1 This debug message is issued just before the IPv6 DHCP server attempts to establish a session with the Kea control channel. % DHCP6_CLASS_ASSIGNED client packet has been assigned to the following class(es): %1 This debug message informs that incoming packet has been assigned to specified class or classes. This is a norma % DHCP6_CLIENTID_MISSING mandatory client-id option is missing, message from %1 dropped This error message indicates that the received message is being dropped because it does not include the mandatory client-id option necessary for address assignment. The most likely cause is a problem with the client. % DHCP6_COMMAND_RECEIVED received command %1, arguments: %2 A debug message listing the command (and possible arguments) received from the Kea control system by the IPv6 DHCP server. % DHCP6_CONFIG_COMPLETE DHCPv6 server has completed configuration: %1 This is an informational message announcing the successful processing of a new configuration. it is output during server startup, and when an updated configuration is committed by the administrator. Additional information may be provided. % DHCP6_CONFIG_LOAD_FAIL configuration error using file: %1, reason: %2 This error message indicates that the DHCPv6 configuration has failed. If this is an initial configuration (during server's startup) the server will fail to start. If this is a dynamic reconfiguration attempt the server will continue to use an old configuration. % DHCP6_CONFIG_NEW_SUBNET a new subnet has been added to configuration: %1 This is an informational message reporting that the configuration has been extended to include the specified subnet. % DHCP6_CONFIG_OPTION_DUPLICATE multiple options with the code: %1 added to the subnet: %2 This warning message is issued on an attempt to configure multiple options with the same option code for the particular subnet. Adding multiple options is uncommon for DHCPv6, but it is not prohibited. % DHCP6_CONFIG_RECEIVED received configuration: %1 A debug message listing the configuration received by the DHCPv6 server. The source of that configuration depends on used configuration backend. % DHCP6_CONFIG_START DHCPv6 server is processing the following configuration: %1 This is a debug message that is issued every time the server receives a configuration. That happens start up and also when a server configuration change is committed by the administrator. % DHCP6_CONFIG_UPDATE updated configuration received: %1 A debug message indicating that the IPv6 DHCP server has received an updated configuration from the Kea configuration system. % DHCP6_DB_BACKEND_STARTED lease database started (type: %1, name: %2) This informational message is printed every time the IPv6 DHCP server is started. It indicates what database backend type is being to store lease and other information. % DHCP6_DDNS_CREATE_ADD_NAME_CHANGE_REQUEST created name change request: %1 This debug message is logged when the new Name Change Request has been created to perform the DNS Update, which adds new RRs. % DHCP6_DDNS_CREATE_REMOVE_NAME_CHANGE_REQUEST created name change request: %1 This debug message is logged when the new Name Change Request has been created to perform the DNS Update, which removes RRs from the DNS. % DHCP6_DDNS_LEASE_ASSIGN_FQDN_CHANGE FQDN for the allocated lease: %1 has changed. New values: hostname = %2, reverse mapping = %3, forward mapping = %4 This debug message is logged when FQDN mapping for a particular lease has been changed by the recent Request message. This mapping will be changed in DNS. % DHCP6_DDNS_LEASE_RENEW_FQDN_CHANGE FQDN for the renewed lease: %1 has changed New values: hostname = %2, reverse mapping = %3, forward mapping = %4 This debug message is logged when FQDN mapping for a particular lease has been changed by the recent Renew message. This mapping will be changed in DNS. % DHCP6_DDNS_RECEIVE_FQDN received DHCPv6 Client FQDN Option: %1 This debug message is logged when server has found the DHCPv6 Client FQDN Option sent by a client and started processing it. % DHCP6_DDNS_REMOVE_INVALID_HOSTNAME invalid FQDN: %1 for the lease: %2 when removing DNS bindings This error message is issued when a lease being deleted contains an indication that the DNS Update has been performed for it, but the FQDN held in the lease database has invalid format and can't be transformed to the canonical on-wire format. % DHCP6_DDNS_REQUEST_SEND_FAILED failed sending a request to kea-dhcp-ddns, error: %1, ncr: %2 This error message indicates that IPv6 DHCP server failed to send a DDNS update reqeust to the DHCP-DDNS server. This is most likely a configuration or networking error. % DHCP6_DDNS_SEND_FQDN sending DHCPv6 Client FQDN Option to the client: %1 This debug message is logged when server includes an DHCPv6 Client FQDN Option in its response to the client. % DHCP6_DEACTIVATE_INTERFACE deactivate interface %1 This message is printed when DHCPv6 server disables an interface from being used to receive DHCPv6 traffic. Sockets on this interface will not be opened by the Interface Manager until interface is enabled. % DHCP6_DYNAMIC_RECONFIGURATION initate server reconfiguration using file: %1, after receiving SIGHUP signal This is the info message logged when the DHCPv6 server starts reconfiguration as a result of receiving SIGHUP signal. % DHCP6_DYNAMIC_RECONFIGURATION_FAIL dynamic server reconfiguration failed with file: %1 This is an error message logged when the dynamic reconfiguration of the DHCP server failed. % DHCP6_EXTEND_LEASE_SUBNET_SELECTED the %1 subnet was selected for client extending its lease This is a debug message informing that a given subnet was selected. It will be used for extending lifetime of the lease. This is one of the early steps in the processing of incoming client message. % DHCP6_EXTEND_LEASE_SUBNET_SELECT_FAILED failed to select a subnet for received %1: src=%2 type=%3 This warning message is output when a Renew or Rebind was received from a subnet for which the DHCPv6 server has not been configured. The cause is most likely due to a misconfiguration of the server. The packet processing will continue, but the response will only contain generic configuration parameters and no addresses or prefixes. % DHCP6_EXTEND_NA_UNKNOWN received unknown IA_NA from client (duid=%1, iaid=%2) in subnet %3 This warning message is printed when client attempts to extend the lease for the address (in the IA_NA option) but no such lease is known by the server. It typically means that client has attempted to use its lease past its lifetime: causes of this include a adjustment of the client's date/time setting or poor support on the client for sleep/recovery. A properly implemented client will recover from such a situation by restarting the lease allocation process after receiving a negative reply from the server. An alternative cause could be that the server has lost its database recently and does not recognize its well-behaving clients. This is more probable if you see many such messages. Clients will recover from this, but they will most likely get a different IP addresses and experience a brief service interruption. % DHCP6_EXTEND_NA_UNKNOWN_SUBNET %1 message received from client on unknown subnet (duid=%2, iaid=%3) A warning message indicating that a client is attempting to extend lease lifetime for the address, but the server does not have any information about the subnet this client belongs to. This may mean that faulty the mobile client changed its location and is trying to renew its old address (client is supposed to send confirm, not renew in such cases, according to RFC3315) or the server configuration has changed and information about existing subnet was removed. Note that in a sense this is worse case of DHCP6_EXTEND_NA_UNKNOWN, as not only the lease is unknown, but also the subnet is. Depending on the reasons of this condition, it may or may not correct on its own. % DHCP6_EXTEND_PD_NO_BINDING client sent a %1 message to extend lifetimes of prefixes for an unknown binding: duid=%2, iaid=%3, subnet=%4 This warning message is logged when a client attempts to extend the lifetime of the prefix it is using, but the server was unable to find the binding to which this lease belongs. This error condition has different implications for the Renew and Rebind messages. For the former, the server will respond with NoBinding status code. For the latter, the server will discard the message. % DHCP6_EXTEND_PD_UNKNOWN_SUBNET %1 message received from client on unknown subnet (duid=%2, iaid=%3) A warning message indicating that a client is attempting to extend lease lifetime for the prefix, but the server doesn't have any information about the subnet this client belongs to. % DHCP6_HOOKS_LIBS_RELOAD_FAIL reload of hooks libraries failed A "libreload" command was issued to reload the hooks libraries but for some reason the reload failed. Other error messages issued from the hooks framework will indicate the nature of the problem. % DHCP6_HOOK_BUFFER_RCVD_SKIP received DHCPv6 buffer was dropped because a callout set the skip flag This debug message is printed when a callout installed on buffer6_receive hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to drop the packet. % DHCP6_HOOK_BUFFER_SEND_SKIP prepared DHCPv6 response was dropped because a callout set the skip flag This debug message is printed when a callout installed on buffer6_send hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to drop the packet. Server completed all the processing (e.g. may have assigned, updated or released leases), but the response will not be send to the client. % DHCP6_HOOK_LEASE6_EXTEND_SKIP DHCPv6 lease lifetime was not extended because a callout set the skip flag for message %1 or lease6_rebind hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to not extend the lifetime for a lease. If client requested renewal of multiples leases (by sending multiple IA options), the server will skip the renewal of the one in question and will proceed with other renewals as usual. % DHCP6_HOOK_LEASE6_RELEASE_NA_SKIP DHCPv6 address lease was not released because a callout set the skip flag This debug message is printed when a callout installed on the lease6_release hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to not release a lease. If a client requested the release of multiples leases (by sending multiple IA options), the server will retain this particular lease and proceed with other releases as usual. % DHCP6_HOOK_LEASE6_RELEASE_PD_SKIP DHCPv6 prefix lease was not released because a callout set the skip flag This debug message is printed when a callout installed on lease6_release hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to not release a lease. If client requested release of multiples leases (by sending multiple IA options), the server will retains this particular lease and will proceed with other renewals as usual. % DHCP6_HOOK_LEASE6_RENEW_SKIP DHCPv6 lease was not renewed because a callout set the skip flag This debug message is printed when a callout installed on lease6_renew hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to not renew a lease. If client requested renewal of multiples leases (by sending multiple IA options), the server will skip the renewal of the one in question and will proceed with other renewals as usual. % DHCP6_HOOK_PACKET_RCVD_SKIP received DHCPv6 packet was dropped because a callout set the skip flag This debug message is printed when a callout installed on the pkt6_receive hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to drop the packet. % DHCP6_HOOK_PACKET_SEND_SKIP prepared DHCPv6 response was not sent because a callout set the skip flag This debug message is printed when a callout installed on the pkt6_send hook point set the skip flag. For this particular hook point, the setting of the flag by a callout instructs the server to drop the packet. This effectively means that the client will not get any response, even though the server processed client's request and acted on it (e.g. possibly allocated a lease). % DHCP6_HOOK_SUBNET6_SELECT_SKIP no subnet was selected because a callout set the skip flag This debug message is printed when a callout installed on the subnet6_select hook point set the skip flag. For this particular hook point, the setting of the flag instructs the server not to choose a subnet, an action that severely limits further processing; the server will be only able to offer global options - no addresses or prefixes will be assigned. % DHCP6_INIT_FAIL failed to initialize Kea server: %1 The server has failed to establish communication with the rest of Kea, failed to read JSON configuration file or excountered any other critical issue that prevents it from starting up properly. Attached error message provides more details about the issue. % DHCP6_LEASE_ADVERT address lease %1 advertised (client duid=%2, iaid=%3) This debug message indicates that the server successfully advertised an address lease. It is up to the client to choose one server out of the advertised servers and continue allocation with that server. This is a normal behavior and indicates successful operation. % DHCP6_LEASE_ADVERT_FAIL failed to advertise an address lease for client duid=%1, iaid=%2 This message indicates that in response to a received SOLICIT, the server failed to advertise a non-temporary lease for a given client. There may be many reasons for such failure. Each failure is logged in a separate log entry. % DHCP6_LEASE_ALLOC address lease %1 has been allocated (client duid=%2, iaid=%3) This debug message indicates that in response to a client's REQUEST message, the server successfully granted an non-temporary address lease. This is a normal behavior and indicates successful operation. % DHCP6_LEASE_ALLOC_FAIL failed to grant an address lease for client duid=%1, iaid=%2 This message indicates that in response to a received REQUEST, the server failed to grant a non-temporary address lease for the client. There may be many reasons for such failure. Each failure is logged in a separate log entry. % DHCP6_LEASE_DATABASE_TIMERS_EXEC_FAIL failed to execute timer-based functions for lease database: %1 A warning message executed when a server process is unable to execute the periodic actions for the lease database. An example of the periodic action is a Lease File Cleanup. One of the reasons for the failure is a misconfiguration of the lease database, whereby the lease database hasn't been selected. % DHCP6_LEASE_NA_WITHOUT_DUID address lease for address %1 does not have a DUID This error message indicates a database consistency problem. The lease database has an entry indicating that the given address is in use, but the lease does not contain any client identification. This is most likely due to a software error: please raise a bug report. As a temporary workaround, manually remove the lease entry from the database. % DHCP6_LEASE_PD_WITHOUT_DUID prefix lease for address %1 does not have a DUID This error message indicates a database consistency failure. The lease database has an entry indicating that the given prefix is in use, but the lease does not contain any client identification. This is most likely due to a software error: please raise a bug report. As a temporary workaround, manually remove the lease entry from the database. % DHCP6_NAME_GEN_UPDATE_FAIL failed to update the lease using address %1, after generating FQDN for a client, reason: %2 This message indicates the failure when trying to update the lease and/or options in the server's response with the hostname generated by the server from the acquired address. % DHCP6_NOT_RUNNING IPv6 DHCP server is not running A warning message is issued when an attempt is made to shut down the IPv6 DHCP server but it is not running. % DHCP6_NO_INTERFACES failed to detect any network interfaces During startup the IPv6 DHCP server failed to detect any network interfaces and is therefore shutting down. % DHCP6_NO_SOCKETS_OPEN no interface configured to listen to DHCP traffic This warning message is issued when current server configuration specifies no interfaces that server should listen on, or specified interfaces are not configured to receive the traffic. % DHCP6_OPEN_SOCKET opening sockets on port %1 A debug message issued during startup, this indicates that the IPv6 DHCP server is about to open sockets on the specified port. % DHCP6_OPEN_SOCKET_FAIL failed to open socket: %1 A warning message issued when IfaceMgr fails to open and bind a socket. The reason for the failure is appended as an argument of the log message. % DHCP6_PACKET_MISMATCH_SERVERID_DROP dropping packet %1 (transid=%2, interface=%3) having mismatched server identifier A debug message noting that server has received message with server identifier option that not matching server identifier that server is using. % DHCP6_PACKET_PARSE_FAIL failed to parse incoming packet: %1 The DHCPv6 server has received a packet that it is unable to interpret. There may be many causes: truncated header, truncated or malformed option, trailing padding that contains garbage etc. More information is specified as a parameter. % DHCP6_PACKET_PROCESS_FAIL processing of %1 message received from %2 failed: %3 This is a general catch-all message indicating that the processing of the specified packet type from the indicated address failed. The reason is given in the message. The server will not send a response but will instead ignore the packet. % DHCP6_PACKET_RECEIVED %1 packet received A debug message noting that the server has received the specified type of packet. Note that a packet marked as UNKNOWN may well be a valid DHCP packet, just a type not expected by the server (e.g. it will report a received OFFER packet as UNKNOWN). % DHCP6_PACKET_RECEIVE_FAIL error on attempt to receive packet: %1 The IPv6 DHCP server tried to receive a packet but an error occurred during this attempt. The reason for the error is included in the message. % DHCP6_PACKET_SEND_FAIL failed to send DHCPv6 packet: %1 This error is output if the IPv6 DHCP server fails to send an assembled DHCP message to a client. The reason for the error is included in the message. % DHCP6_PACK_FAIL failed to assemble response correctly This error is output if the server failed to assemble the data to be returned to the client into a valid packet. The reason is most likely to be to a programming error: please raise a bug report. % DHCP6_PARSER_COMMIT_EXCEPTION parser failed to commit changes On receipt of message containing details to a change of the IPv6 DHCP server configuration, a set of parsers were successfully created, but one of them failed to commit its changes due to a low-level system exception being raised. Additional messages may be output indicating the reason. % DHCP6_PARSER_COMMIT_FAIL parser failed to commit changes: %1 On receipt of message containing details to a change of the IPv6 DHCP server configuration, a set of parsers were successfully created, but one of them failed to commit its changes. The reason for the failure is given in the message. % DHCP6_PARSER_CREATED created parser for configuration element %1 A debug message output during a configuration update of the IPv6 DHCP server, notifying that the parser for the specified configuration element has been successfully created. % DHCP6_PARSER_EXCEPTION failed to create or run parser for configuration element %1 On receipt of message containing details to a change of its configuration, the IPv6 DHCP server failed to create a parser to decode the contents of the named configuration element, or the creation succeeded but the parsing actions and committal of changes failed. The message has been output in response to a non-Kea exception being raised. Additional messages may give further information. The most likely cause of this is that the specification file for the server (which details the allowable contents of the configuration) is not correct for this version of Kea. This may be the result of an interrupted installation of an update to Kea. % DHCP6_PARSER_FAIL failed to create or run parser for configuration element %1: %2 On receipt of message containing details to a change of its configuration, the IPv6 DHCP server failed to create a parser to decode the contents of the named configuration element, or the creation succeeded but the parsing actions and committal of changes failed. The reason for the failure is given in the message. % DHCP6_PD_LEASE_ADVERT prefix lease %1/%2 advertised (client duid=%3, iaid=%4) This debug message indicates that the server successfully advertised a prefix lease. It is up to the client to choose one server out of the advertised servers and continue allocation with that server. This is a normal behavior and indicates successful operation. % DHCP6_PD_LEASE_ADVERT_FAIL failed to advertise a prefix lease for client duid=%1, iaid=%2 This message indicates that in response to a received SOLICIT, the server failed to advertise a prefix lease for the client. There may be many reasons for such failure. Each failure is logged in a separate log entry. % DHCP6_PD_LEASE_ALLOC prefix lease %1/%2 has been allocated (client duid=%3, iaid=%4) This debug message indicates that in response to a client's REQUEST message, the server successfully granted a prefix delegation lease. This is a normal behavior and indicates successful operation. % DHCP6_PD_LEASE_ALLOC_FAIL failed to grant a prefix lease for client duid=%1, iaid=%2 This message indicates that the server failed to grant (in response to received REQUEST) a prefix lease for a given client. There may be many reasons for such failure. Each failure is logged in a separate log entry. % DHCP6_PROCESS_IA_NA_REQUEST server is processing IA_NA option (duid=%1, iaid=%2, hint=%3) This is a debug message that indicates the processing of a received IA_NA option. It may optionally contain an address that may be used by the server as a hint for possible requested address. % DHCP6_PROCESS_IA_PD_REQUEST server is processing IA_PD option (duid=%1, iaid=%2, hint=%3) This is a debug message that indicates a processing of received IA_PD option. It may optionally contain an prefix that may be used by the server as a hint for possible requested prefix. % DHCP6_QUERY_DATA received packet length %1, data length %2, data is %3 A debug message listing the data received from the client or relay. % DHCP6_RELEASE_MISSING_CLIENTID client (address=%1) sent RELEASE message without mandatory client-id This warning message indicates that client sent RELEASE message without mandatory client-id option. This is most likely caused by a buggy client (or a relay that malformed forwarded message). This request will not be processed and a response with error status code will be sent back. % DHCP6_RELEASE_NA address %1 belonging to client duid=%2, iaid=%3 was released properly This debug message indicates that an address was released properly. It is a normal operation during client shutdown. % DHCP6_RELEASE_NA_FAIL failed to remove address lease for address %1 for duid=%2, iaid=%3 This error message indicates that the software failed to remove an address lease from the lease database. It probably due to an error during a database operation: resolution will most likely require administrator intervention (e.g. check if DHCP process has sufficient privileges to update the database). It may also be triggered if a lease was manually removed from the database during RELEASE message processing. % DHCP6_RELEASE_NA_FAIL_WRONG_DUID client (duid=%1) tried to release address %2, but it belongs to another client (duid=%3) This warning message indicates that a client tried to release an address that belongs to a different client. This should not happen in normal circumstances and may indicate a misconfiguration of the client. However, since the client releasing the address will stop using it anyway, there is a good chance that the situation will correct itself. % DHCP6_RELEASE_NA_FAIL_WRONG_IAID client (duid=%1) tried to release address %2, but it used wrong IAID (expected %3, but got %4) This warning message indicates that client tried to release an address that does belong to it, but the address was expected to be in a different IA (identity association) container. This probably means that the client's support for multiple addresses is flawed. % DHCP6_RELEASE_PD prefix %1 belonging to client duid=%2, iaid=%3 was released properly This debug message indicates that a prefix was released properly. It is a normal operation during client shutdown. % DHCP6_RELEASE_PD_FAIL failed to remove prefix lease for address %1 for duid=%2, iaid=%3 This error message indicates that the software failed to remove a prefix lease from the lease database. It probably due to an error during a database operation: resolution will most likely require administrator intervention (e.g. check if DHCP process has sufficient privileges to update the database). It may also be triggered if a lease was manually removed from the database during RELEASE message processing. % DHCP6_RELEASE_PD_FAIL_WRONG_DUID client (duid=%1) tried to release prefix %2, but it belongs to another client (duid=%3) This warning message indicates that client tried to release a prefix that belongs to a different client. This should not happen in normal circumstances and may indicate a misconfiguration of the client. However, since the client releasing the prefix will stop using it anyway, there is a good chance that the situation will correct itself. % DHCP6_RELEASE_PD_FAIL_WRONG_IAID client (duid=%1) tried to release prefix %2, but it used wrong IAID (expected %3, but got %4) This warning message indicates that client tried to release a prefix that does belong to it, but the address was expected to be in a different IA (identity association) container. This probably means that the client's support for multiple prefixes is flawed. % DHCP6_REQUIRED_OPTIONS_CHECK_FAIL %1 message received from %2 failed the following check: %3 This message indicates that received DHCPv6 packet is invalid. This may be due to a number of reasons, e.g. the mandatory client-id option is missing, the server-id forbidden in that particular type of message is present, there is more than one instance of client-id or server-id present, etc. The exact reason for rejecting the packet is included in the message. % DHCP6_RESPONSE_DATA responding with packet type %1 data is %2 A debug message listing the data returned to the client. % DHCP6_SERVERID_GENERATED server-id %1 has been generated and will be stored in %2 This informational messages indicates that the server was not able to read its server identifier (DUID) and has generated a new one. This server-id will be stored in a file and will be read and used during next restart. It is normal behavior when the server is started for the first time. If this message is printed every start, please check that the server have sufficient permission to write its server-id file and that the file is not corrupt. Changing the server identifier in a production environment is not recommended as existing clients will not recognize the server and may go through a rebind phase. However, they should be able to recover without losing their leases. % DHCP6_SERVERID_LOADED server-id %1 has been loaded from file %2 This debug message indicates that the server loaded its server identifier. That value is sent in all server responses and clients use it to discriminate between servers. This is a part of normal startup or reconfiguration procedure. % DHCP6_SERVERID_WRITE_FAIL server was not able to write its ID to file %1 This warning message indicates that server was not able to write its server identifier (DUID) to a file. This likely indicates lack of write permission to a given file or directory. This is not critical and the server will continue to operate, but server will generate different DUID during every start and clients will need to go through a rebind phase to recover. % DHCP6_SERVER_FAILED server failed: %1 The IPv6 DHCP server has encountered a fatal error and is terminating. The reason for the failure is included in the message. % DHCP6_SHUTDOWN server shutdown The IPv6 DHCP server has terminated normally. % DHCP6_SHUTDOWN_REQUEST shutdown of server requested This debug message indicates that a shutdown of the IPv6 server has been requested via a call to the 'shutdown' method of the core Dhcpv6Srv object. % DHCP6_SOCKET_UNICAST server is about to open socket on address %1 on interface %2 This is a debug message that inform that a unicast socket will be opened. % DHCP6_SRV_CONSTRUCT_ERROR error creating Dhcpv6Srv object, reason: %1 This error message indicates that during startup, the construction of a core component within the IPv6 DHCP server (the Dhcpv6 server object) has failed. As a result, the server will exit. The reason for the failure is given within the message. % DHCP6_STANDALONE skipping message queue, running standalone This is a debug message indicating that the IPv6 server is running in standalone mode, not connected to the message queue. Standalone mode is only useful during program development, and should not be used in a production environment. % DHCP6_STARTING Kea DHCPv6 server version %1 starting This informational message indicates that the IPv6 DHCP server has processed any command-line switches and is starting. The version is also printed. % DHCP6_START_INFO pid: %1, port: %2, verbose: %3 This is a debug message issued during the IPv6 DHCP server startup. It lists some information about the parameters with which the server is running. % DHCP6_SUBNET_SELECTED the %1 subnet was selected for client assignment This is a debug message informing that a given subnet was selected. It will be used for address and option assignment. This is one of the early steps in the processing of incoming client message. % DHCP6_SUBNET_SELECTION_FAILED failed to select a subnet for incoming packet, src=%1 type=%2 This warning message is output when a packet was received from a subnet for which the DHCPv6 server has not been configured. The cause is most likely due to a misconfiguration of the server. The packet processing will continue, but the response will only contain generic configuration parameters and no addresses or prefixes. % DHCP6_UNKNOWN_MSG_RECEIVED received unknown message (type %d) on interface %2 This debug message is printed when server receives a message of unknown type. That could either mean missing functionality or invalid or broken relay or client. The list of formally defined message types is available here: http://www.iana.org/assignments/dhcpv6-parameters. % DHCP6_UNKNOWN_RELEASE_NA received RELEASE from unknown client (IA_NA, duid=%1, iaid=%2) This warning message is printed when client attempts to release an address lease, but no such lease is known by the server. See the explanation of the status code DHCP6_UNKNOWN_RENEW_NA for possible reasons for such behavior. % DHCP6_UNKNOWN_RELEASE_PD received RELEASE from unknown client (IA_PD, duid=%1, iaid=%2) This warning message is printed when client attempts to release an prefix lease, but no such lease is known by the server. See the explanation of the status code DHCP6_UNKNOWN_RENEW_PD for possible reasons for such behavior.