Impet
А что эти строки означают? Если пойму ЧТО сделать, то может разберусь и КАК сделать.
Чуток поиска и ответ готов :
3.1.5. Encapsulation
Sometimes also called 'Sub-Options', encapsulated options are any
condition where DHCP-mimicing option formats are placed inside DHCP
Option contents.
To support such Encapsulation, the server must first present an
alternative 'site option space', the device that maps the
Encapsulated option codes into sub-option names.
The [value] text for an Encapsulated option is:
encapsulate "[option-space-name]"
But this is an incomplete description of how to configure
encapsulated options. So, here is an example of a Vendor
Encapsulated Option [2]:
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-oport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option PXE.discovery-control code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr code 7 = unsigned integer 8;
class "pxeclients" {
match if substring(option vendor-class-identifier, 0,
9) = "PXEClient";
vendor-option-space PXE;
}
# Alternatively:
#option vendor-encaps code 43 = encapsulate PXE;
In the above example, manual configuration is necessary, because it
is impossible (and possibly improper) for the internal tables to
document all possible Vendor-Specific interpretations of option code
43, Vendor Encapsulated Options.
Multiple Vendor-Encapsulated spaces may be supported by utilizing the
vendor-option-space configuration directive. This automatically
aliases the configured option space into the option 43 encapsulation,
as exampled above, if there is some good reason to think the client
will use it. Obviously, only one option space is used to form option
contents on the wire.
For other options (or to not support multiple vendor option spaces),
an option code may be explicitly defined to consume a specific option
space.
In other examples, however, manual configuration is not necessary,
because they've been described by an RFC and have a standard format.
So they can be included in the software's default internal tables,
for example:
{ "nwip-suboptions", "Enwip.", &dhcp_universe, 63 },
The 'E' byte indicates the format of the option is encapsulated
options. The following bytes up to the '.' byte indicate the name of
the option space to be used for encapsulation. How this option space
is configured to have a name that is meaningful is unimportant, but
within that option space the NWIP Sub Options [5] may be defined:
{ "nsq-broadcast", "f", &nwip_universe, 5 },
{ "preferred-dss", "IA", &nwip_universe, 6 },
{ "nearest-nwip-server", "IA", &nwip_universe, 7 },
{ "autoretries", "B", &nwip_universe, 8 },
{ "autoretry-secs", "B", &nwip_universe, 9 },
{ "nwip-1-1", "f", &nwip_universe, 10 },
{ "primary-dss", "I", &nwip_universe, 11 },
On the wire, an encapsulated option itself contains DHCP-like sub-
options. That is, single code bytes, single length bytes, followed
by that number of octets. The meaning and format of those octets
depends upon the definition in the encapsulated option space.
One doesn't normally configure an encapsulated option...rather one
configures the encapsulated option space, in the format specific to
each option in that space. But if one did, one would use a colon-
separated hexadecimal string. Examples:
option PXE.mtftp-ip 0.0.0.0;
# Alternatively.
#option vendor-encapsulated-options 01:04:00:00:00;
option nwip.nsq-broadcast true;
option nwip.nearest-nwip-server 10.0.0.1;
# Alternatively.
#option nwip-suboptions 05:01:01:07:04:0A:00:00:01;
One also doesn't normally present an encapsulated option...rather one
consumes the individual option from its option space, and so that
option is presented depending upon its specific format. But if you
did, likewise to configuring, it would be presented as a colon-
separated hexadecimal string.
For each suboption, you can look at presentation examples elsewhere
in this document. For whole-option consumption however, it would
look (identically as above) like so:
01:04:00:00:00:00
05:01:01:07:04:0A:00:00:01
А что эти строки означают? Если пойму ЧТО сделать, то может разберусь и КАК сделать.
Чуток поиска и ответ готов :
3.1.5. Encapsulation
Sometimes also called 'Sub-Options', encapsulated options are any
condition where DHCP-mimicing option formats are placed inside DHCP
Option contents.
To support such Encapsulation, the server must first present an
alternative 'site option space', the device that maps the
Encapsulated option codes into sub-option names.
The [value] text for an Encapsulated option is:
encapsulate "[option-space-name]"
But this is an incomplete description of how to configure
encapsulated options. So, here is an example of a Vendor
Encapsulated Option [2]:
option space PXE;
option PXE.mtftp-ip code 1 = ip-address;
option PXE.mtftp-oport code 2 = unsigned integer 16;
option PXE.mtftp-sport code 3 = unsigned integer 16;
option PXE.mtftp-tmout code 4 = unsigned integer 8;
option PXE.mtftp-delay code 5 = unsigned integer 8;
option PXE.discovery-control code 6 = unsigned integer 8;
option PXE.discovery-mcast-addr code 7 = unsigned integer 8;
class "pxeclients" {
match if substring(option vendor-class-identifier, 0,
9) = "PXEClient";
vendor-option-space PXE;
}
# Alternatively:
#option vendor-encaps code 43 = encapsulate PXE;
In the above example, manual configuration is necessary, because it
is impossible (and possibly improper) for the internal tables to
document all possible Vendor-Specific interpretations of option code
43, Vendor Encapsulated Options.
Multiple Vendor-Encapsulated spaces may be supported by utilizing the
vendor-option-space configuration directive. This automatically
aliases the configured option space into the option 43 encapsulation,
as exampled above, if there is some good reason to think the client
will use it. Obviously, only one option space is used to form option
contents on the wire.
For other options (or to not support multiple vendor option spaces),
an option code may be explicitly defined to consume a specific option
space.
In other examples, however, manual configuration is not necessary,
because they've been described by an RFC and have a standard format.
So they can be included in the software's default internal tables,
for example:
{ "nwip-suboptions", "Enwip.", &dhcp_universe, 63 },
The 'E' byte indicates the format of the option is encapsulated
options. The following bytes up to the '.' byte indicate the name of
the option space to be used for encapsulation. How this option space
is configured to have a name that is meaningful is unimportant, but
within that option space the NWIP Sub Options [5] may be defined:
{ "nsq-broadcast", "f", &nwip_universe, 5 },
{ "preferred-dss", "IA", &nwip_universe, 6 },
{ "nearest-nwip-server", "IA", &nwip_universe, 7 },
{ "autoretries", "B", &nwip_universe, 8 },
{ "autoretry-secs", "B", &nwip_universe, 9 },
{ "nwip-1-1", "f", &nwip_universe, 10 },
{ "primary-dss", "I", &nwip_universe, 11 },
On the wire, an encapsulated option itself contains DHCP-like sub-
options. That is, single code bytes, single length bytes, followed
by that number of octets. The meaning and format of those octets
depends upon the definition in the encapsulated option space.
One doesn't normally configure an encapsulated option...rather one
configures the encapsulated option space, in the format specific to
each option in that space. But if one did, one would use a colon-
separated hexadecimal string. Examples:
option PXE.mtftp-ip 0.0.0.0;
# Alternatively.
#option vendor-encapsulated-options 01:04:00:00:00;
option nwip.nsq-broadcast true;
option nwip.nearest-nwip-server 10.0.0.1;
# Alternatively.
#option nwip-suboptions 05:01:01:07:04:0A:00:00:01;
One also doesn't normally present an encapsulated option...rather one
consumes the individual option from its option space, and so that
option is presented depending upon its specific format. But if you
did, likewise to configuring, it would be presented as a colon-
separated hexadecimal string.
For each suboption, you can look at presentation examples elsewhere
in this document. For whole-option consumption however, it would
look (identically as above) like so:
01:04:00:00:00:00
05:01:01:07:04:0A:00:00:01
Добавление от 20.08.2007 10:28:
http://forums.kerio.com/index.php?t=msg&goto=393…0ab4bdc7904263116