dhcpcd-discuss

Re: DHCP renewal send as IP unicast but using Broadcast on Layer II

Roy Marples

Fri Dec 03 20:11:20 2010

On Fri, 2010-12-03 at 13:35 +0100, EXTERNAL Konold Martin (Firma,
RtP2/TEF72) wrote:
> Hi,
> 
> When debugging some issues with non working DHCP renewals I discovered that some version (more details later) of dhcpcd are correctly sending the renewal DHCP requests to the IP Address of the DHCP server (unicast).
> 
> But these renewal packets contain the Layer II broadcast address FF:FF:FF:FF:FF:FF while it is expected that they use the MAC address of the gateway instead.
> 
> Can you confirm that that sending a unicast DHCP renewal to the broadcast address would be a bug?

Here's the relevant section of RFC2131

4.3.6 Client messages

   Table 4 details the differences between messages from clients in
   various states.

   ---------------------------------------------------------------------
   |              |INIT-REBOOT  |SELECTING    |RENEWING     |REBINDING |
   ---------------------------------------------------------------------
   |broad/unicast |broadcast    |broadcast    |unicast      |broadcast |
   |server-ip     |MUST NOT     |MUST         |MUST NOT     |MUST NOT  |
   |requested-ip  |MUST         |MUST         |MUST NOT     |MUST NOT  |
   |ciaddr        |zero         |zero         |IP address   |IP address|
   ---------------------------------------------------------------------

So yes, any broadcast for renewal is a bug.
Could you state which versions suffer from this?

Thanks

Roy


Follow-Ups:
AW: DHCP renewal send as IP unicast but using Broadcast on Layer IIEXTERNAL Konold Martin (Firma, RtP2/TEF72)
References:
DHCP renewal send as IP unicast but using Broadcast on Layer IIEXTERNAL Konold Martin (Firma, RtP2/TEF72)
Archive administrator: postmaster@marples.name