Hi Jeff,
Regarding "circuit-id" based host reservations, the "circuit-id" is
used solely
to find the reservation.
Lease data will contain the identifier(s) used by the client, either the
hw-addr
or a DUID; therefore, renews and other unicast traffic will not be
affected by
missing RAI
Thanks for the clarification Peter. You're right, I failed to show that
I have configuration in each of the subnet definitions to match on the
client-class (and to restrict to the IP address of the expected relay)
"client-class": "VLAN_84",
"relay": { "ip-address": "10.11.12.13" },
Hi Jeff,
As you have discovered, classes based on option 82 values will only
match relayed traffic.
Therefore, all things being equal, Kea will not be able to select a
subnet for renewing clients.
Have you considered using host reservations with "circuit-id" as the
identifier?
Kind Regards
I had hoped that someone would post a better "solution" than what I've
been using.
My topology is a Cisco SG-series switch in Level 3 mode that is
supplying DHCP (v4) relay to a dedicated subnet with the Kea hosts.
With the caveat that I have not tested this approach for robustness
under
Hi Libor,
As you noted, this is because the server doesn't receive the option 82
data in subsequent renews. You may be able to force clients to always
use the relay-agent on your router or whatever is doing the relay.
Otherwise, there isn't much you can do. The Kea server can't classify
a
Hi, I am trying to start kea dhcp with client classification using option 82
through dhcp relay server.
When client tries to do renew of ip address, tries to prolongate his lease,
kea response with NAK.
The problem is that when client makes simple dhcp discover, the packet goes
broadcast
