<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">I would recommend doing this without “shared-networks” unless they are absolutely necessary in your<div>environment for some reason that isn’t clear to me from your prior writings.</div><div><br></div><div>I’m doing DHCPv6 relay without shared subnet declarations and the information provided by my relay</div><div>(Juniper MX240) allows KEA to determine the correct subnet without issue.</div><div><br></div><div>In my case, I didn’t have to do anything special. I declared the KEA interface as follows:</div><div><p style="margin: 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; font-size: 23px; line-height: normal; font-family: "Andale Mono"; font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; font-variant-emoji: normal; font-feature-settings: normal; font-optical-sizing: auto; font-variation-settings: normal; color: rgb(47, 255, 18); background-color: rgba(0, 0, 0, 0.9);"><span style="font-variant-ligatures: no-common-ligatures"> "interfaces-config" : {</span></p>
<p style="margin: 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; font-size: 23px; line-height: normal; font-family: "Andale Mono"; font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; font-variant-emoji: normal; font-feature-settings: normal; font-optical-sizing: auto; font-variation-settings: normal; color: rgb(47, 255, 18); background-color: rgba(0, 0, 0, 0.9);"><span style="font-variant-ligatures: no-common-ligatures"> "interfaces" : [ “eth0/xxxx:xxxx:xxxx:1::200:231" ],</span></p>
<p style="margin: 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; font-size: 23px; line-height: normal; font-family: "Andale Mono"; font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; font-variant-emoji: normal; font-feature-settings: normal; font-optical-sizing: auto; font-variation-settings: normal; color: rgb(47, 255, 18); background-color: rgba(0, 0, 0, 0.9);"><span style="font-variant-ligatures: no-common-ligatures"> "service-sockets-require-all": true</span></p>
<p style="margin: 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; font-size: 23px; line-height: normal; font-family: "Andale Mono"; font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; font-variant-emoji: normal; font-feature-settings: normal; font-optical-sizing: auto; font-variation-settings: normal; color: rgb(47, 255, 18); background-color: rgba(0, 0, 0, 0.9);"><span style="font-variant-ligatures: no-common-ligatures"> },</span></p></div><div><span style="font-variant-ligatures: no-common-ligatures"><br></span></div><div><span style="font-variant-ligatures: no-common-ligatures"><br></span></div><div><div>I then simply declared my subnet6 clauses like normal. The one that is locally attached is automatically</div><div>recognized as local because of the interface address being within the specified range. The ones that</div><div>are via relay are automatically recognized as such because the server receives relay requests and there</div><div>Is information in the relay request that identifies the subnet desired.</div><div><br></div><div>I believe shared-networks is intended for environments where you have multiple subnets on the</div><div>same physical link.</div><div><br></div><div>Owen</div><div><br></div><div><br><blockquote type="cite"><div>On Feb 15, 2025, at 16:15, kea-users-request@lists.isc.org wrote:</div><br class="Apple-interchange-newline"><div><div>Send Kea-users mailing list submissions to<br><span class="Apple-tab-span" style="white-space:pre"> </span>kea-users@lists.isc.org<br><br>To subscribe or unsubscribe via the World Wide Web, visit<br><span class="Apple-tab-span" style="white-space:pre"> </span>https://lists.isc.org/mailman/listinfo/kea-users<br>or, via email, send a message with subject or body 'help' to<br><span class="Apple-tab-span" style="white-space:pre"> </span>kea-users-request@lists.isc.org<br><br>You can reach the person managing the list at<br><span class="Apple-tab-span" style="white-space:pre"> </span>kea-users-owner@lists.isc.org<br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Kea-users digest..."<br><br><br>Today's Topics:<br><br> 1. Re: Not processing DHPCv6 Relayed requests (Geoff Sweet)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Sat, 15 Feb 2025 16:14:54 -0800<br>From: Geoff Sweet <thegorf+kea@gmail.com><br>To: "Kea user's list" <kea-users@lists.isc.org><br>Subject: Re: [Kea-users] Not processing DHPCv6 Relayed requests<br>Message-ID:<br><span class="Apple-tab-span" style="white-space:pre"> </span><CAPkbxkrxd=W-59jGnyb5Yx7bzJLm5HnsZ14vXTgSCeWLMOF2zA@mail.gmail.com><br>Content-Type: text/plain; charset="utf-8"<br><br>So I have now modified this shared-network configuration to look like the<br>following. However, it has not made any difference. It still only generates<br>"type=00013, len=00040: NoPrefixAvail(6) "Sorry, no prefixes could be<br>allocated."" in the logfiles. To be clear, the /56 at this site has been<br>divided up into different /64's for each zone on the firewall. The firewall<br>is doing the DHCPv6 relaying. I had added the different relay IP's because<br>that is how the link-address comes through in the tcpdump. So I guess I<br>misundertood that one. I've tried this configuration both with and without<br>the link-local address for the local interface of the firewall that the<br>relay comes from. Makes no difference:<br><br> "shared-networks": [<br> {<br> "name": "Site Subnets",<br> "interface": "ens18",<br> "relay":{<br> "ip-addresses": [<br> "2603:3023:62c:e160::1"<br> ]<br> },<br> "subnet6": [<br> {<br> "id":6100,<br> "subnet":"2603:3023:62c:e101::/64",<br> "pools":[ { "pool":"2603:3023:62c:e101::1000 -<br>2603:3023:62c:e101::ffff" } ]<br> },<br> {<br> "id":6110,<br> "subnet":"2603:3023:62c:e110::/64",<br> "pools":[ { "pool":"2603:3023:62c:e110::1000 -<br>2603:3023:62c:e110::ffff" } ]<br> },<br> {<br> "id":6130,<br> "subnet":"2603:3023:62c:e130::/64",<br> "pools":[ { "pool":"2603:3023:62c:e130::1000 -<br>2603:3023:62c:e130::ffff" } ]<br> },<br> {<br> "id":6150,<br> "subnet":"2603:3023:62c:e150::/64",<br> "pools":[ { "pool":"2603:3023:62c:e150::1000 -<br>2603:3023:62c:e150::ffff" } ]<br> },<br> {<br> "id":6160,<br> "subnet":"2603:3023:62c:e160::/64",<br> "pools":[ { "pool":"2603:3023:62c:e160::1000 -<br>2603:3023:62c:e160::ffff" } ]<br> }<br> ]<br> }<br> ],<br><br><br><br>On Sat, Feb 15, 2025 at 4:08?AM Darren Ankney <darren.ankney@gmail.com><br>wrote:<br><br><blockquote type="cite">Hi Geoff,<br><br>You can read more about any messages you encounter in the Kea logs by<br>accessing the messages manual here:<br>https://kea.readthedocs.io/en/kea-2.6.1/kea-messages.html and<br>searching for the phrase that is in all caps separated by underscores,<br>in this case: ALLOC_ENGINE_V6_ALLOC_FAIL_SHARED_NETWORK The double<br>negative sentence wouldn't be a double negative if it had found<br>subnets with "no available addresses".<br><br>What I notice about your configuration that will be causing Kea<br>problems is that you have different relay IP addresses for some<br>subnets in the same shared-network. That has no meaning. The shared<br>network subnets must all be assigned to the same relay agent or group<br>of relay agents. While this can be done at the subnet level, it makes<br>more sense to do it once per shared-network. See here:<br><br>https://kea.readthedocs.io/en/kea-2.6.1/arm/dhcp4-srv.html#local-and-relayed-traffic-in-shared-networks<br>where it says:<br><br>" it is a configuration error to specify different relay addresses for<br>the respective subnets in the shared network."<br><br>Thank you,<br>Darren Ankney<br><br>On Sat, Feb 15, 2025 at 3:10?AM Geoff Sweet <thegorf+kea@gmail.com> wrote:<br><blockquote type="cite"><br>Thanks kindly there Darren, that did make a difference and solved part<br></blockquote>of the problem. I also made a change in the configuration. Check this out,<br>the config is shared-network now and the debug logs clearly show that it<br>now receives the request and looks for a subnet. What is strange here is<br>this log entry:<br><blockquote type="cite"><br>2025-02-14 23:49:15.069 WARN<br></blockquote>[kea-dhcp6.alloc-engine/9752.140223914522304]<br>ALLOC_ENGINE_V6_ALLOC_FAIL_SHARED_NETWORK<br>duid=[00:03:00:01:16:fb:97:88:25:a7], [no hwaddr info], tid=0xe52907:<br>failed to allocate a lease in the shared network Site Subnets: 0 subnets<br>have no available leases, 15 subnets have no matching pools<br><blockquote type="cite"><br>I don't know where it's getting that 15 subnets from. Or why it thinks<br></blockquote>there are 0 subnets with available leases. By the way, that sentence is an<br>odd double negative.<br><blockquote type="cite"><br>Anyway, I'm just throwing stuff against the wall in this config now.<br></blockquote>Current subnet configuration and block of logs below:<br><blockquote type="cite"><br>####<br>Config<br>####<br> "shared-networks": [<br> {<br> "name": "Site Subnets",<br> "subnet6": [<br> {<br> "id":6100,<br> "subnet":"2603:3023:62c:e101::/64",<br> "pools":[ { "pool":"2603:3023:62c:e101::1000 -<br></blockquote>2603:3023:62c:e101::ffff" } ],<br><blockquote type="cite"> "relay":{<br> "ip-addresses":[ "2603:3023:62c:e101::1" ]<br> },<br> "interface": "ens18"<br> },<br> {<br> "id":6110,<br> "subnet":"2603:3023:62c:e110::/64",<br> "pools":[ { "pool":"2603:3023:62c:e110::1000 -<br></blockquote>2603:3023:62c:e110::ffff" } ],<br><blockquote type="cite"> "relay":{<br> "ip-addresses":[ "2603:3023:62c:e110::1" ]<br> },<br> "interface": "ens18"<br> },<br> {<br> "id":6130,<br> "subnet":"2603:3023:62c:e130::/64",<br> "pools":[ { "pool":"2603:3023:62c:e130::1000 -<br></blockquote>2603:3023:62c:e130::ffff" } ],<br><blockquote type="cite"> "relay":{<br> "ip-addresses":[ "2603:3023:62c:e130::1" ]<br> },<br> "interface": "ens18"<br> },<br> {<br> "id":6150,<br> "subnet":"2603:3023:62c:e150::/64",<br> "pools":[ { "pool":"2603:3023:62c:e150::1000 -<br></blockquote>2603:3023:62c:e150::ffff" } ],<br><blockquote type="cite"> "relay":{<br> "ip-addresses":[ "2603:3023:62c:e150::1" ]<br> },<br> "interface": "ens18"<br> },<br> {<br> "id":6160,<br> "subnet":"2603:3023:62c:e160::/64",<br> "pools":[ { "pool":"2603:3023:62c:e160::1000 -<br></blockquote>2603:3023:62c:e160::ffff" } ],<br><blockquote type="cite"> "interface": "ens18"<br> }<br> ]<br> }<br> ],<br><br>####<br>Logfile of a request:<br>####<br><br>msg_type=SOLICIT (1), trans_id=0xe52907,<br>options:<br> type=00001, len=00010: 00:03:00:01:16:fb:97:88:25:a7<br> type=00006, len=00002: 82(uint16)<br> type=00008, len=00002: 23347 (uint16)<br> type=00014, len=00000:<br> type=00025(IA_PD), len=00041: iaid=0, t1=0, t2=0,<br>options:<br> type=00026(IAPREFIX), len=00025: prefix=::/64, preferred-lft=0,<br></blockquote>valid-lft=0<br><blockquote type="cite">1 relay(s):<br>relay[0]: msg-type=12(RELAY_FORWARD), hop-count=0,<br>link-address=2603:3023:62c:e101::1,<br></blockquote>peer-address=fe80::14fb:97ff:fe88:25a7, 1 option(s)<br><blockquote type="cite">type=00018, len=00004: 04:00:00:00<br><br>2025-02-14 23:49:15.068 DEBUG [kea-dhcp6.packets/9752.140223914522304]<br></blockquote>DHCP6_SUBNET_SELECTED duid=[00:03:00:01:16:fb:97:88:25:a7], [no hwaddr<br>info], tid=0xe52907: the subnet with ID 6100 was selected for client<br>assignments<br><blockquote type="cite">2025-02-14 23:49:15.068 DEBUG [kea-dhcp6.packets/9752.140223914522304]<br></blockquote>DHCP6_SUBNET_DATA duid=[00:03:00:01:16:fb:97:88:25:a7], [no hwaddr info],<br>tid=0xe52907: the selected subnet details: 2603:3023:62c:e101::/64<br><blockquote type="cite">2025-02-14 23:49:15.068 DEBUG [kea-dhcp6.hosts/9752.140223914522304]<br></blockquote>HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using<br>identifier: hwaddr=16FB978825A7<br><blockquote type="cite">2025-02-14 23:49:15.068 DEBUG [kea-dhcp6.hosts/9752.140223914522304]<br></blockquote>HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier hwaddr=16FB978825A7,<br>found 0 host(s)<br><blockquote type="cite">2025-02-14 23:49:15.068 DEBUG [kea-dhcp6.hosts/9752.140223914522304]<br></blockquote>HOSTS_CFG_GET_ALL_IDENTIFIER get all hosts with reservations using<br>identifier: duid=0003000116FB978825A7<br><blockquote type="cite">2025-02-14 23:49:15.068 DEBUG [kea-dhcp6.hosts/9752.140223914522304]<br></blockquote>HOSTS_CFG_GET_ALL_IDENTIFIER_COUNT using identifier<br>duid=0003000116FB978825A7, found 0 host(s)<br><blockquote type="cite">2025-02-14 23:49:15.068 DEBUG [kea-dhcp6.dhcp6/9752.140223914522304]<br></blockquote>DHCP6_CLASS_ASSIGNED duid=[00:03:00:01:16:fb:97:88:25:a7], [no hwaddr<br>info], tid=0xe52907: client packet has been assigned to the following<br>class: UNKNOWN<br><blockquote type="cite">2025-02-14 23:49:15.068 DEBUG [kea-dhcp6.dhcp6/9752.140223914522304]<br></blockquote>DHCP6_CLASSES_ASSIGNED_AFTER_SUBNET_SELECTION<br>duid=[00:03:00:01:16:fb:97:88:25:a7], [no hwaddr info], tid=0xe52907:<br>client packet has been assigned to the following classes: ALL, UNKNOWN<br><blockquote type="cite">2025-02-14 23:49:15.069 DEBUG<br></blockquote>[kea-dhcp6.alloc-engine/9752.140223914522304]<br>ALLOC_ENGINE_V6_ALLOC_UNRESERVED no static reservations available - trying<br>to dynamically allocate leases for client<br>duid=[00:03:00:01:16:fb:97:88:25:a7], [no hwaddr info], tid=0xe52907<br><blockquote type="cite">2025-02-14 23:49:15.069 WARN<br></blockquote>[kea-dhcp6.alloc-engine/9752.140223914522304]<br>ALLOC_ENGINE_V6_ALLOC_FAIL_SHARED_NETWORK<br>duid=[00:03:00:01:16:fb:97:88:25:a7], [no hwaddr info], tid=0xe52907:<br>failed to allocate a lease in the shared network Site Subnets: 0 subnets<br>have no available leases, 15 subnets have no matching pools<br><blockquote type="cite">2025-02-14 23:49:15.069 WARN<br></blockquote>[kea-dhcp6.alloc-engine/9752.140223914522304]<br>ALLOC_ENGINE_V6_ALLOC_FAIL_NO_POOLS duid=[00:03:00:01:16:fb:97:88:25:a7],<br>[no hwaddr info], tid=0xe52907: no pools were available for the lease<br>allocation<br><blockquote type="cite">2025-02-14 23:49:15.069 WARN<br></blockquote>[kea-dhcp6.alloc-engine/9752.140223914522304]<br>ALLOC_ENGINE_V6_ALLOC_FAIL_CLASSES duid=[00:03:00:01:16:fb:97:88:25:a7],<br>[no hwaddr info], tid=0xe52907: Failed to allocate an IPv6 address for<br>client with classes: ALL, UNKNOWN<br><blockquote type="cite">2025-02-14 23:49:15.069 DEBUG [kea-dhcp6.options/9752.140223914522304]<br></blockquote>DHCP6_ADD_STATUS_CODE_FOR_IA duid=[00:03:00:01:16:fb:97:88:25:a7], [no<br>hwaddr info], tid=0xe52907: adding Status Code to IA with iaid=0:<br>NoPrefixAvail(6) "Sorry, no prefixes could be allocated."<br><blockquote type="cite">2025-02-14 23:49:15.070 DEBUG [kea-dhcp6.dhcp6/9752.140223914522304]<br></blockquote>DHCP6_CLASSES_ASSIGNED duid=[00:03:00:01:16:fb:97:88:25:a7], [no hwaddr<br>info], tid=0xe52907: client packet has been assigned on SOLICIT message to<br>the following classes: ALL, UNKNOWN<br><blockquote type="cite">2025-02-14 23:49:15.070 INFO [kea-dhcp6.packets/9752.140223914522304]<br></blockquote>DHCP6_PACKET_SEND duid=[00:03:00:01:16:fb:97:88:25:a7], [no hwaddr info],<br>tid=0xe52907: trying to send packet ADVERTISE (type 2) from<br>[2603:3023:62c:e160::11]:547 to [2603:3023:62c:e160::1]:547 on interface<br>ens18<br><blockquote type="cite">2025-02-14 23:49:15.070 DEBUG [kea-dhcp6.packets/9752.140223914522304]<br></blockquote>DHCP6_RESPONSE_DATA duid=[00:03:00:01:16:fb:97:88:25:a7], [no hwaddr info],<br>tid=0xe52907: responding with packet ADVERTISE (type 2), packet details:<br>local_address=[2603:3023:62c:e160::11]:547,<br>remote_address=[2603:3023:62c:e160::1]:547,<br><blockquote type="cite">msg_type=ADVERTISE (2), trans_id=0xe52907,<br>options:<br> type=00001, len=00010: 00:03:00:01:16:fb:97:88:25:a7<br> type=00002, len=00014: 00:01:00:01:2f:37:1b:26:bc:24:11:80:c9:7a<br> type=00025(IA_PD), len=00056: iaid=0, t1=0, t2=0,<br>options:<br> type=00013, len=00040: NoPrefixAvail(6) "Sorry, no prefixes could be<br></blockquote>allocated."<br><blockquote type="cite">1 relay(s):<br>relay[0]: msg-type=13(RELAY_REPLY), hop-count=0,<br>link-address=2603:3023:62c:e101::1,<br></blockquote>peer-address=fe80::14fb:97ff:fe88:25a7, 1 option(s)<br><blockquote type="cite">type=00018, len=00004: 04:00:00:00<br><br><br>On Thu, Feb 13, 2025 at 11:29?AM Darren Ankney <darren.ankney@gmail.com><br></blockquote>wrote:<br><blockquote type="cite"><blockquote type="cite"><br>Hi Geoff,<br><br>You might need to specify your IP address on which to listen in your<br>interfaces-config. You can check with the command: `ss -ulnp`. In<br>the output, look what address is listed with 547. It might be your<br>LLA for the interface. If it is that instead of your GLA for the<br>interface, then you need to specify the address. Something like this:<br><br> "interfaces-config": {<br> "interfaces": [<br> "ens18/2001:db8::12"<br> ]<br> },<br><br>See here:<br></blockquote></blockquote>https://kea.readthedocs.io/en/latest/arm/dhcp6-srv.html#interface-configuration<br><blockquote type="cite"><blockquote type="cite"><br>Thank you,<br>Darren Ankney<br><br>On Tue, Feb 11, 2025 at 1:28?AM Geoff Sweet <thegorf+kea@gmail.com><br></blockquote></blockquote>wrote:<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br>Greetings everyone,<br> I have a Kea 2.6 installation that for the most part is going<br></blockquote></blockquote></blockquote>great. However, I'm not able to figure out the config to make it work with<br>IPv6 relayed DHCPv6 requests. At the end of this email is my complete<br>config. So, my firewall is doing all DHCP relaying. I can see via tcpdump<br>that the request originates in the local subnet, is received by the<br>firewall relay agent, forwards it to the subnet with the Kea server on it,<br>and forwards it. On the Kea server itself I can see the request arrive for<br>instance:<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br>22:00:52.949059 IP6 (hlim 64, next-header UDP (17) payload length:<br></blockquote></blockquote></blockquote>133) 2603:3023:62c:e160::1.547 > 2603:3023:62c:e160::11.547: [udp sum ok]<br>dhcp6 relay-fwd (linkaddr=2603:3023:62c:e101::1<br>peeraddr=fe80::14fb:97ff:fe88:25a7 (interface-ID 04000000...)<br>(relay-message (dhcp6 solicit (xid=4d2037 (elapsed-time 0) (client-ID<br>hwaddr type 1 16fb978825a7) (IA_PD IAID:0 T1:0 T2:0 (IA_PD-prefix ::/64<br>pltime:0 vltime:0)) (option-request opt_82) (rapid-commit))))<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br>I'm not sure why the interface-ID is set the way it is. So opted to<br></blockquote></blockquote></blockquote>ignore it and instead focus on the linkaddr. But while the documentation<br>mentions it, for the life of me I can NOT find a single example of how to<br>configure it. So I'm kinda throwing things at the wall now. As you can see<br>below. Can anyone offer any insight into what I am doing wrong? Also,could<br>someone tell me if my loggers are configured correctly? They literally<br>produce exactly the same output no matter what I do with severity and<br>debuglevel. Part of the reason this is so frustrating to troubleshoot.<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br>Thanks everyone!<br><br>#######<br>kea-dhcpv6.conf<br>#######<br>{<br> "Dhcp6": {<br> "renew-timer": 21600,<br> "rebind-timer": 43200,<br> "valid-lifetime": 86400,<br> "interfaces-config": {<br> "interfaces": [<br> "ens18"<br> ]<br> },<br> "lease-database": {<br> "type": "memfile",<br> "persist": true,<br> "name": "/var/lib/kea/dhcp6.leases"<br> },<br> "option-data": [<br> {<br> "name": "dns-servers",<br> "data": "2603:3023:62c:e101::10, 2603:3023:62c:e101::12"<br> },<br> {<br> "name": "domain-search",<br> "data": "iotlab.loc"<br> }<br> ],<br> "dhcp-ddns": {<br> "enable-updates": true,<br> "server-ip": "127.0.0.1",<br> "server-port": 53001<br> },<br> "ddns-override-client-update": true,<br> "ddns-override-no-update": true,<br> "ddns-qualifying-suffix": "iotlab.loc",<br> "ddns-update-on-renew": true,<br> "subnet6": [<br># Home Subnet<br> {<br> "subnet": "2603:3023:62c:e101::/64",<br>"id": 6100,<br> "pools": [<br> {<br> "pool": "2603:3023:62c:e101::1000 -<br></blockquote></blockquote></blockquote>2603:3023:62c:e101::ffff"<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> }<br> ],<br> "relay": {<br> "linkaddr": [ "2603:3023:62c:e101::1" ]<br> }<br> },<br># DMZ Subnet<br> {<br> "subnet": "2603:3023:62c:e110::/64",<br> "id": 6110,<br> "pools": [<br> {<br> "pool": "2603:3023:62c:e110::1000 -<br></blockquote></blockquote></blockquote>2603:3023:62c:e110::ffff"<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> }<br> ],<br> "relay": {<br> "ip-addresses": [ "2603:3023:62c:e110::1" ]<br> }<br> },<br># IoT Subnet<br> {<br> "subnet": "2603:3023:62c:e130::/64",<br> "id": 6130,<br> "pools": [<br> {<br> "pool": "2603:3023:62c:e130::1000 -<br></blockquote></blockquote></blockquote>2603:3023:62c:e130::ffff"<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> }<br> ],<br> "relay": {<br> "ip-addresses": [ "2603:3023:62c:e130::1" ]<br> }<br> },<br># Guest Subnet<br> {<br> "subnet": "2603:3023:62c:e150::/64",<br> "id": 6150,<br> "pools": [<br> {<br> "pool": "2603:3023:62c:e150::1000 -<br></blockquote></blockquote></blockquote>2603:3023:62c:e150::ffff"<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> }<br> ],<br> "relay": {<br> "ip-addresses": [ "2603:3023:62c:e150::1" ]<br> }<br> },<br> {<br> "subnet": "2603:3023:62c:e160::/64",<br> "id": 6160,<br> "interface": "ens18",<br> "pools": [<br> {<br> "pool": "2603:3023:62c:e160::1000 -<br></blockquote></blockquote></blockquote>2603:3023:62c:e160::ffff"<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"> }<br> ]<br> }<br> ],<br> "loggers": [<br> {<br> "name": "kea-dhcp6",<br> "severity": "DEBUG",<br> "debuglevel": "99",<br> "output_options": [<br> {<br> "output": "/var/log/kea/dhcp6.log",<br> "maxver": 10<br> }<br> ]<br> },<br> {<br> "name": "kea-dhcp6.dhcpsrv",<br> "severity": "DEBUG",<br> "debuglevel": "99",<br> "output_options": [<br> {<br> "output": "/var/log/kea/dhcp6-dhcpsrv.log",<br> "maxver": 10<br> }<br> ]<br> },<br> {<br> "name": "kea-dhcp6.leases",<br> "severity": "DEBUG",<br> "debuglevel": "99",<br> "output_options": [<br> {<br> "output": "/var/log/kea/dhcp6-leases.log",<br> "maxver": 10<br> }<br> ]<br> },<br> {<br> "name": "kea-netconf",<br> "severity": "DEBUG",<br> "debuglevel": "99",<br> "output_options": [<br> {<br> "output": "/var/log/kea/kea-netconf.log",<br> "maxver": 10<br> }<br> ]<br> }<br> ]<br> }<br>}<br><br><br><br>--<br>ISC funds the development of this software with paid support<br></blockquote></blockquote></blockquote>subscriptions. Contact us at https://www.isc.org/contact/ for more<br>information.<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br>To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users<br></blockquote></blockquote></blockquote>.<br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><br>Kea-users mailing list<br>Kea-users@lists.isc.org<br>https://lists.isc.org/mailman/listinfo/kea-users<br></blockquote>--<br>ISC funds the development of this software with paid support<br></blockquote></blockquote>subscriptions. Contact us at https://www.isc.org/contact/ for more<br>information.<br><blockquote type="cite"><blockquote type="cite"><br>To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.<br><br>Kea-users mailing list<br>Kea-users@lists.isc.org<br>https://lists.isc.org/mailman/listinfo/kea-users<br></blockquote><br>--<br>ISC funds the development of this software with paid support<br></blockquote>subscriptions. Contact us at https://www.isc.org/contact/ for more<br>information.<br><blockquote type="cite"><br>To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.<br><br>Kea-users mailing list<br>Kea-users@lists.isc.org<br>https://lists.isc.org/mailman/listinfo/kea-users<br></blockquote>--<br>ISC funds the development of this software with paid support<br>subscriptions. Contact us at https://www.isc.org/contact/ for more<br>information.<br><br>To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.<br><br>Kea-users mailing list<br>Kea-users@lists.isc.org<br>https://lists.isc.org/mailman/listinfo/kea-users<br><br></blockquote>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <https://lists.isc.org/pipermail/kea-users/attachments/20250215/06be2f14/attachment.htm><br><br>------------------------------<br><br>Subject: Digest Footer<br><br>_______________________________________________<br><br>ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.<br><br>Kea-users mailing list<br>Kea-users@lists.isc.org<br>https://lists.isc.org/mailman/listinfo/kea-users<br><br><br>------------------------------<br><br>End of Kea-users Digest, Vol 128, Issue 30<br>******************************************<br></div></div></blockquote></div><br></div></body></html>