Opened 4 years ago

Closed 4 years ago

#4230 closed defect (fixed)

v4 host reservations by client identifier use keyword "duid" and are not documented in the Admin Guid

Reported by: tmark Owned by: marcin
Priority: medium Milestone: Kea1.0
Component: dhcp4 Version: git
Keywords: host reservations 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

In order to create a host reservation for v4 by client id, currently one must use the keyword "duid" as shown:

         {
             "duid": "30:30:30:31",
             "ip-address": "178.16.1.103"
         }

Use of the word "duid" is not intuitive for v4, and is not documented in the Admin guide. Tomek is also of the opinion that we need to address three forms:

[14:58:41] <tomek> we'll need to support 3: hwaddr, client-id and duid (which is not the same as client-id).
[14:59:05] <tomek> rfc4361 explains the difference.
[14:59:16] <tomek> DUID also has iaid in there.

Marcin had this to add:

15:16:04] <marcin@jabber.isc.org> we may need a ticket to differentiate between duid and client id in libdhcp++
[15:16:25] <marcin@jabber.isc.org> Currently ClientId derives from DUID which may not be a right thing to do, I don't know
[15:16:31] <tmark> I can add that comment to the ticket or you can
[15:16:57] <marcin@jabber.isc.org> The reason for using DUID in host reservation was to be able to correlate v4 and v6 clients
[15:17:01] <marcin@jabber.isc.org> so this is fine
[15:17:14] <marcin@jabber.isc.org> but apparently the v4 only deployments also want any type of client id
[15:17:23] <marcin@jabber.isc.org> like derived from hwaddress
[15:17:41] <tmark> do we want to document any of this for 1.0 final?
[15:17:56] <marcin@jabber.isc.org> We have to make this work to document it

This needs sorting out and then of course documentation.

Subtickets

Change History (7)

comment:1 Changed 4 years ago by marcin

  • Milestone changed from Kea-proposed to Kea1.0
  • Owner set to marcin
  • Status changed from new to accepted

On the Kea call on 16/12/2015 we discussed that for Kea 1.0 we simply want to make sure that documentation is clear that we don't support client-id based host reservations in v4. We also thought that we'd just reduce the scope of #4229 to check the documentation. On reflection I think that this ticket is more suitable to address possible deficiency in the documention. So I move it to 1.0. At the same time, the #4229 I will move to outstanding tasks.

comment:2 Changed 4 years ago by marcin

  • Owner changed from marcin to UnAssigned
  • Status changed from accepted to reviewing

Added a note to the user's guide that client id based reservations are not supported in the current version. I also updated the known issues list on kea.isc.org: http://kea.isc.org/wiki/KeaKnownIssues

comment:3 Changed 4 years ago by tmark

  • Owner changed from UnAssigned to tmark

comment:4 follow-up: Changed 4 years ago by tmark

  • Owner changed from tmark to marcin

One minor nit, the guide comment does not mention that the config parser will accept it, as the known issues text does. I think you should add that text to the guide.

comment:5 in reply to: ↑ 4 Changed 4 years ago by marcin

  • Owner changed from marcin to tmark

Replying to tmark:

One minor nit, the guide comment does not mention that the config parser will accept it, as the known issues text does. I think you should add that text to the guide.

I updated the guide according to your comment. Please review.

comment:6 Changed 4 years ago by tmark

  • Owner changed from tmark to marcin

Change is fine, please merge.

comment:7 Changed 4 years ago by marcin

  • Resolution set to fixed
  • Status changed from reviewing to closed

Merged with commit 9eb61a4468dbd56998d14004cf63576e22b374a4

Note: See TracTickets for help on using tickets.