host declaration restrction (Re: ISC DHCP 3.0.5b1 has been released!)
David W. Hankins
David_Hankins at isc.org
Fri Jul 28 18:43:35 UTC 2006
On Fri, Jul 28, 2006 at 02:08:26PM -0400, John Wobus wrote:
> Is this right? If so, it'll generate some reengineering work for us.
No, what you quoted is fine, and you don't have to redo anything.
These:
host george {
hardware ethernet 00:00:00:00:00:00;
hardware ethernet ff:ff:ff:ff:ff:ff;
deny booting;
}
host multibootmadness {
uid "mywindows uid";
uid "mylinux uid";
fixed-address foo;
}
Are both no longer legal (no parse warnings, no errors) syntax, as
they are currently.
It never worked the way people thought it did when they configured
it this way: a union of the two identifiers. What it really did is
to silently discard the previously defined identifier, so it was
equivalent to configuring these:
host george {
hardware ethernet ff:ff:ff:ff:ff:ff;
deny booting;
}
host multibootmadness {
uid "mylinux uid";
fixed-address foo;
}
Literally the host structure in memory had the new value stored
to it, over-writing the previous.
--
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
More information about the dhcp-users
mailing list