Opened 3 years ago

Last modified 7 months ago

#3777 new defect

WARN log when a client changes his Client Id

Reported by: nicolas.chaigneau Owned by:
Priority: low 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 (last modified by tomek)

If a client changes his Client Id after acquiring a lease, then tries to Renew, the following happens:

He is denied (NAK), which is OK (as described in the RFC, the client is not supposed to change his Client ID).

But we get a WARN message in the logs, for example:

2015-03-25 18:56:23.983 DEBUG [kea-dhcp4.dhcpsrv/25912] DHCPSRV_MEMFILE_GET_SUBID_HWADDR obtaining IPv4 lease for subnet ID 1001 and hardware address hwtype=1 4e:43:48:00:00:01
2015-03-25 18:56:23.983 WARN [kea-dhcp4.dhcpsrv/25912] DHCPSRV_ADDRESS4_ALLOC_FAIL failed to allocate an IPv4 address after 100

attempt(s)

2015-03-25 18:56:23.983 DEBUG [kea-dhcp4.dhcp4/25912] DHCP4_LEASE_ALLOC_FAIL failed to grant a lease for client-id 43:31, hwaddr

hwtype=1 4e:43:48:00:00:01, client sent ciaddr 0.0.0.0, requested-ip- address 10.156.0.2

A client doing something silly should not cause the server to log WARN messages.

Subtickets

Change History (9)

comment:1 Changed 3 years ago by hschempf

  • Milestone changed from Kea-proposed to DHCP Outstanding Tasks

comment:2 Changed 2 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

comment:3 Changed 15 months ago by tomek

  • Description modified (diff)
  • Milestone changed from Outstanding Tasks to Kea-proposed

comment:4 Changed 14 months ago by tomek

  • Milestone changed from Kea-proposed to Kea1.2

Moving to 1.2 milestone as discussed on 2016-09-08 call.

comment:5 Changed 14 months ago by tomek

  • Component changed from Unclassified to dhcp4

comment:6 Changed 9 months ago by fdupont

The problem is more the 100 attempts than the WARN message...
I propose first to try to reproduce the case.

comment:7 Changed 9 months ago by nicolas.chaigneau

Just tested this with Kea 1.1.0, the issue does not appear anymore.

  • With "match-client-id": false, client renewing with a new Client Id gets an Ack.
  • With "match-client-id": true, client renewing with a new Client Id gets a NAK (which is expected).

And there are no WARN log anymore.

So you can close this :)

comment:8 Changed 8 months ago by tomek

  • Milestone changed from Kea1.2 to Kea1.2-final

Code freeze for 1.2-beta. Moving all remaining open tickets to 1.2-final.

comment:9 Changed 7 months ago by tomek

  • Milestone changed from Kea1.2-final to Outstanding Tasks

As discussed on 2017-04-13 call, moving to outstanding.

Note: See TracTickets for help on using tickets.