Re: ldap

[Adam Williams <awilliam@xxxxxxxxxxxxx>]

>>1. Get LDAP installed and working (a lot easier with RH7).
>It's already working with RH 6.2, what advantage is there to 
>going to 7 now.  (not in general, just to work on this)

RH7 lets you specify you LDAP server and LDAP base at
installation, and a few other nicities.  Nothing radical,
but a very nice touch.  THis comment is more for the "worlds"
benefit than yours.

>>2. Install Samba 2.0.x ang get that working but use the
>>"interfaces = 192.168.3.6/24" parameter to tell that Samba
>>to ONLY listen to the primary ethernet interface.
>hosts allow = 192.168.0. 127.

"hosts allow" is different, it tells Samba to only 
accept connections from a given set of consumers (SMB speak
for clients).  "interfaces" tells it what interfaces to
listen on.

>#Configure Samba to use multiple interfaces
>#If you have multiple network interfaces then you must list them
>#here. See the man page for details.
>#  interfaces = 192.168.0.1/24
>>>samba-2.0.6-9
>>>samba-client-2.0.6-9
>>>samba-common-2.0.6-9
>is already working.  I thought the hosts allow would accomplish 
>the same thing but would be happy to uncomment the interfaces.

Nope, you need at least interfaces, but having "hosts allow" 
certainly is a good idea.

>>3. Get Samba HEAD 10-15-1999.  If you have trouble 
>>with the cvs server dropping you I can send you a tar ball.
>I have not been dropped yet.  It is just slower than molasses 
>in liquid nitrogen.  It has gotten one more file in the last 
>hour.  If you could send me the tarfile, that would be great.

I'll send it.  The CVS server is VERY slow.

>>4. Compile with "./configure --prefix={somewhere} --with-ldap"
>--prefix={where?} the location of the ldap header files?  or do 
>you want me to take '{somewhere}' literally?

"--prefix" tells the make file the directory into which samba will
be installed (ex. "/usr/local/samba").  I don't know where your 
current installation live,  head needs it's own path so as not
to interfere with 2.0.x.  If you used the LDAP RPM's you do not
need to worry about header file location, RPM took care of that
for you.  I install Samba in "/usr/local/samba" and Samba-HEAD in
"/usr/local/samba-head"  and just for clarity I rename 
"/usr/local/samba-head/bin/smbd" to "/usr/local/samba-head/smbd-head" 
and "/usr/local/samba-head/bin/nmbd" to "/usr/local/samba-head/bin
/nmbd-head".  That way I can tell them appart when I "ps ax".

>>5. Create a virtual interface "ifconfig eth0:1 192.168.3.7"
>cando
>>6. Install Samba head and use the "interfaces=192.168.3.7/24"
>cando
>make install to /usr/local/...  other than packages binary locale 
>I assume. This interface is not on my local subnet?  or would I 
>use 192.168.0.(not yet used) on my current local subnet.

Change the IP/Subnet mask.  Those are just examples from my net.

>>to make Samba head listen on the virtual interface.
>>7. Go about setting up Samba LDAP,  play with HEAD till you
>Not familiar with but can read.  Just read the docs of the Head 
>source I assume.

http://www.unav.es/cti/ldap-smb/ldap-smb-HEAD-howto.html

I've never read any of the docs from the HEAD branch, that 
might be a good idea.

>>get it working (Meanwhile 2.0.x still continues running
>>undistrubed).
>>8. Make the HEAD the domain master and the password server to
>>the 2.0.x server.  This way you get the advantage of LDAP
>>PDC and the stability of file/print services (from the 2.0.x
>>server).
>>This is much easier than it sounds.  HEAD 10-15-1999 is quite
>>stable, but I like to play it safe and keep 2.0.x around.
>>Samba 2.2.x I'm told has a tenative release date of Q1-2001
>>and will incorporate the LDAP code.
>That will be nice.

Very.