Hello Rajan -
I am not sure that I understand your question, but if you want to limit users to one NAS only or another NAS only, you can do something like this:
# define Client clauses
Identifier NAS1
.
Identifier NAS2
.
.
..
.
.
.
regards
Hugh
Hi all,
I have to use two authby clause one for
router1 and another for router2.
Now the problem is router2 user can be authenticate
dialing to router1. Since i have only one AAA server. Is it possible to check
handler in Client clause itself. Will this slove my problem.
Please help me.
Hello Mike, Hello Stephen -
Mike is correct, a NoDefault usually fixes this problem, which is due to the
LDAP server incorrectly returning a result for DEFAULT if it is not found.
Radiator by default will always look for "DEFAULT" entries in the user
database, but this can be altered with the
I ran into this problem also, you need to add the line NoDefault
to your LDAP Authby. See 6.17.12 in the manual. I am not quite sure why
I did this now, but it seems to work. If it does not find the user it
then tries the DEFAULT user.
Mike Forbes
On Mon, 18 Feb 2002, Stephen Davies wrote:
Hi,
I am trying to set radiator to authenticate against
and OpenLDAP database version 2.0.28
Openldap is working fine with everything else,
including my telnet and webmail (written in perl) access.
When I try to run radpwtst I get the error in the
logfile as:
*** Received from 127.0.0
I need help pls! and very URGENTLY too!
My RADIATOR Authentication is suddenly rejecting all passwords. It is
logging encrypted passwords in password.log.
I am not using encryption at all. I am authentication via ODBC. I tried
with User flat file without any success.
'Tunde Ogedengbe
Linkser
Hello,
Everything works fine now.
Thanks for your support.
Mike McCauley wrote:
>
> Hello Nacho,
>
> Thanks for the detailed description of this problem.
> Basically the problem is this.
> The default configuration for LDAP2 is to reject empty passwords, as protection
> against a problem in
redes <[EMAIL PROTECTED]>
> >Organization: EICSA
> >X-Accept-Language: en
> >To: [EMAIL PROTECTED]
> >Subject: (RADIATOR) Authentication problem
> >Sender: [EMAIL PROTECTED]
> >
> >This is really annoying me.
> >
> >I've already posted this,
This is really annoying me.
I've already posted this, but I'm going to put it in a more
comprehensive way.
We are using Radiator 2.16.3 + OpenLDAP + MySQL
We use LDAP for authentication and MySQL por IP allocation.
This configuration works fine with radpwtst, the authentication is ok
and the IP
