"DHCP4_ALREADY_RUNNING", "%1 already running? %2",
"DHCP4_BUFFER_RECEIVED", "received buffer from %1:%2 to %3:%4 over interface %5",
"DHCP4_BUFFER_RECEIVE_FAIL", "error on attempt to receive packet: %1",
- "DHCP4_BUFFER_UNPACK", "parsing buffer received from %1 to %2 over interface %3",
+ "DHCP4_BUFFER_UNPACK", "%1: parsing buffer received from %2 to %3 over interface %4",
"DHCP4_BUFFER_WAIT_SIGNAL", "signal received while waiting for next packet",
"DHCP4_CB_ON_DEMAND_FETCH_UPDATES_FAIL", "error on demand attempt to fetch configuration updates from the configuration backend(s): %1",
"DHCP4_CB_PERIODIC_FETCH_UPDATES_FAIL", "error on periodic attempt to fetch configuration updates from the configuration backend(s): %1",
"DHCP4_PACKET_NAK_0002", "%1: invalid address %2 requested by INIT-REBOOT",
"DHCP4_PACKET_NAK_0003", "%1: failed to advertise a lease, client sent ciaddr %2, requested-ip-address %3",
"DHCP4_PACKET_NAK_0004", "%1: failed to grant a lease, client sent ciaddr %2, requested-ip-address %3",
- "DHCP4_PACKET_OPTIONS_SKIPPED", "An error unpacking an option, caused subsequent options to be skipped: %1",
+ "DHCP4_PACKET_OPTIONS_SKIPPED", "%1: An error unpacking an option, caused subsequent options to be skipped: %2",
"DHCP4_PACKET_OPTION_UNPACK_FAIL", "An error unpacking the option %1: %2",
"DHCP4_PACKET_PACK", "%1: preparing on-wire format of the packet to be sent",
"DHCP4_PACKET_PACK_FAIL", "%1: preparing on-wire-format of the packet to be sent failed %2",
occurred during this attempt. The reason for the error is included in
the message.
-% DHCP4_BUFFER_UNPACK parsing buffer received from %1 to %2 over interface %3
+% DHCP4_BUFFER_UNPACK %1: parsing buffer received from %2 to %3 over interface %4
This debug message is issued when the server starts parsing the received
buffer holding the DHCPv4 message. The arguments specify the source and
destination IPv4 addresses as well as the interface over which the buffer has
in the ciaddr field. The third argument contains the IPv4 address in the
requested-ip-address option (if present).
-% DHCP4_PACKET_OPTIONS_SKIPPED An error unpacking an option, caused subsequent options to be skipped: %1
+% DHCP4_PACKET_OPTIONS_SKIPPED %1: An error unpacking an option, caused subsequent options to be skipped: %2
A debug message issued when an option failed to unpack correctly, making it
impossible to unpack the remaining options in the packet. The server will
server will still attempt to service the packet.
if (!skip_unpack) {
try {
LOG_DEBUG(options4_logger, DBG_DHCP4_DETAIL, DHCP4_BUFFER_UNPACK)
+ .arg(query->getLabel())
.arg(query->getRemoteAddr().toText())
.arg(query->getLocalAddr().toText())
.arg(query->getIface());
// anyway. Log it and let's hope for the best.
LOG_DEBUG(options4_logger, DBG_DHCP4_DETAIL,
DHCP4_PACKET_OPTIONS_SKIPPED)
+ .arg(query->getLabel())
.arg(e.what());
} catch (const std::exception& e) {
// Failed to parse the packet.
"DHCP6_ADD_STATUS_CODE_FOR_IA", "%1: adding Status Code to IA with iaid=%2: %3",
"DHCP6_ALREADY_RUNNING", "%1 already running? %2",
"DHCP6_BUFFER_RECEIVED", "received buffer from %1:%2 to %3:%4 over interface %5",
- "DHCP6_BUFFER_UNPACK", "parsing buffer received from %1 to %2 over interface %3",
+ "DHCP6_BUFFER_UNPACK", "%1: parsing buffer received from %2 to %3 over interface %4",
"DHCP6_BUFFER_WAIT_SIGNAL", "signal received while waiting for next packet",
"DHCP6_CB_ON_DEMAND_FETCH_UPDATES_FAIL", "error on demand attempt to fetch configuration updates from the configuration backend(s): %1",
"DHCP6_CB_PERIODIC_FETCH_UPDATES_FAIL", "error on periodic attempt to fetch configuration updates from the configuration backend(s): %1",
"DHCP6_PACKET_DROP_PARSE_FAIL", "%1: failed to parse packet from %2 to %3, received over interface %4, reason: %5, %6",
"DHCP6_PACKET_DROP_SERVERID_MISMATCH", "%1: dropping packet with server identifier: %2, server is using: %3",
"DHCP6_PACKET_DROP_UNICAST", "%1: dropping unicast %2 packet as this packet should be sent to multicast",
- "DHCP6_PACKET_OPTIONS_SKIPPED", "An error unpacking an option, caused subsequent options to be skipped: %1",
+ "DHCP6_PACKET_OPTIONS_SKIPPED", "%1: An error unpacking an option, caused subsequent options to be skipped: %2",
"DHCP6_PACKET_PROCESS_EXCEPTION", "exception occurred during packet processing",
"DHCP6_PACKET_PROCESS_FAIL", "%1: processing of %2 message received from %3 failed: %4",
"DHCP6_PACKET_PROCESS_STD_EXCEPTION", "exception occurred during packet processing: %1",
"DHCP6_PACKET_RECEIVE_FAIL", "error on attempt to receive packet: %1",
"DHCP6_PACKET_SEND", "%1: trying to send packet %2 (type %3) from [%4]:%5 to [%6]:%7 on interface %8",
"DHCP6_PACKET_SEND_FAIL", "failed to send DHCPv6 packet: %1",
- "DHCP6_PACK_FAIL", "failed to assemble response correctly",
+ "DHCP6_PACK_FAIL", "1%: failed to assemble response correctly: %2",
"DHCP6_PARSER_COMMIT_EXCEPTION", "parser failed to commit changes",
"DHCP6_PARSER_COMMIT_FAIL", "parser failed to commit changes: %1",
"DHCP6_PARSER_EXCEPTION", "failed to create or run parser for configuration element %1",
packet hasn't been parsed yet. The only available information is the
interface and the source and destination addresses/ports.
-% DHCP6_BUFFER_UNPACK parsing buffer received from %1 to %2 over interface %3
+% DHCP6_BUFFER_UNPACK %1: parsing buffer received from %2 to %3 over interface %4
This debug message is issued when the server starts parsing the received
buffer holding the DHCPv6 message. The arguments specify the source and
destination addresses as well as the interface over which the buffer has
specifies the client and transaction identification information, the
second argument specifies packet type.
-% DHCP6_PACKET_OPTIONS_SKIPPED An error unpacking an option, caused subsequent options to be skipped: %1
+% DHCP6_PACKET_OPTIONS_SKIPPED %1: An error unpacking an option, caused subsequent options to be skipped: %2
A debug message issued when an option failed to unpack correctly, making it
impossible to unpack the remaining options in the packet. The server will
server will still attempt to service the packet.
DHCP message to a client. The reason for the error is included in the
message.
-% DHCP6_PACK_FAIL failed to assemble response correctly
+% DHCP6_PACK_FAIL 1%: failed to assemble response correctly: %2
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.
if (!skip_unpack) {
try {
LOG_DEBUG(options6_logger, DBG_DHCP6_DETAIL, DHCP6_BUFFER_UNPACK)
+ .arg(query->getLabel())
.arg(query->getRemoteAddr().toText())
.arg(query->getLocalAddr().toText())
.arg(query->getIface());
// anyway. Log it and let's hope for the best.
LOG_DEBUG(options6_logger, DBG_DHCP6_DETAIL,
DHCP6_PACKET_OPTIONS_SKIPPED)
+ .arg(query->getLabel())
.arg(e.what());
} catch (const std::exception &e) {
// Failed to parse the packet.
try {
rsp->pack();
} catch (const std::exception& e) {
- LOG_ERROR(options6_logger, DHCP6_PACK_FAIL).arg(e.what());
+ LOG_ERROR(options6_logger, DHCP6_PACK_FAIL)
+ .arg(query->getLabel())
+ .arg(e.what());
return;
}