Hi Hugh,
>
> You should try using AuthBy LDAP2 and the corresponding Net::LDAP module.
> Please have a look at section 6.30 in the Radiator 2.14.1 reference manual
for
> a discussion of the various LDAP options.
>
> Could you also let us know what LDAP server you are using?
>
> Note that there is a recent patch for Radiator 2.14.1:
>
> 7/1/00 Fixed a problem with AuthBy LDAP2, where recent versions
> of Net::LDAP do not support ldap_error_message.
> Download a new AuthLDAP2.pm from here.
>
Thank you for your reply. We have tried the modification yesterday
evening and it seemed that the situation became worse. What we have done
were:
1. Installed perl-ldap-0.13.tar.gz
(perl Makefile.PL; make; make test; no error-> make install)
2. Upgraded the AuthLDAP2.pm in perl lib directory.
3. Changed radius.cfg so it used <AuthBy LDAP2> instead of <AuthBy LDAP>.
4. Restarted the server.
Afterwards we observed the log and the requests and response kept coming
in, so we thought the change was okay. However, upon further testing with
radpwtst we found that we got "No Reply" with all three types of requests.
When we did actual dialup testing, the client timed out even though the log
said Radiator has sent back both access-accept and accounting-response (our
NAS here at the local telco was set to grant permission only after receiving
accounting-reponse).
Investigation from telco told us our radius service did not respond from
time to time. So finally we reverted the configuration to use old LDAP
service and it started working again (for the time being).
We are using openldap-1.2.7-2 rpm for redhat6.1 for providing LDAP
service.
Thank you very much for your advice in this issue again, in particular I
would like to know whether we have skipped any steps in changing to the
LDAP2 module, and why the radpwtst stopped working with the new
configuration.
--
Aaron Liu
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
