<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>hi,</p>
<p><br>
</p>
<p>wrote an article about the use of option 43 in KEA for Cisco PnP.
Perhaps you can get inspiration from there.</p>
<p><a class="moz-txt-link-freetext" href="https://blog.sys4.de/blog/kea-veos/">https://blog.sys4.de/blog/kea-veos/</a></p>
<p><br>
</p>
<p>Michael.</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 22.06.23 12:27, Kraishak Mahtha
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADDat85t7eZorz2MqdEjz23fJ9dVOC0LxM6FAaw6f4Do_ePWQg@mail.gmail.com">
<div dir="ltr"> kea-dhcp4 -t kea-dhcp4.conf.option43<br>
Syntax check failed with: kea-dhcp4.conf.option43:67.14-25: got
unexpected keyword "option-def" in subnet4 map<br>
<div><br>
</div>
<div>It is saying we cannot use the option-def inside the
subnet4 section, It should be within class-def or in the
global section I guess</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, Jun 20, 2023 at
3:08 PM Darren Ankney <<a
href="mailto:darren.ankney@gmail.com" moz-do-not-send="true"
class="moz-txt-link-freetext">darren.ankney@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote">Hi Kraishak,<br>
<br>
Please provide the error message that you received.<br>
<br>
Thank you,<br>
<br>
Darren Ankney<br>
<br>
On Sun, Jun 18, 2023 at 1:34 AM Kraishak Mahtha <<a
href="mailto:kraishak.edu@gmail.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">kraishak.edu@gmail.com</a>>
wrote:<br>
><br>
> Hi Darren,<br>
> This might be best kept out of the global area (use in
subnet, classes etc..),<br>
> ------>do you mean the following?<br>
><br>
> "subnet4": [<br>
> {<br>
> "subnet": "<a href="http://4.0.0.0/16"
rel="noreferrer" target="_blank" moz-do-not-send="true">4.0.0.0/16</a>",<br>
> "valid-lifetime": 86400,<br>
> "option-def": [{<br>
> "code": 43,<br>
> "name": "vendor-encapsulated-options",<br>
> "type": "string",<br>
> "space": "dhcp4"<br>
> }],<br>
> "option-data": [<br>
> {<br>
> "name": "vendor-encapsulated-options",<br>
> "data": "any old string"<br>
> },<br>
> {<br>
> "data": "6.6.6.6, 7.7.7.7, 8.8.8.4",<br>
> "name": "domain-name-servers"<br>
> },<br>
> {<br>
> "data": "86400",<br>
> "name": "dhcp-lease-time"<br>
> },<br>
> {<br>
> "data": "255.255.0.0",<br>
> "name": "subnet-mask"<br>
> },<br>
> {<br>
> "data": "4.0.0.1",<br>
> "name": "routers"<br>
> }],<br>
> "pools": [<br>
> {<br>
> "pool": "4.0.0.2-4.0.6.125"<br>
> }<br>
> ],<br>
> "id": 786173<br>
> },<br>
> but it gives a syntax error for me and I don't see any
reference in any forums too that declares the option
definition within the subnet.<br>
><br>
><br>
> On Thu, Jun 15, 2023 at 9:21 PM Darren Ankney <<a
href="mailto:darren.ankney@gmail.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">darren.ankney@gmail.com</a>>
wrote:<br>
>><br>
>> Hi Kraishak,<br>
>><br>
>> I am informed by a colleague that you can redefine
the expected<br>
>> contents of option 43 as shown:<br>
>> "option-def": [<br>
>> {<br>
>> "name": "vendor-encapsulated-options",<br>
>> "code": 43,<br>
>> "type": "string"<br>
>> }<br>
>> "option-data": [<br>
>> {<br>
>> "name": "vendor-encapsulated-options",<br>
>> "data": "any old string"<br>
>> },<br>
>> ]<br>
>> which will allow you to store strings directly in the
option. This<br>
>> might be best kept out of the global area (use in
subnet, classes<br>
>> etc..), however, in case you need to use option 43 in
the default way<br>
>> with sub-options.<br>
>><br>
>> Thank you,<br>
>><br>
>> Darren Ankney<br>
>><br>
>> On Wed, Jun 14, 2023 at 10:03 AM Kraishak Mahtha <<a
href="mailto:kraishak.edu@gmail.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">kraishak.edu@gmail.com</a>>
wrote:<br>
>> ><br>
>> > Yes, for a few of my lab centers that run using
the ISC, I have checked the config and they only have option
43 in their subnet without any option spaces so I thought it
would be the same for kea.<br>
>> > I don't have much familiarity with this option
43 but the current clients in the subnet do use option 43, My
existing production has the same options with different values
(a domain, number, and text) . I just replaced them with some
random text and I am checking the tcpdump of both ISC and Kea
server output to make sure I see the same results.<br>
>> ><br>
>> > In ISC tcpdump I can see the option value for
option 43 and for kea, it is missing completely<br>
>> ><br>
>> > TIME: 13:59:13.451640<br>
>> > IP: > (00:50:56:99:38:1c) >
(00:50:56:99:5c:f3)<br>
>> > OP: 2 (BOOTPREPLY)<br>
>> > HTYPE: 1 (Ethernet)<br>
>> > HLEN: 6<br>
>> > HOPS: 0<br>
>> > XID: 36835441<br>
>> > SECS: 0<br>
>> > FLAGS: 7f80<br>
>> > CIADDR: 0.0.0.0<br>
>> > YIADDR: 3.4.0.2<br>
>> > SIADDR: 0.0.0.0<br>
>> > GIADDR: 3.4.0.1<br>
>> > CHADDR:
a1:21:2f:00:00:01:00:00:00:00:00:00:00:00:00:00<br>
>> > SNAME: .<br>
>> > FNAME: .<br>
>> > OPTION: 53 ( 1) DHCP message type 5
(DHCPACK)<br>
>> > OPTION: 54 ( 4) Server identifier
192.168.0.81<br>
>> > OPTION: 51 ( 4) IP address leasetime
86400 (24h)<br>
>> > OPTION: 1 ( 4) Subnet mask
255.255.0.0<br>
>> > OPTION: 3 ( 4) Routers
3.4.0.1<br>
>> > OPTION: 6 ( 12) DNS server
6.6.6.6,7.7.7.7,8.8.8.4<br>
>> > OPTION: 15 ( 11) Domainname <a
href="http://test.com" rel="noreferrer" target="_blank"
moz-do-not-send="true">test.com</a><br>
>> > OPTION: 43 ( 11) Vendor specific info
74657374 test<br>
>> ><br>
>> ><br>
>> > >>It sounds like you should be able to
send data that isn't a suboption, but I cannot find anywhere
in the ARM that indicates that Kea supports this.<br>
>> > ---> This is the major thing if we have
different behavior change for option 43 in kea compared to ISC<br>
>> ><br>
>> > On Wed, Jun 14, 2023 at 6:48 PM Darren Ankney
<<a href="mailto:darren.ankney@gmail.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">darren.ankney@gmail.com</a>>
wrote:<br>
>> >><br>
>> >> Hi Kraishak,<br>
>> >><br>
>> >> I don't know if I can provide more specific
information than is<br>
>> >> contained in the RFC 2132 section about
option 43:<br>
>> >> <a
href="https://www.rfc-editor.org/rfc/rfc2132#section-8.4"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.rfc-editor.org/rfc/rfc2132#section-8.4</a><br>
>> >><br>
>> >> According to the RFC, the data in option 43
is "opaque" as it is meant<br>
>> >> to be vendor specific. It sounds like you
should be able to send data<br>
>> >> that isn't a suboption, but I cannot find
anywhere in the ARM that<br>
>> >> indicates that Kea supports this. It
definitely supports sending<br>
>> >> sub-options of option 43 which is the usual
case encountered in<br>
>> >> practice.<br>
>> >><br>
>> >> Thank you,<br>
>> >><br>
>> >> Darren Ankney<br>
>> >><br>
>> >> On Wed, Jun 14, 2023 at 8:46 AM Kraishak
Mahtha <<a href="mailto:kraishak.edu@gmail.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">kraishak.edu@gmail.com</a>>
wrote:<br>
>> >> ><br>
>> >> > Hi Darren,<br>
>> >> ><br>
>> >> > I am testing for each option and its
corresponding behavior in kea by checking the tcpdump and
packet4.log mainly<br>
>> >> ><br>
>> >> > Can you please confirm one thing, so
basically to use option 43 do we must need to define the
vendor-encapsulated-options-space in both ISC and Kea-DHCP?<br>
>> >> ><br>
>> >> > I am a bit confused here, maybe it
would be basic but can you please give me more info on it or
any reference link so that I can understand the scope of
option 43<br>
>> >> ><br>
>> >> > Thanks In Advance<br>
>> >> > Kraishak<br>
>> >> ><br>
>> >> > On Tue, Jun 13, 2023 at 6:08 PM Darren
Ankney <<a href="mailto:darren.ankney@gmail.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">darren.ankney@gmail.com</a>>
wrote:<br>
>> >> >><br>
>> >> >> Hi Kraishak,<br>
>> >> >><br>
>> >> >> Does this do something for some
device you are trying to support?<br>
>> >> >><br>
>> >> >> option vendor-encapsulated-options
"test";<br>
>> >> >><br>
>> >> >> Typically, option 43 is defined on
the basis of something that a<br>
>> >> >> vendor device needs to receive.
That gives some constraints regarding<br>
>> >> >> how it is configured. Most of the
time, it will be a collection of<br>
>> >> >> one or more sub-options. For
example, here is one vendor's passing of<br>
>> >> >> a URL for tr69 in ISC DHCP:<br>
>> >> >><br>
>> >> >> option space CALIXGC;<br>
>> >> >> option CALIXGC.acs-url code 1 =
text;<br>
>> >> >> vendor-option-space CALIXGC;<br>
>> >> >> option CALIXGC.acs-url "<a
href="http://someurl" rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://someurl</a>";<br>
>> >> >><br>
>> >> >> which, translated to Kea, would
look like this:<br>
>> >> >><br>
>> >> >> "option-def": [<br>
>> >> >> {<br>
>> >> >> "space": "CALIXGC",<br>
>> >> >> "name": "acs-url",<br>
>> >> >> "code": 1,<br>
>> >> >> "type": "string"<br>
>> >> >> },<br>
>> >> >> {<br>
>> >> >> "name":
"vendor-encapsulated-options",<br>
>> >> >> "code": 43,<br>
>> >> >> "type": "empty",<br>
>> >> >> "encapsulate": "CALIXGC"<br>
>> >> >> }<br>
>> >> >> ],<br>
>> >> >> "option-data": [<br>
>> >> >> {<br>
>> >> >> "name":
"vendor-encapsulated-options",<br>
>> >> >> "code": 43<br>
>> >> >> },<br>
>> >> >> {<br>
>> >> >> "space": "CALIXGC",<br>
>> >> >> "name": "acs-url",<br>
>> >> >> "code": 1,<br>
>> >> >> "data": "<a
href="http://someurl" rel="noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">http://someurl</a>"<br>
>> >> >> }<br>
>> >> >> ]<br>
>> >> >><br>
>> >> >> See if you can send that to your
device or discover what actual data<br>
>> >> >> your device needs and we can see
how that might be configured?<br>
>> >> >><br>
>> >> >> Thank you,<br>
>> >> >><br>
>> >> >> Darren Ankney<br>
>> >> >><br>
>> >> >> On Tue, Jun 13, 2023 at 7:42 AM
Kraishak Mahtha <<a href="mailto:kraishak.edu@gmail.com"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">kraishak.edu@gmail.com</a>>
wrote:<br>
>> >> >> ><br>
>> >> >> > Hi Darren,<br>
>> >> >> ><br>
>> >> >> > Thank you for the suggestion
but I am still facing the same problem.<br>
>> >> >> ><br>
>> >> >> > {<br>
>> >> >> > "code":
"43",<br>
>> >> >> >
"csv-format": true,<br>
>> >> >> > "data":
"74657374",<br>
>> >> >> > },<br>
>> >> >> ><br>
>> >> >> > ---> With the above format
I am getting a few issues because of double quotes for the
code, and for CSV format, If I set that to true I am getting
an error as<br>
>> >> >> > 2023-06-13 06:23:40.309 ERROR
[kea-dhcp4.dhcp4/6561.139810011805888] DHCP4_PARSER_FAIL
failed to create or run parser for configuration element
subnet4: option data does not match option definition (space:
dhcp4, code: 43): attempt to write invalid option data field
type into the option buffer: 0 (kea-dhcp4.conf:60:27)<br>
>> >> >> > Error encountered: option data
does not match option definition (space: dhcp4, code: 43):
attempt to write invalid option data field type into the
option buffer: 0 (kea-dhcp4.conf:60:27)<br>
>> >> >> ><br>
>> >> >> > The final trial is as follows:<br>
>> >> >> > {<br>
>> >> >> > "code":
"43",<br>
>> >> >> >
"csv-format": false,<br>
>> >> >> > "data":
"74657374",<br>
>> >> >> > },<br>
>> >> >> ><br>
>> >> >> > This also gave me an empty for
option 43 in the ACK packet.<br>
>> >> >> ><br>
>> >> >> > This is the subnet of the ISC
config that I using for testing<br>
>> >> >> > subnet 3.4.0.0 netmask
255.255.0.0 {<br>
>> >> >> > pool {<br>
>> >> >> > range 3.4.0.2
3.4.0.5;<br>
>> >> >> > range 3.4.0.12
3.4.0.16;<br>
>> >> >> > range 3.4.0.41
3.4.0.56;<br>
>> >> >> > }<br>
>> >> >> >
default-lease-time 86400;<br>
>> >> >> > max-lease-time
86400;<br>
>> >> >> > option
domain-name "<a href="http://test.com" rel="noreferrer"
target="_blank" moz-do-not-send="true">test.com</a>";<br>
>> >> >> > option
domain-name-servers 6.6.6.6,7.7.7.7,8.8.8.4;<br>
>> >> >> > option routers
3.4.0.1;<br>
>> >> >> > option
subnet-mask 255.255.0.0;<br>
>> >> >> > option
vendor-encapsulated-options "test";<br>
>> >> >> > }<br>
>> >> >> ><br>
>> >> >> > Thanks<br>
>> >> >> > Kraishak<br>
>> >> >> ><br>
>> >> >> ><br>
>> >> >> ><br>
>> >> >> > On Tue, Jun 13, 2023 at
12:35 AM Darren Ankney <<a
href="mailto:darren.ankney@gmail.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">darren.ankney@gmail.com</a>>
wrote:<br>
>> >> >> >><br>
>> >> >> >> Hi Kraishak,<br>
>> >> >> >><br>
>> >> >> >> Have a look here:<br>
>> >> >> >> <a
href="https://kea.readthedocs.io/en/kea-2.2.0/arm/dhcp4-srv.html?highlight=%22vendor-encapsulated-options%22#dhcpv4-vendor-specific-options"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://kea.readthedocs.io/en/kea-2.2.0/arm/dhcp4-srv.html?highlight=%22vendor-encapsulated-options%22#dhcpv4-vendor-specific-options</a><br>
>> >> >> >><br>
>> >> >> >> You might need to setup
encapsulated sub-options and tell Kea to<br>
>> >> >> >> include the
"vendor-encapsulated-options-space" content in the options<br>
>> >> >> >> as a sub-option:<br>
>> >> >> >><br>
>> >> >> >> "option-data": [<br>
>> >> >> >> {<br>
>> >> >> >> "name": "REPLACE_ME",<br>
>> >> >> >> "space":
"vendor-encapsulated-options",<br>
>> >> >> >> "code": 1,<br>
>> >> >> >> "csv-format": false,<br>
>> >> >> >> "data": "74657374"<br>
>> >> >> >> },<br>
>> >> >> >> {<br>
>> >> >> >> "name":
"vendor-encapsulated-options"<br>
>> >> >> >> }<br>
>> >> >> >> ]<br>
>> >> >> >><br>
>> >> >> >> So, above, first the data
is added as a sub-option of option 43<br>
>> >> >> >> (option 43 typically
consists of one or more sub-options). Replace<br>
>> >> >> >> "REPLACE_ME" with the name
of the sub-option you are trying to send (I<br>
>> >> >> >> think you can omit name
entirely if there is none as that part isn't<br>
>> >> >> >> sent). Set the code to
the correct sub-option number. If this<br>
>> >> >> >> particular data should not
be a sub-option, then you might have to do<br>
>> >> >> >> something like this:<br>
>> >> >> >><br>
>> >> >> >> {<br>
>> >> >> >>
"code": "43",<br>
>> >> >> >>
"csv-format": true,<br>
>> >> >> >>
"data": "74657374",<br>
>> >> >> >> },<br>
>> >> >> >><br>
>> >> >> >> please note that if
"csv-format" is set to false, then Kea will be<br>
>> >> >> >> expecting "a hexadecimal
string." see:<br>
>> >> >> >> <a
href="https://kea.readthedocs.io/en/kea-2.2.0/arm/dhcp4-srv.html?highlight=%22csv-format%22#standard-dhcpv4-options"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://kea.readthedocs.io/en/kea-2.2.0/arm/dhcp4-srv.html?highlight=%22csv-format%22#standard-dhcpv4-options</a><br>
>> >> >> >><br>
>> >> >> >> Can you share the option
43 portion of the ISC DHCP configuration you<br>
>> >> >> >> are trying to convert if
you still have trouble?<br>
>> >> >> >><br>
>> >> >> >> Thank you,<br>
>> >> >> >><br>
>> >> >> >> Darren Ankney<br>
>> >> >> >><br>
>> >> >> >> On Mon, Jun 12, 2023 at
1:59 PM Kraishak Mahtha <<a
href="mailto:kraishak.edu@gmail.com" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">kraishak.edu@gmail.com</a>>
wrote:<br>
>> >> >> >> ><br>
>> >> >> >> > Hi,<br>
>> >> >> >> > I am trying to
convert my ISC config to kea-equivalent and testing the
changes as part of the testing, I am stuck at testing option
43 ,<br>
>> >> >> >> > Using the keama tool
I convert my ISC config to Kea equivalent config and tested
the leases but in the DHCP ACK packet I cannot see option 43
coming when I operate with Kea<br>
>> >> >> >> ><br>
>> >> >> >> > sample code config
for option 43 that I used in my testing subnet<br>
>> >> >> >> > {<br>
>> >> >> >> >
"data": "74657374",<br>
>> >> >> >> >
"name": "vendor-encapsulated-options",<br>
>> >> >> >> >
"csv-format": false<br>
>> >> >> >> > },<br>
>> >> >> >> ><br>
>> >> >> >> > But in log and
tcpdump I see the empty value for option 43<br>
>> >> >> >> ><br>
>> >> >> >> > Log:<br>
>> >> >> >> > ===<br>
>> >> >> >> > 2023-06-12
15:10:26.284 DEBUG [kea-dhcp4.packets/30590.140464453838592]
DHCP4_RESPONSE_DATA [hwtype=1 21:21:2f:00:00:01],
cid=[01:21:21:2f:00:00:01]x8259145: responding with packet
DHCPACK (type 5), packet details: local_address=<a
href="http://192.168.0.125:67" rel="noreferrer"
target="_blank" moz-do-not-send="true">192.168.0.125:67</a>,
remote_address=<a href="http://4.0.0.1:67" rel="noreferrer"
target="_blank" moz-do-not-send="true">4.0.0.1:67</a>,
msg_type=DHCPACK (5), =0x8259145,<br>
>> >> >> >> > options:<br>
>> >> >> >> > type=001, len=004:
4294901760 (uint32)<br>
>> >> >> >> > type=003, len=004:
4.0.0.1<br>
>> >> >> >> > type=006, len=012:
6.6.6.6 7.7.7.7 8.8.8.4<br>
>> >> >> >> > type=012, len=018:
"dhcp-client-000001" (string)<br>
>> >> >> >> > type=015, len=011:
"<a href="http://test.com" rel="noreferrer" target="_blank"
moz-do-not-send="true">test.com</a>" (string)<br>
>> >> >> >> > type=043, len=000:
----->Empty Value, and I cross-verified the tcpdump too.<br>
>> >> >> >> > type=051, len=004:
86400 (uint32)<br>
>> >> >> >> > type=053, len=001:
5 (uint8)<br>
>> >> >> >> > type=054, len=004:
192.168.0.125<br>
>> >> >> >> > type=061, len=007:
01:21:21:2f:00:00:01<br>
>> >> >> >> ><br>
>> >> >> >> > I have checked the
discover packet option 55 just to make sure if my packet is
asking for option 43 or not, and yes I can see option 43 in
the option 55 parameter value.<br>
>> >> >> >> ><br>
>> >> >> >> > I am not sure what is
wrong I am doing, Can someone who has familiar can guide me<br>
>> >> >> >> ><br>
>> >> >> >> > Thanks in Advance<br>
>> >> >> >> > Kraishak<br>
>> >> >> >> > --<br>
>> >> >> >> > ISC funds the
development of this software with paid support subscriptions.
Contact us at <a href="https://www.isc.org/contact/"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.isc.org/contact/</a>
for more information.<br>
>> >> >> >> ><br>
>> >> >> >> > To unsubscribe visit
<a href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
>> >> >> >> ><br>
>> >> >> >> > Kea-users mailing
list<br>
>> >> >> >> > <a
href="mailto:Kea-users@lists.isc.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">Kea-users@lists.isc.org</a><br>
>> >> >> >> > <a
href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
>> >> >> >> --<br>
>> >> >> >> ISC funds the development
of this software with paid support subscriptions. Contact us
at <a href="https://www.isc.org/contact/" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.isc.org/contact/</a>
for more information.<br>
>> >> >> >><br>
>> >> >> >> To unsubscribe visit <a
href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
>> >> >> >><br>
>> >> >> >> Kea-users mailing list<br>
>> >> >> >> <a
href="mailto:Kea-users@lists.isc.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">Kea-users@lists.isc.org</a><br>
>> >> >> >> <a
href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
>> >> >> --<br>
>> >> >> ISC funds the development of this
software with paid support subscriptions. Contact us at <a
href="https://www.isc.org/contact/" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.isc.org/contact/</a>
for more information.<br>
>> >> >><br>
>> >> >> To unsubscribe visit <a
href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
>> >> >><br>
>> >> >> Kea-users mailing list<br>
>> >> >> <a
href="mailto:Kea-users@lists.isc.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">Kea-users@lists.isc.org</a><br>
>> >> >> <a
href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
>> >> --<br>
>> >> ISC funds the development of this software
with paid support subscriptions. Contact us at <a
href="https://www.isc.org/contact/" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.isc.org/contact/</a>
for more information.<br>
>> >><br>
>> >> To unsubscribe visit <a
href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
>> >><br>
>> >> Kea-users mailing list<br>
>> >> <a href="mailto:Kea-users@lists.isc.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">Kea-users@lists.isc.org</a><br>
>> >> <a
href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
>> --<br>
>> ISC funds the development of this software with paid
support subscriptions. Contact us at <a
href="https://www.isc.org/contact/" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.isc.org/contact/</a>
for more information.<br>
>><br>
>> To unsubscribe visit <a
href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
>><br>
>> Kea-users mailing list<br>
>> <a href="mailto:Kea-users@lists.isc.org"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">Kea-users@lists.isc.org</a><br>
>> <a
href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
-- <br>
ISC funds the development of this software with paid support
subscriptions. Contact us at <a
href="https://www.isc.org/contact/" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.isc.org/contact/</a>
for more information.<br>
<br>
To unsubscribe visit <a
href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a>.<br>
<br>
Kea-users mailing list<br>
<a href="mailto:Kea-users@lists.isc.org" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">Kea-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/kea-users"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://lists.isc.org/mailman/listinfo/kea-users</a><br>
</blockquote>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
</body>
</html>