Skip to content
GitLab
Projects
Groups
Snippets
/
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
Sebastian Schrader
Kea
Commits
0657510f
Commit
0657510f
authored
Jul 18, 2013
by
Tomek Mrugalski
🛰
Browse files
Merge branch 'trac2994' of
ssh://git.bind10.isc.org/var/bind10/git/bind10
into trac2994
parents
5b097c33
18dd133a
Changes
3
Hide whitespace changes
Inline
Side-by-side
src/bin/dhcp4/dhcp4_messages.mes
View file @
0657510f
...
...
@@ -37,7 +37,7 @@ This critical error message indicates that the initial DHCPv4
configuration has failed. The server will start, but nothing will be
served until the configuration has been corrected.
% DHCP4_CONFIG_NEW_SUBNET
A
new subnet has been added to configuration: %1
% DHCP4_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 IPv4 subnet.
...
...
@@ -60,24 +60,24 @@ This informational message is printed every time DHCPv4 server is started
and gives both the type and name of the database being used to store
lease and other information.
% DHCP4_HOOK_PACKET_RCVD_SKIP received DHCPv4 packet was dropped, because a callout set skip flag.
This debug message is printed when a callout installed on pkt4_receive
hook point sets skip flag. For this particular hook point, the
setting
of the flag
by a callout
instructs the server to drop the packet.
% DHCP4_HOOK_PACKET_SEND_SKIP
P
repared DHCPv6 response was not sent, because a callout set skip flag.
This debug message is printed when a callout installed on pkt4_send
hook point sets 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).
% DHCP4_HOOK_SUBNET4_SELECT_SKIP No subnet was selected, because a callout set skip flag.
This debug message is
p
r
int
ed when a callout installed on subnet4_select
hook point sets a skip flag. It means that the server was told that no subnet
s
hould be selected. This
severely limits further processing
-
server
will be only
able to offer global options
. N
o addresses will be assigned.
% DHCP4_HOOK_PACKET_RCVD_SKIP received DHCPv4 packet was dropped, because a callout set
the
skip flag.
This debug message is printed when a callout installed on
the
pkt4_receive
hook point sets
the
skip flag. For this particular hook point, the
setting
of the flag instructs the server to drop the packet.
% DHCP4_HOOK_PACKET_SEND_SKIP
p
repared DHCPv6 response was not sent, because a callout set skip flag.
This debug message is printed when a callout installed on
the
pkt4_send
hook point sets
the
skip flag. For this particular hook point, the setting
of the flag instructs the server to drop the packet. This
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).
% DHCP4_HOOK_SUBNET4_SELECT_SKIP no subnet was selected, because a callout set skip flag.
This debug message is printed when a callout installed on the
subnet4_select hook
p
o
int
sets the skip flag. For this particular hook
point, the setting of the flag instructs the server not to choose a
s
ubnet, an action that
severely limits further processing
; the
server
will be only
able to offer global options
- n
o addresses will be assigned.
% DHCP4_LEASE_ADVERT lease %1 advertised (client client-id %2, hwaddr %3)
This debug message indicates that the server successfully advertised
...
...
src/bin/dhcp6/dhcp6_messages.mes
View file @
0657510f
...
...
@@ -66,23 +66,25 @@ is started. It indicates what database backend type is being to store
lease and other information.
% DHCP6_HOOK_PACKET_RCVD_SKIP received DHCPv6 packet was dropped, because a callout set skip flag.
This debug message is printed when a callout installed on pkt6_receive
hook point sets skip flag. For this particular hook point, the
setting
of the flag by a callout instructs the server to drop the packet.
This debug message is printed when a callout installed on
the
pkt6_receive
hook point sets
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
P
repared DHCPv6 response was not sent, because a callout set skip flag.
This debug message is printed when a callout installed on pkt6_send
hook point sets skip flag. For this particular hook point, the setting
% DHCP6_HOOK_PACKET_SEND_SKIP
p
repared DHCPv6 response was not sent, because a callout set skip flag.
This debug message is printed when a callout installed on
the
pkt6_send
hook point sets
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 skip flag.
This debug message is printed when a callout installed on subnet6_select
hook point sets a skip flag. It means that the server was told that no subnet
should be selected. This severely limits further processing - server will be only
able to offer global options. No addresses or prefixes could be assigned.
% DHCP6_HOOK_SUBNET6_SELECT_SKIP no subnet was selected, because a callout set skip flag.
This debug message is printed when a callout installed on the
subnet6_select hook point sets 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_LEASE_ADVERT lease %1 advertised (client duid=%2, iaid=%3)
This debug message indicates that the server successfully advertised
...
...
@@ -178,10 +180,10 @@ actions and committal of changes failed. The message has been output in
response to a non-BIND 10 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 BIND 10. This
former
may be the result of an
interrupted
installation of an update to BIND 10.
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 BIND 10. This may be the result of an
interrupted
installation of an update to BIND 10.
% 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,
...
...
src/lib/dhcpsrv/dhcpsrv_messages.mes
View file @
0657510f
...
...
@@ -123,15 +123,15 @@ the new parameters.
% DHCPSRV_HOOK_LEASE4_SELECT_SKIP Lease4 creation was skipped, because of callout skip flag.
This debug message is printed when a callout installed on lease4_select
hook point sets
a
skip flag. It means that the server was told that
no lease4
should be assigned. The server will not put that lease in its
database and the client
will get a NAK packet.
hook point sets
the
skip flag. It means that the server was told that
no lease4
should be assigned. The server will not put that lease in its
database and the client
will get a NAK packet.
% DHCPSRV_HOOK_LEASE6_SELECT_SKIP Lease6 (non-temporary) creation was skipped, because of callout skip flag.
This debug message is printed when a callout installed on lease6_select
hook point sets
a
skip flag. It means that the server was told that
no lease6
should be assigned. The server will not put that lease in its
database and the client
will get a NoAddrsAvail for that IA_NA option.
hook point sets
the
skip flag. It means that the server was told that
no lease6
should be assigned. The server will not put that lease in its
database and the client
will get a NoAddrsAvail for that IA_NA option.
% DHCPSRV_INVALID_ACCESS invalid database access string: %1
This is logged when an attempt has been made to parse a database access string
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment