<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
The section heading is misleading. In my case I was not upgrading to Kea 3, it was my starting point, so I saw no reason to read that. Also, the ARM docs do not mention a need to the Control Agent in either Kea or Stork.</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
That being said, having never configured the Control Agent, what is the proper configuration when hosting Kea and Stork on the same server (basic, getting started, get them talking, no SSL yet level)? Again, I'm brand new to Kea, Stork, this whole ecosystem.
The docs need to be written at that level. My main DHCP experience is Microsoft based so I'm not new to DHCP itself, but this is a very different platform in terms of setup/configuration.</div>
<div class="elementToProof" id="Signature">
<div style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof">
<br>
</div>
<p style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;" class="elementToProof">
<span style="font-family: Calibri, sans-serif; font-size: 11pt; color: rgb(36, 36, 36);"><br>
</span></p>
<p style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;" class="elementToProof">
<span style="font-family: "Calibri Light", sans-serif; font-size: 12pt; color: rgb(31, 73, 125);"><b>Corby Stephens, Fiber Network Administrator</b> |
</span><span style="font-family: "Calibri Light", sans-serif; font-size: 12pt; color: rgb(10, 28, 65);"><b>ACCESS</b> Anacortes Fiber Internet</span><span style="font-family: "Calibri Light", sans-serif; font-size: 12pt; color: rgb(31, 73, 125);"> | P.O. Box
547 | 904 Sixth Street | Anacortes, WA 98221</span></p>
<p style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;" class="elementToProof">
<span style="font-family: "Calibri Light", sans-serif; font-size: 12pt; color: rgb(31, 73, 125);">Office: 360.588.8362 | Cell: 360.873.3770 |
</span><span style="font-family: Aptos, sans-serif; font-size: 12pt; color: rgb(31, 73, 125);"><a style="color: rgb(31, 73, 125); margin: 0px;" data-linkindex="0" title="mailto:corbys@anacorteswa." href="mailto:corbys@anacorteswa.">corbys@anacorteswa.</a>gov</span><span style="font-family: "Calibri Light", sans-serif; font-size: 12pt; color: rgb(31, 73, 125);"> |
</span><span style="font-family: Aptos, sans-serif; font-size: 12pt; color: rgb(31, 73, 125);"><a style="color: rgb(31, 73, 125); margin: 0px;" data-auth="NotApplicable" data-linkindex="1" title="http://www.anacorteswa.gov/fiber" href="http://www.anacorteswa.gov/fiber">www.anacorteswa.gov/fiber</a></span><span style="font-family: "Calibri Light", sans-serif; font-size: 12pt; color: rgb(31, 73, 125);"> </span></p>
<p style="text-align: left; text-indent: 0px; background-color: rgb(255, 255, 255); margin: 0in;" class="elementToProof">
<span style="font-family: Aptos, sans-serif; font-size: 12pt; color: rgb(36, 36, 36);"><img style="width: 2.6041in; height: 2.6041in; max-width: 722px; min-width: auto; min-height: auto; margin: 0px;" height="249" width="249" id="x_Picture_x0020_1" data-outlook-trace="F:1|T:1" src="cid:3ca67e4e-54e4-444c-bb92-537914f39bfc"></span></p>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Stork-users <stork-users-bounces@lists.isc.org> on behalf of Kevin P. Fleming <lists.stork-users@kevin.km6g.us><br>
<b>Sent:</b> Tuesday, July 22, 2025 10:46 AM<br>
<b>To:</b> stork-users@lists.isc.org <stork-users@lists.isc.org><br>
<b>Subject:</b> Re: [stork-users] Fresh Stork 2.2.0 does not discover fresh Kea DHCP 3.0.0 instalation</font>
<div> </div>
</div>
<style type="text/css">
<!--
#x_qt p
{margin-top:0px;
margin-bottom:0px}
-->
</style>
<div>
<p align="center" style="text-align:center"><strong><span style="font-size:10.0pt; font-family:"Arial",sans-serif; color:white; background:#BA4642">***** This email is from outside the City of Anacortes network. Please use caution when clicking on links,
opening attachments, or replying. *****</span></strong></p>
<div>
<div>On Tue, Jul 22, 2025, at 12:55, Corby Stephens wrote:</div>
<blockquote type="cite" id="x_qt" style="">
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Where is it documented that Stork 2.2.0 and Kea 3.0.0 do not yet work together? What are the versions that do work together currently?
<a id="x_qt-LPlnk764017" href="https://kea.readthedocs.io/en/stable/arm/stork.html">
https://kea.readthedocs.io/en/stable/arm/stork.html</a> suggests that they do work together by the fact that the section exists in the 3.0.0 docs.</div>
</blockquote>
<div><br>
</div>
<div>I did not say that they "do not work together", only that the Control Agent is still required for Stork to be able to communicate with Kea 3.0.0 (where it is not required for Kea to communicate with itself).<br>
</div>
<div><br>
</div>
<div>This is documented here: <a href="https://kb.isc.org/docs/things-to-be-aware-of-when-upgrading-to-kea-300#connection-with-stork-agent">https://kb.isc.org/docs/things-to-be-aware-of-when-upgrading-to-kea-300#connection-with-stork-agent</a></div>
<div><br>
If there is other documentation which indicates that Stork can communicate with Kea without using the Control Agent, please point it out (by posting links) so that the ISC team can correct it.</div>
<div><br>
</div>
</div>
</div>
</body>
</html>