lookup_hashed_option()

[Ted Lemon]

Oh, yes, that sounds right.   The problem is that for DHCPINFORM, the 
server doesn't look up the client - it just assigns information based 
on the network to which the client is connected.   You could add the 
client lookup code, but you'd have to duplicate most of the work that 
find_lease() does, which would be a pain.   Hm, actually you might be 
able to just call find_lease(), since find_lease() won't actually 
_allocate_ a lease.

There's also a lot to be said for merging the DHCPREQUEST and 
DHCPINFORM code paths - the reason I didn't do that originally was that 
I didn't want to pay the cost of the client lookup, but in retrospect I 
think that was an unnecessary optimization - I think most of the time 
the server spends handling client requests is writing to the database, 
which DHCPINFORM would never need to do.