Send dhcp-users mailing list submissions to
dhcp-users@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
dhcp-users-requ...@lists.isc.org
You can reach the person managing the list at
dhcp-users-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."
Today's Topics:
1. ipv6 leasequery (Brat Krik)
----------------------------------------------------------------------
Message: 1
Date: Wed, 21 Sep 2022 11:30:59 +0300
From: Brat Krik <bratkrik...@gmail.com>
To: dhcp-users@lists.isc.org
Subject: ipv6 leasequery
Message-ID:
<CALjAH-9t-nWZj0hz1aukKRPNYU7dR=sR5i0hfyHCM0=b_ss...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Good day, Members!
I have a problem with getting lease information about IPv6 prefixes that
were delegated by ISC DHCP (version isc-dhcp-4.4.2-P1).
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.
Actualy, I got a Leasequery reply with Status Code: NotConfigured.
Is this a normal operation of isc-dhcp?
Does there exist a method how to configure the isc-dhcp to find that it has
information about the requested IPv6 address,
beacause it is part of a prefix that was delegated (delegated prefix
2aXX:XXXX:f067:134f::/64, IPv6 address in LQ
2aXX:XXXX:f067:134f:a9c5:4b1a:7d87:438)?
Please, help if there is something additional to be configured.
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 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@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/dhcp-users/attachments/20220921/20592ea4/attachment-0001.htm>
------------------------------
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.
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users
------------------------------
End of dhcp-users Digest, Vol 167, Issue 6
******************************************
