Client misconfigured after DHCPINFORM/DHCPACK

[David W. Hankins]

On Tue, Jan 23, 2007 at 10:38:31AM -0600, Paine, Thomas Asa wrote:
>         I had recent issues after upgrading to release 3.0.5.  In versions sometime after 3.0.3 (checked 3.0.5 and the alpha release of 3.1.0a2) the service started doing the subnet lookup (for INFORMs) based on the gip (the relay's IP address) instead of cip (the client's ip address).  I don't now the reasoning behind this, but it causes clients
> to become misconfigured.  Why wouldn't you always use the client's IP addr to resolve dhcp options?  Is this a bug or by design?  If by design, what RFC stipulates using the relay's IP addr?

I don't think there's any RFC that describes this behaviour.  How
the server looks at its configuration to form a response has been
a matter left entirely up to implementors.

The inform sections of RFC2131 also don't even mention relays, it
only says that servers 'SHOULD' send replies to ciaddr (and then
reinforces this by assuming such throughout other sections).