"LDAP patch" and bootp

[John Morris]

Hi Alan,

Putting this back on the list....

On 10/17/2013 01:28 AM, Alan Clegg wrote:
> 
> On Oct 17, 2013, at 12:24 AM, John Morris <john at zultron.com> wrote:
> 
>> Do the list members know why, and whether that can be fixed?  The dhcpd
>> documentation indicates that bootp is handled in a different way from
>> dhcp.  Is it an architectural limitation?  Or is it just that nobody's
>> wanted it enough to implement it?
> 
> Are there modern systems that still boot using bootp?
> 
> I know that legacy systems might, but I've not seen a system needing bootp in well over 5 years...

PXE boot systems are standard in large environments today as part of
'server provisioning', mentioned in the original post.  This example
contains typical parameters for a PXE boot configuration:

allow bootp;
allow booting;

subnet 10.0.0.0 netmask 255.255.255.0 {
  range dynamic-bootp 10.0.0.10 10.0.0.254;
  next-server                     10.0.0.20;
  filename                        "pxelinux.0";

  host foo {
    hardware ethernet ee:ee:ee:ff:ff:ff;
    fixed-address 10.0.0.42;
  }
}

Addressing your question, perhaps I'm mistaken that this is a bootp
configuration, despite the parameter names?

At any rate, the question is about translating the above file into an
LDAP-based configuration.  IIRC from my earlier investigation, six of
the above lines cannot be expressed by the LDAP patch (including the
'range' line).  I'll be happy to be proven wrong!

	John