[Bug 6614] New: Questionable implementation of RFC2132 - udhcpc

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6614

           Summary: Questionable implementation of RFC2132 - udhcpc
           Product: Busybox
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P5
         Component: Standard Compliance
        AssignedTo: unassigned at busybox.net
        ReportedBy: lcreg-busybox at convergence.cx
                CC: busybox-cvs at busybox.net
   Estimated Hours: 0.0


Hi there,

I produce an RFC2132 compliant (I believe) DHCP server, 

This server has a behavioural mechanism which, if enabled, omits option 54
(Server ID) in the DHCPOFFER message.

The reason for this, is that the server does not have an IP address, it
communicates solely
through Ethernet (so broadcast listen and unicast MAC response). 

udhcpc seemingly requires a server ID, if you don't provide one, it responds
with:

bb_error_msg("no server ID, ignoring packet");

and processing stops.

ISC DHCP client does not display this behaviour.

Nothing I appear to have read in RFC2132 indicates that this 'option' is
mandatory in all cases,  there is no RFC2119 language (MUST, SHOULD) which
indicates this, but it is clear in which scenarios it is needed (for example,
unicast IP response)

At present, no users with dhcpc can obtain a lease from my server, I suggest to
people that they should use ISC DHCPc instead.

Regards,

David Freedman
Claranet

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.