<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Hi, Joe. It depends on your access architecture. In the case of DOCSIS (cable) and PON, the access routers are behaving as relay agents and announce the route “automagically” after observing the completed
DHCPv6 transaction. Unsure of other technologies, but I have to think they are similar. I’ve personally used scripts like you’re describing (although not as a kea hook) in virtual PoC spaces and it worked well.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Dan<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Kea-users <kea-users-bounces@lists.isc.org> on behalf of Joe Botha <joe@swimgeek.com><br>
<b>Date: </b>Wednesday, November 30, 2022 at 7:01 AM<br>
<b>To: </b>kea-users@lists.isc.org <kea-users@lists.isc.org><br>
<b>Subject: </b>[EXTERNAL] Re: [Kea-users] ipv6 prefix delegation<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt">Hi<br>
<br>
I was wondering how you handle the extra route that needs<br>
to get added after the DHCPv6 PD-Pool lease event, the<br>
pd-pool route.<br>
<br>
Do you use a hook script?<br>
<br>
I'm looking into doing it with a hook script via Salt-minion.<br>
<br>
-- <br>
Swimmingly,<br>
Joe<br>
<br>
swimgeek.com/blog +27 82 562 6167 instagram.com/joe.swimgeek<br>
"...all progress depends on the unreasonable man.”<br>
<br>
<br>
>>> On 30 Nov 2022, at 02:32, Kevin P. Fleming <lists.kea-users@kevin.km6g.us> wrote:<br>
>>> <br>
>>> On Tue, Nov 29, 2022, at 19:28, Alan Batie wrote:<br>
>>>> I'm trying to setup a kea server to replace our isc-dhcp server and used <br>
>>>> the keama tool to generate a config file. In the ipv6 config, it <br>
>>>> silently commented out all the prefix delegation sections:<br>
>>>> <br>
>>>> "pd-pools": [<br>
>>>> // {<br>
>>>> // # Customer lan delegated prefixes<br>
>>>> // "prefix": "2607:f678:2000::",<br>
>>>> // "delegated-len": 60,<br>
>>>> // "prefix-highest": "2607:f678:2fff::"<br>
>>>> // }<br>
>>>> <br>
>>>> Will kea do prefix delegation?<br>
>>> <br>
>>> Yes, as documented in the Kea ARM (Administrator Reference Manual): <a href="https://urldefense.com/v3/__https:/kea.readthedocs.io/en/latest/arm/dhcp6-srv.html*subnet-and-prefix-delegation-pools__;Iw!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPg341eDHs$">
https://urldefense.com/v3/__https://kea.readthedocs.io/en/latest/arm/dhcp6-srv.html*subnet-and-prefix-delegation-pools__;Iw!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPg341eDHs$</a>
<br>
>>> <br>
>>> Given the nature of the project you are undertaking, it's likely best not to just assume that 'keama' will give you a working and supportable configuration... you'll need to understand how Kea operates and how it is configured as well.<br>
>>> -- <br>
>>> ISC funds the development of this software with paid support subscriptions. Contact us at
<a href="https://urldefense.com/v3/__https:/www.isc.org/contact/__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPgPKUqH3s$">
https://urldefense.com/v3/__https://www.isc.org/contact/__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPgPKUqH3s$</a> for more information.<br>
>>> <br>
>>> To unsubscribe visit <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPggUj304c$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPggUj304c$</a> .<br>
>>> <br>
>>> Kea-users mailing list<br>
>>> Kea-users@lists.isc.org<br>
>>> <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPggUj304c$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPggUj304c$</a>
<br>
>> <br>
> <br>
<br>
-- <br>
ISC funds the development of this software with paid support subscriptions. Contact us at
<a href="https://urldefense.com/v3/__https:/www.isc.org/contact/__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPgPKUqH3s$">
https://urldefense.com/v3/__https://www.isc.org/contact/__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPgPKUqH3s$</a> for more information.<br>
<br>
To unsubscribe visit <a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPggUj304c$">
https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPggUj304c$</a> .<br>
<br>
Kea-users mailing list<br>
Kea-users@lists.isc.org<br>
<a href="https://urldefense.com/v3/__https:/lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPggUj304c$">https://urldefense.com/v3/__https://lists.isc.org/mailman/listinfo/kea-users__;!!Hit2Ag!0NfH6jpJyB4wKrsdkRGh8U8fiAeAZGNl9IfeOGI272UUyO3h7-uojIvZWCAKEvKZGhPggUj304c$</a>
<o:p></o:p></span></p>
</div>
</div>
</body>
</html>