Re: NT 3.51 dhcp client and server ip address

[Ted Lemon <[e-mail]>]

> How much of a problem is this really?  The server implementation I was
> responsible for had to handle multiple interfaces, and it did so just
> fine.  The server kept a list of all of its own IP addresses.  When a
> DHCPREQUEST comes in with a Server Identifier option specified, we ran
> down the list and compared it - if it was on the list, it's ours; if
> not, it isn't.  Unless there's a DHCP server with hundreds of interfaces
> out there, running down the list shouldn't take all that long...

Actually, now that I think about it, the reason I didn't want to do
this is that I didn't want dhcpd to fail to recognize a lease as its
own if some of the server's interface addresses changed.   By
requiring the user to pick one server identifier address, and
documenting the importance of choosing a reasonably permanent address,
rather than assigning these addresses automatically, I felt I was
minimizing the chances of something like this happening.

Nonetheless, I think this is a moot point for reasons we have already
discussed.  Sigh.

			       _MelloN_