[kea-dev] Malformed packets returned by Kea

Chaigneau, Nicolas nicolas.chaigneau at capgemini.com
Tue Dec 23 08:44:58 UTC 2014


I've opened the ticket for yesterday's issue:

I've found other cases in which I have a "malformed packet" (as displayed by Wireshark).
This can happen in ACK or NACK replies.

It occurred on the following attributes:
Option 50 (Requested IP address): 0x 32 01 1f
Option 51 (IP Address lease time): 0x 33 01 20 (the packet actually contains two options 51, the first one is correct).
Option 49 (X Window System Display Manager): 0x 31 01 1e
Option 48, 45... etc.
(there may be more, I didn't check all packets yet, but possibly they are all related).

What is strange is these last three options (49, 48, 45) I don't know where they come from: they are not defined in my configuration.

If that can help investigation, I can provide pcap captures for these cases (and for the case described in ticket 3656).
(I've also saved Kea's full DEBUG log of these just in case, but it's big. If need be, I can probably extract the parts related to malformed requests).


> Please open a ticket and we will investigate. I think that there are cases where the DHCPv4 server may not determine the client's state correctly. I've been working on the host reservation implementation for
> DHCPv4 (#3564) which reworks the allocation strategy extensively. But I believe it may still have the issue you're pointing out.
> Please mention the DHCPNAK issue in the ticket.
> Marcin
> On 12/22/14 16:27, Chaigneau, Nicolas wrote:
> > 
> > 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)

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