Hi Francis,

your analysis seems to be correct. This is the KEA server log:

2024-11-25 15:32:13.867 DEBUG [kea-dhcp6.packets/8707.139678152782336]
DHCP6_SUBNET_SELECTION_FAILED
duid=[00:04:8a:24:56:28:14:87:48:b1:b0:7d:b7:3c:05:b6:fd:dd], tid=0x70f6ae:
failed to select subnet for the client
2024-11-25 15:32:13.867 DEBUG [kea-dhcp6.dhcp6/8707.139678152782336]
DHCP6_CLASS_ASSIGNED
duid=[00:04:8a:24:56:28:14:87:48:b1:b0:7d:b7:3c:05:b6:fd:dd], tid=0x70f6ae:
client packet has been assigned to the following class(es): UNKNOWN
2024-11-25 15:32:13.867 DEBUG [kea-dhcp6.options/8707.139678152782336]
DHCP6_ADD_STATUS_CODE_FOR_IA
duid=[00:04:8a:24:56:28:14:87:48:b1:b0:7d:b7:3c:05:b6:fd:dd], tid=0x70f6ae:
adding Status Code to IA with iaid=10171796: NoAddrsAvail(2) "Server could
not select subnet for this client"
2024-11-25 15:32:13.867 DEBUG [kea-dhcp6.packets/8707.139678152782336]
DHCP6_PACKET_SEND
duid=[00:04:8a:24:56:28:14:87:48:b1:b0:7d:b7:3c:05:b6:fd:dd], tid=0x70f6ae:
trying to send packet ADVERTISE (type 2) from [ff02::1:2]:547 to
[fe80::5054:ff:fe9b:3594]:546 on interface enp7s0
2024-11-25 15:32:13.867 DEBUG [kea-dhcp6.packets/8707.139678152782336]
DHCP6_RESPONSE_DATA responding with packet type 2 data is
localAddr=[ff02::1:2]:547 remoteAddr=[fe80::5054:ff:fe9b:3594]:546
msgtype=2(ADVERTISE), transid=0x70f6ae
type=00001, len=00018: 00:04:8a:24:56:28:14:87:48:b1:b0:7d:b7:3c:05:b6:fd:dd
type=00002, len=00014: 00:01:00:01:2e:66:39:5e:52:54:00:41:2f:9d
type=00003(IA_NA), len=00064: iaid=10171796, t1=0, t2=0,
options:
  type=00013, len=00048: NoAddrsAvail(2) "Server could not select subnet
for this client"
type=00023, len=00032: 2001:4860:4860::8888 2001:4860:4860::8844
No relays traversed.

The IPs of interface enp7s are:
enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
    link/ether 52:54:00:26:30:9f brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.3/24 brd 192.168.1.255 scope global enp7s0
       valid_lft forever preferred_lft forever
    inet 192.168.31.130/24 brd 192.168.31.255 scope global dynamic
noprefixroute enp7s0
       valid_lft 43072sec preferred_lft 37672sec
    inet6 fd00:0:0:1::3/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::85f4:b665:fd85:3d1e/64 scope link
       valid_lft forever preferred_lft forever
    inet6 fe80::5054:ff:fe26:309f/64 scope link
       valid_lft forever preferred_lft forever


-> It should be in the subnet, shouldn't it?

However, how do I fix it?
Thank you.
Best,
C.


Am So., 24. Nov. 2024 um 23:00 Uhr schrieb <kea-users-requ...@lists.isc.org
>:

> Send Kea-users mailing list submissions to
>         kea-users@lists.isc.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.isc.org/mailman/listinfo/kea-users
> or, via email, send a message with subject or body 'help' to
>         kea-users-requ...@lists.isc.org
>
> You can reach the person managing the list at
>         kea-users-ow...@lists.isc.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Kea-users digest..."
>
>
> Today's Topics:
>
>    1. Re: Stateful DHCPv6 with KEA and RADVD (Francis Dupont)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 24 Nov 2024 09:12:56 +0000
> From: Francis Dupont <fdup...@isc.org>
> To: Kea user's list <kea-users@lists.isc.org>, Christoph Markert
>         <magg...@gmail.com>
> Subject: Re: [Kea-users] Stateful DHCPv6 with KEA and RADVD
> Message-ID: <20241124091256.e7d4740...@bikeshed.isc.org>
> Content-Type: text/plain; charset="us-ascii"
>
> Please make the subnet to serve the interface (if directly atached, if you
> have a relay make the subnet to serve the relay). Without this the DHCPv6
> server can't localize (select a subnet in Kea terms) the client.
> BTW it is the same for ISC DHCP and if you have a working config for
> ISC DHCP you can try to translate it to Kea using Keama.
>
> Regards
>
> Francis Dupont <fdup...@isc.org>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
>
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
> Kea-users mailing list
> Kea-users@lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users
>
>
> ------------------------------
>
> End of Kea-users Digest, Vol 125, Issue 17
> ******************************************
>
-- 
ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.

To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users.

Kea-users mailing list
Kea-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/kea-users

Reply via email to