[kea-dev] Issue with INIT-REBOOT use case - Kea returns a NACK

Chaigneau, Nicolas nicolas.chaigneau at capgemini.com
Mon Dec 22 15:27:18 UTC 2014


In addition, the returned NACK is malformed (according to Wireshark).

It contains option 50 (Requested IP address) with a length of 1, containing "1F". (0x 32 01 1F)



> I believe there may be an issue with the following use case (Kea version 0.9) :
> 
> A client in "INIT-REBOOT" state sends a DHCP Request to Kea.
> The message contains option 50 (Requested IP address), and no option 54 (DHCP Server Identifier). 
> The requested IP address belongs to the subnet identified by the giaddr, so this is a valid INIT-REBOOT case.
> 
> Kea has no knowledge of this client.
> 
> 
> - Observed  behavior:
> 
> Kea returns a NACK.
> In the log we have the following DEBUG message:
> 2014-11-06 16:25:05.828 DEBUG [kea-dhcp4.dhcp4/26599] DHCP4_INVALID_ADDRESS_INIT_REBOOT invalid address 10.157.49.213 requested by INIT-REBOOT client (id: 01:00:21:6a:71:60:c4, hwaddr: hwtype=1 00:21:6a:71:60:c4)
> 
> 
> - Expected behavior (according to RFC):
> 
> "If the DHCP server has no record of this client, then it MUST remain silent"
> 
> (see RFC 2131, chapter 4.3.2 DHCPREQUEST message, section "DHCPREQUEST generated during INIT-REBOOT state")
> 
> 
> 
> If you agree this is abnormal, I'll open a ticket.
>
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.



More information about the kea-dev mailing list