lookup_hashed_option()

[Anshuman Singh Rawat]

> > What am I missing here? Is there some place in source where the hash 
> > functions are being changed between the calls to dhcpdiscover() and 
> > dhcpinform() ?
> 
> Probably the dhcpinform isn't matching some scope that the 
> DHCPDISCOVERs and DHCPREQUESTs match.

Well, the lookup function (lookup_option()) is called on the list of options the client has provided for both DHCPDISCOVER/DHCPREQUEST and DHCPINFORM.

Some differences I noticed between lookup's from dhcpdiscover()/dhcprequest() and dhcpinform. I am not sure how relevant they might be -

- I hadn't used DHCPREQUESTs before, but they also can fetch the option. Both DHCPDISCOVERs & DHCPINFORMs use the ack_lease() which does the lookup for the option (option name DHO_DHCP_PARAMETER_REQUEST_LIST).

- in ack_lease(), the execute_statements_in_scope() is called with the binding scope of the lease for DHCPDISCOVER & DHCPREQUEST. For DHCPINFORM, it's called with the binding scope of 'global_scope'.

Does this provide any more information than I gave earlier about the problem?

-Anshuman