Hello,
unfortunately I have no means to influence client side. It always sends full
DUID, but the beginning changes ower power-on cycles. Mac source duid is OK for
me, since this part is stable, so those server side tweaks are not needed in my
situation.
I need only reservations not to be part
The following configuration works for my environment, using Mac address for
ipv6 reservations
- on the dhcp client side after installing the node, I force the use of the
DUID-LL and the setting dhcp6.method = auto (if I remember correctly it is used
to set the routing correctly)
nmcli co
Nope, solution is to not place reservations into leases. The reservations in
leases create more problems then it solves. There are many change requests for
it from multiple people. This was just step sidewards.
Marek
Sent with Proton Mail secure email.
On Friday, November 29th, 2024 at 11:
Véronique is right: the solution is to use flex-id with replace-client-id
set to true.
Regards
Francis Dupont
--
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.
Greško
> via Kea-users
> Sent: Friday, November 29, 2024 10:45 AM
> To: Marcin Siodelski
> Cc: Marek Greško ; Kea user's list
>
> Subject: Re: [Kea-users] DHCPv6 DUID-LL matching
>
> Hello,
>
> I found out the problem source. It seems it is not achievable
Yes, it is probably not possible for the device to store the DUID value so it
generates it on every power-on. Only the MAC part of the DUID is constant. If
kea does not put reservation into lease, all the problems would be gone.
Marek
Sent with Proton Mail secure email.
On Friday, November
If the client keeps changing it DUID the Kea server has no way to tell
whether it is the same client that gets back or a different client.
That's why it would offer a different IP address assuming it is a
different client.
Having said that, the DUID is a client unique identifier and SHOULD be
Hi Marek,
The solution is to use flex-id.
Cheers,
Veronique
From: Kea-users on behalf of Marek Greško via
Kea-users
Sent: Friday, November 29, 2024 10:45 AM
To: Marcin Siodelski
Cc: Marek Greško ; Kea user's list
Subject: Re: [Kea-users] DHCPv6 DU
Hello,
I found out the problem source. It seems it is not achievable what I am trying
to do. It works for the first time. The kea matches the DUID-LL and creates
lease with full DUID. Then when the DUID changes, when the client tries to get
the ip address, kea finds out the reservation address
Does your client using a DUID-LL (highly recommended for clients without
a stable storage where they can save the DUID-LLT) or a DUID-LLT ?
In the second case if the by hardware address reservation matches it is
no the case for the DHCPv6 lease because the DUID-LLT changed.
There are two ways to ha
Marek,
Have you configured MAC sources correctly? Since you're using MAC
address as host identifier you should also instruct the server where to
get the client's MAC address from. This is achieved by listing MAC
sources as described here:
https://kea.readthedocs.io/en/kea-2.6.1/arm/dhcp6-srv
Hello,
I have working kea dhcpv6 setup. I am struggling with one problem. All my
devices get correct IPv6 addresses from reservations by matching DUID. But one
of the devices in the network have changing DUID, only the DUID-LL part is
constant, so I tried to match on DUID-LL. I am convinced it
12 matches
Mail list logo