Opened 2 years ago

Last modified 2 years ago

#4229 accepted defect

kea-dhcp4 does not reserve in-pool addresses reserved by client id

Reported by: tmark Owned by: marcin
Priority: medium Milestone: Outstanding Tasks
Component: dhcp4 Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

If an in-pool address is reserved by client id, rather than by hwaddr, the server will still sees the address as available to for allocation and will assign it to anyone.

In my testing, I created a reservation for client_id = "0001" for address 178.16.1.104, in a pool of 178.16.1.100 - 178.16.1.200. When submitting discovers with sequentially increasing MACs, the addresses handed out are 100, 101, 102, 103, 104, 105. 104 should have been skipped.

I have attached a snippet of the log output.

Subtickets

Attachments (2)

log.txt (3.9 KB) - added by tmark 2 years ago.
log output
4229.patch (453 bytes) - added by tomek 2 years ago.

Download all attachments as: .zip

Change History (5)

Changed 2 years ago by tmark

log output

Changed 2 years ago by tomek

comment:1 Changed 2 years ago by tomek

Added patch that remedies the intermediate problem. It's not a proper solution, more like a dirty hack. Proper solution will be developed soon.

comment:2 Changed 2 years ago by marcin

  • Owner set to marcin
  • Status changed from new to accepted

The reservation by client identifier was never fully implemented and this is why it is not documented in the user guide. I am planning on inspecting the code to see how much work it is to finish this up.

comment:3 Changed 2 years ago by marcin

  • Milestone changed from Kea1.0 to Outstanding Tasks

Moving to outstanding. See the note http://kea.isc.org/ticket/4230#comment:1 why I am doind it.

Note: See TracTickets for help on using tickets.