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
ISC Open Source Projects
Kea
Commits
80360862
Commit
80360862
authored
Sep 25, 2017
by
Francis Dupont
Browse files
[5073a] Attempt to resolve last review comments
parent
3ea49f84
Changes
2
Hide whitespace changes
Inline
Side-by-side
doc/examples/kea4/advanced.json
View file @
80360862
...
...
@@ -36,9 +36,13 @@
"re-detect"
:
true
},
//
Option
43
last
resort
definition
can
make
legal
messages
to
be
//
rejected
because
they
use
not
compatible
"raw"
value.
//
The
option
definition
can
be
applied
to
avoid
this
problem.
//
Option
43
last
resort
definition
can
make
well-formed
messages
//
to
be
rejected
because
they
use
not
compatible
"raw"
value
,
//
and
different
vendors
may
define
different
sub-options.
//
The
option
definition
should
be
applied
to
avoid
these
problems
,
//
for
instance
by
defining
at
the
global
scope
the
option
as
binary.
//
In
client-classes
the
option
may
be
redefined
as
carrying
vendor
//
dependent
sub-options.
"option-def"
:
[
{
"name"
:
"vendor-encapsulated-options"
,
"code"
:
43
,
...
...
doc/guide/dhcp4-srv.xml
View file @
80360862
...
...
@@ -1527,10 +1527,105 @@ It is merely echoed by the server
Options with code between 224 and 254 are reserved for private use.
They can be defined at the global scope or at client class local
scope: this allows to use option definitions depending on context
and to set option data accordingly.
and to set option data accordingly. For instance to configure
an old PXEClient vendor:
<screen>
"Dhcp4": {
"client-class": [
{
<userinput>
"name": "pxeclient",
"test": "option[vendor-class-identifier].text == 'PXEClient'",
"option-def": [
{
"name": "configfile",
"code": 209,
"type": "string"
}
],
</userinput>
...
}, ...
],
...
}
</screen>
</para>
<para>
As the Vendor Specific Information option (code 43) has vendor
specific format, i.e. can carry either raw binary value or
sub-options, this mechanism is available for this option too.
</para>
<para>
In the following example taken from a real configuration two vendor
classes use the option 43 for different and incompatible purposes:
<screen>
"Dhcp4": {
"option-def": [
{
<userinput>
"name": "cookie",
"code": 1,
"type": "string",
"space": "APC"
},
{
"name": "mtftp-ip",
"code": 1,
"type": "ipv4-address",
"space": "PXE"
},
</userinput>
...
],
"client-class": [
{
<userinput>
"name": "APC",
"test": "(option[vendor-class-identifier].text == 'APC'",
"option-def": [
{
"name": "vendor-encapsulated-options",
"type": "empty",
"encapsulate": "APC"
}
],
"option-data": [
{
"name": "cookie",
"space": "APC",
"data": "1APC"
},
{
"name": "vendor-encapsulated-options"
},
</userinput>
...
],
...
},
{
<userinput>
"name": "PXE",
"test": "(option[vendor-class-identifier].text == 'PXE'",
"option-def": [
{
"name": "vendor-encapsulated-options",
"type": "empty",
"encapsulate": "PXE"
}
],
"option-data": [
{
"name": "mtftp-ip",
"space": "PXE",
"data": "0.0.0.0"
},
{
"name": "vendor-encapsulated-options"
},
</userinput>
...
],
...
},
...
],
...
}
</screen>
</para>
<para>
The definition used to decode a VSI option is:
...
...
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