Page MenuHomeVyOS Platform
Create Task
Maniphest T6063

Kea DHCP: Expose match-client-id setting
Closed, ResolvedPublic
Actions

Description

By default the kea DHCP server does strict client-id matching.
This breaks network boot setups with static ip assignments (as the network boot agent and operating system will have different client ids).
The solution is to set the match-client-id setting to false. This already works when manually editing the config file and restarting the service.
See also https://kea.readthedocs.io/en/latest/arm/dhcp4-srv.html#using-client-identifier-and-hardware-address

Can this setting be exposed in the VyOS configuration?

Details

Difficulty level
Unknown (require assessment)
Version
1.5-rolling
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Config syntax change (migratable)
Issue type
Improvement (missing useful functionality)

Event Timeline

l.austenfeld triaged this task as Normal priority.Feb 24 2024, 6:55 PM
l.austenfeld created this task.
l.austenfeld created this object in space S1 VyOS Public.
l.austenfeld updated the task description. (Show Details)Feb 24 2024, 8:05 PM
sarthurdev claimed this task.Feb 24 2024, 10:44 PM
pasik added a subscriber: pasik.Feb 24 2024, 10:55 PM
sarthurdev changed the task status from Open to Needs testing.Feb 25 2024, 10:43 PM
sarthurdev moved this task from Need Triage to In Progress on the VyOS 1.5 Circinus board.

PR: https://github.com/vyos/vyos-1x/pull/3049

l.austenfeld added a comment.Feb 29 2024, 6:02 PM

I don't know what testing you might want to do, but for me it now works as expected.

I set the ignore-client-id option on the relevant subnet, verified that the kea config was modified, pxe booted some clients and verified that they ended up with the configured ip addresses (during both pxe boot and system boot).

sarthurdev closed this task as Resolved.Mar 6 2024, 7:06 PM
sarthurdev moved this task from In Progress to Finished on the VyOS 1.5 Circinus board.