Hello Bruno -
On Thu, 18 May 2000, Bruno Rodrigues wrote:
> hi there
>
> I work for a portuguese ISP with a couple hundred thousand customers. we're
> currently working with Sun's RADIUS servers and we may be considering
> changing this in the near future.
>
> we're particulary worried about the performance issues but we're exchanging
> some ideias with people using platforms similar to ours. next comes the
> migration procedure. Sun's RADIUS stores the users and the NAS definitions
> on LDAP and we're interested in keeping it that way. Has anyone got into a
> situation like this we're living on? I would like to hear about the
> migration procedures and hickups you might have had.
>
You shouldn't have too much of a problem, as Radiator can access an LDAP
server directly when authenticating a user. The NAS definitions however are a
different matter, as they must be included in the Radiator configuration file
(or held in an SQL database). If you really wanted to keep them in LDAP, you
could handle the requirement in a number of ways: first dump them into a text
file in Radiator format and have Radiator access the file with an "Include"
statement, second move them into an SQL database so Radiator can access them
there, or third - modify the Radiator source code to pull the Client
definitions from the LDAP server. The third option can either be done by you,
or we can discuss a contract solution to do it for you.
In any case, I am sure we can find a solution for you.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
