Diff client IDs -> multiple leases

[David W. Hankins]

On Mon, Mar 13, 2006 at 07:42:28PM +0200, Yedidyah Bar-David wrote:
> On Mon, Mar 13, 2006 at 09:14:48AM -0800, David W. Hankins wrote:
> > On Mon, Mar 13, 2006 at 11:04:21AM -0600, John Hascall wrote:
> > > So, would then:
> > >   	select-identity hardware;
> > > 
> > > do what the "patch to ignore client-identifier entirely" does?
> > > If so, that would be awesome.
> > 
> > Yes, but it would not be awesome.
> > 
> > Ignoring the client-id isn't the right way out of this.
> 
> Can you tell us what do you think _is_ the right way? If it's trying to
> make Intel change their PXE client (in my case), than I am not sure I
> agree.

I thought I already did that;

#	select-identity pick-first-value(
#				option client-identifier,
#				hardware);

Think carefully.  You have the problem where;

	lease x {
		hardware ethernet 00:01:02:03:04:05;
		uid "\001\000\001\002\003\004\005";
		...
	}

	lease y {
		hardware ethernet 00:01:02:03:04:05;
		...
	}

'hardware' as a configuration directive will give you:

	01:00:01:02:03:04:05

7 byte string, where 01 encodes the hardware type (ethernet).

'option client-identifier' as a configuration directive will give you:

	01:00:01:02:03:04:05

Because Windows does that.

Note that these are identical.

-- 
David W. Hankins		"If you don't do it right the first time,
Software Engineer			you'll just have to do it again."
Internet Systems Consortium, Inc.		-- Jack T. Hankins