Opened 3 years ago

Last modified 2 years ago

#3693 new defect

conflicts in DHCPv4 reservation malfunction.

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

Description

Test scenario:

  1. Server is configured with pool 192.168.50.5-192.168.50.10 and without any reserved addresses.
  1. Client X request address and leases with address A is saved.
  1. Server reconfiguration with same pool but with reservation for address A for client Y.
  1. Client X in renew state tries to renew address A. It's getting NAK (which is correct)
  1. Client Y requests address A and also gets NAK and that is incorrect!

In this scenario Client Y is able to get address A after leases expired. According to Kea leases politics in point 4 kea should save lease for address A with valid_lifetime = 0.
attached: file_set_no1.tar.gz

Same thing happens when sever is initially configured to give address A to client X then we change that address A should go to client Y.

Process of adding lease with valid_lifetime = 0 works only when server is reconfigured to give different IP address for the same client (no changes in MAC address):

  1. Server is configured with pool 192.168.50.5-192.168.50.10 and reservation of address A to client X.
  1. Client X request address and leases with address A is saved.
  1. Server reconfiguration with same pool but with reservation for address B for client X.
  1. Client X in renew state tries to renew address A. It's getting NAK (which is correct). New lease for address A with valid_lifetime = 0 is saved.
  1. Client X requests new address and gets reserved address B.

attached: file_set_no2.tar.gz

Subtickets

Attachments (2)

file_set_no1.tar.gz (3.1 KB) - added by wlodekwencel 3 years ago.
file_set_no2.tar.gz (3.0 KB) - added by wlodekwencel 3 years ago.

Download all attachments as: .zip

Change History (7)

Changed 3 years ago by wlodekwencel

Changed 3 years ago by wlodekwencel

comment:1 Changed 3 years ago by wlodekwencel

After call I checked scenario that Marcin talked about.

Test scenario:

  1. Server is configured with pool 192.168.50.5-192.168.50.10 and without any reserved addresses.
  1. Client X request address and leases with address A is saved.
  1. Server reconfiguration with same pool but with reservation for address A for client Y.
  1. Client X in renew state tries to renew address A. It's getting NAK (which is correct).
  1. (new step) Client X gets new lease for any other test. At this point Kea is saving lease for address A with valid_lifetime = 0.
  1. Client Y requests address A and gets it.

Question is - which way we prefer?

comment:2 Changed 3 years ago by hschempf

  • Milestone changed from Kea-proposed to Kea0.9.2

comment:3 Changed 3 years ago by marcin

  • Milestone changed from Kea0.9.2 to Kea1.1

comment:4 Changed 2 years ago by tomek

  • Milestone changed from Kea1.1 to DHCP Outstanding Tasks

comment:5 Changed 2 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

Note: See TracTickets for help on using tickets.