Re: Registered clients.

[Ted Lemon <[e-mail]>]

> (a) The ability for a client to roam between different networks and to
> be allocated a suitable dynamic IP address from a pool specific to that
> network.
> 
> (b) The ability to register clients by their hardware addresses and 
> to respond only to requests from registered clients,

The Internet Software Consortium DHCP server provides both (a) and
(b).   I am doing testing on the latest release right now, and should
be releasing it later today.

> (c) Multiple redundant servers to provide fault tolerance.

Major guilt trip - I owe the group a preliminary writeup of the
Server-to-Server protocol that we talked about at the most recent
IETF.  I haven't forgotten, but I'm still catching up.  Until the
Server-to-Server protocol is implemented, the solution you described
is probably best, although at least one vendor currently has a
proprietary server-to-server protocol operating through NIS+.

The Internet Software Consortium DHCP server is not public domain, but
is covered by a copyright derived from the Copyright appearing on
4.4BSD-Lite code - basically, you can do what you want with the code
as long as you preserve the copyright and acknowledge the ISC in your
documentation (use the actual copyright on the code for guidance,
though - this is just a summary, and I probably left something out).

You can find out more about the ISC DHCP server at
http://www.fugue.com/dhcp, and you can get a copy of the source at
ftp://www.fugue.com/pub/DHCPD-BETA-4.7.tar.gz.   I'd recommend waiting
for Beta 5 before trying to do anything with it, though, since (b)
wasn't implemented in Beta 4 Patchlevel 7.

			       _MelloN_