LDAP...

[Markus Schabel]

Brian Masney wrote:
> On Thu, Nov 13, 2003 at 06:52:11PM +0100, Markus Schabel wrote:
> 
>>Hello!
>>
>>Some questions about DHCP and LDAP (again). I know the LDAP patch from
>>Brian Masney (http://home.ntelos.net/~masneyb/) to read the DHCP config
>>from an LDAP directory - which works here without problems for over one
>>year. What is keeping that patch from the official source-tree? Can
>>there be anything done to get it in?
> 
> ?

I'd like to see your patch in the official source, so there is no need
to patch always when a new version is released. Just configure it with
some kind like --with-ldap-configuration and recompile it, istead of
first patching it, then rewriting the debian/* files to generate only
the default debian packages instead of your dhcp3-ldap-ntelos debs or
probably have some dhcp3-server-ldap packages in the debian source?

>>I'd like to store the active leases in my LDAP directory - which at the
>>moment works fine with a perl script which parses the lease-file, but I
>>guess the better solution would be to implement this in the server? As
>>far as I can see all the functions regarding the lease-file are in db.c?
>>So I would have to replace the db.c with a new db_ldap.c which stores
>>all lease data in LDAP? Would you like to see this in the offical source
>>and configurable at compile time?
> 
> 
> When I wrote my LDAP patch, I looked at implementing this part of the LDAP
> schema. If you have a DHCP server with any kind of load on it, the LDAP
> server probably would not be able to keep up. Reads happen very fast, writes
> take much longer to complete. I don't have too much time to spare at the
> moment, but I could maybe try help you implement this if you want.

What I'd like to have in my LDAP is the following:

ou=dhcpd
|-- ou=Config     => DHCP configuration
|-- ou=Computers  => dhcpHost entries, (should be extensible via
|                    external applications to e.g. add sambaAccount
|                    information for Domain member computers) each of
|                    this entries should have a dhcpLeaseDN attribute
|                    which points to the actual lease/IP or is empty
|-- ou=Leases     => the actual lease information (min. IP+state)
|-- ou=History    => maybe lease history, not really needed

all my dhcpHost entries would have an macAddress to identify them, and
may have some other attributes like sambaAccount information if the host
is member in a domain (which of course is no concern of dhcpd, but it
shouldn't be able to drop the entry because it is needed again).

Sure there could be performance problems, but without testing I wouldn't
find out ;-)

Any ideas if it is only db.c or are there other files needed? Surely
I'll take a deeper look in all of them, but I think somebody here has
a better overview on the code than I...

>>I'd like to use the ietf-draft from 2001 about "LDAP Schema for DHCP"
>>which has expired, but AFAIKT there is no newer version and it seems
>>well-tought for me. Any comments about this?
>>
>>http://www.ietf.org/proceedings/01aug/I-D/draft-ietf-dhc-ldap-schema-00.txt
> 
> 
> I include this draft document in my patch. It gets placed in the doc/
> directory.

best regards, Markus