[Kea-users] IPv6 Leasequery PD information

Brat Krik bratkrik332 at gmail.com
Wed Sep 21 21:34:51 UTC 2022


Good day, Members!

I have a question on which can't find exact response/information.

Does DHCP Kea respond to IPv6 Leasequery with information about PD prefix
from which belong the IPv6 address included in the request (may be there
are some links where I could read details about it)?

This question arises, as a result of testing isc-dhcp and observing that it
doesn't respond with the supposed information.

Below is detailed problem with isc-dhcp, but I would like to know *if this
issue is solved on Kea?*

When server got a Leasequery request for IPv6 address
2aXX:XXXX:f067:134f:a9c5:4b1a:7d87:438, I suppose it will lookup in lease
file and found that this address is part of a prefix delegation record and
will response with detailed information about the lease stored in
dhcpd6.leases regarding the iaprefix 2aXX:XXXX:f067:134f::/64.

Actually, I got a Leasequery reply with Status Code: NotConfigured.

The server is configured as follows:

default-lease-time 600;
max-lease-time 7200;
log-facility local7;

allow leasequery;

allow client-updates;
lease-id-format hex;
option client-class-information code  97 = string;
log-facility local7;

# The subnet where the server is attached and get DHCPv6 relayed messages
subnet6 2AXX:XXXX:F067:1236::/64 { }

# The subnet where the server is attached and get DHCPv6 Leasequery requests
subnet6 2AXX:XXXX:F067:144::/64 { }

# The subnet where reside CPE of subscrand get DHCPv6 Leasequery requests
subnet6 2AXX:XXXX:F067:144::/64 { }

# The subnet where reside CPE of subscribers
subnet6 2aXX:XXXX:f067:1300::/56 {
        # Prefix range for delegation to sub-routers
        prefix6 2AXX:XXX:F067:134A:: 2A02:a30:F067:134F:: /64;
}

Lease file contains following information:

root at Cati-DHCP:~ # tail -f /var/db/dhcpd6/dhcpd6.leases
# The format of this file is documented in the dhcpd.leases(5) manual page.
# This lease file was written by isc-dhcp-4.4.2-P1

# authoring-byte-order entry is generated, DO NOT DELETE
authoring-byte-order little-endian;

server-duid 00:01:00:01:2a:bd:83:a3:00:50:56:ae:39:4a;

ia-pd 01:00:00:00:00:03:00:01:e4:8d:8c:ac:02:68 {
  cltt 3 2022/09/21 08:11:37;
  iaprefix 2aXX:XXXX:f067:134f::/64 {
    binding state active;
    preferred-life 375;
    max-life 600;
    ends 3 2022/09/21 08:21:37;
  }
}

Packet capture of the LQ-Request and LQ-Reply (if it matters, the
Leasequery is done by a Cisco router):

DHCPv6
    Message type: Leasequery (14)
    Transaction ID: 0xd18eb7
    Leasequery Query
        Option: Leasequery Query (44)
        Length: 53
        Value: 0100000000000000000000000000000000000500182a020a…
        Query-type: by-address (1)
        Link address: ::
        IA Address
            Option: IA Address (5)
            Length: 24
            Value: 2aXXXXXXf067134fa9c54b1a7d8704380000000000000000
            IPv6 address: 2aXX:XXXX:f067:134f:a9c5:4b1a:7d87:438
            Preferred lifetime: 0
            Valid lifetime: 0
        Option Request
            Option: Option Request (6)
            Length: 4
            Value: 002f001a
            Requested Option code: Leasequery Relay Data (47)
            Requested Option code: IA Prefix (26)
    Client Identifier
        Option: Client Identifier (1)
        Length: 10
        Value: 00030001e02f6d868600
        DUID: 00030001e02f6d868600
        DUID Type: link-layer address (3)
        Hardware type: Ethernet (1)
        Link-layer address: e0:2f:6d:86:86:00

DHCPv6
    Message type: Leasequery-reply (15)
    Transaction ID: 0xd18eb7
    Client Identifier
        Option: Client Identifier (1)
        Length: 10
        Value: 00030001e02f6d868600
        DUID: 00030001e02f6d868600
        DUID Type: link-layer address (3)
        Hardware type: Ethernet (1)
        Link-layer address: e0:2f:6d:86:86:00
    Server Identifier
        Option: Server Identifier (2)
        Length: 14
        Value: 000100012abd7d33005056ae394a
        DUID: 000100012abd7d33005056ae394a
        DUID Type: link-layer address plus time (1)
        Hardware type: Ethernet (1)
        DUID Time: Sep 21, 2022 10:43:47.000000000 E. Europe Daylight Time
        Link-layer address: 00:50:56:ae:39:4a
    Status code
        Option: Status code (13)
        Length: 24
        Value: 000941646472657373206e6f7420696e206120706f6f6c2e
        Status Code: NotConfigured (9)
        Status Message: Address not in a pool.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20220922/b710a1a8/attachment.htm>


More information about the Kea-users mailing list