Hi all,
I have very simple conf as below:
Key somekey
AddToRequest NAS-Identifier=TACACS
GroupMemberAttr OSC-AVPAIR
AuthorizeGroup group1 permit service=shell cmd=show cmd-arg=.*
AuthorizeGroup group1 permit service=shell cmd\* {autocmd="telnet
169.163.226
Hello,
I’m trying to Backoff an SQL query to my database whenever a timeout
happened. I have the next configuration in my radius_auth.cfg :
RewriteUsername s/^([^@]+).*/$1/
AuthByPolicy ContinueWhileIgnore
DBSource
looks like your first AuthBy SQL is answering accept. is this maybe
because you don't have any 'check' options at all? Then if accept,
never process the AuthBy FILE because of ContunueWhileIgnore.
For example, maybe you need at least one check option:
AuthColumnDef 1, Encrypted-Password, ch
Hello Michael.
I have modified the AuthByPolicy fro mContinueWhileIgnore for
And now it jumps to the second AuthBy, but is not marking the DB as fail
(and therefor doing the Backooff Time), this is the log.
What I’m doing wrong?
Mon Nov 19 16:41:05 2012: DEBUG: Packet dump:
*** Received fr
I miss the change : ContinueWhileIgnore for ContinueWhileReject
*De:* Michael [mailto:ri...@vianet.ca]
*Enviado el:* lunes, 19 de noviembre de 2012 16:28
*Para:* Ricardo Martinez
*CC:* radiator@open.com.au
*Asunto:* Re: [RADIATOR] SQL Timeout
looks like your first AuthBy SQL is answering acce
I think you would have to query a 2nd time within 60 seconds in order to
see the BackOff in the log.
On 19/11/12 02:44 PM, Ricardo Martinez wrote:
Hello Michael.
I have modified the AuthByPolicy fro mContinueWhileIgnore for
And now it jumps to the second AuthBy, but is not marking the DB as
I’m doing 3 or even 4 querys for each one and keeps connecting to the mySQL
server and not doing the BackOff.
The Timeout parameter seems to be very clear about the behavior :
*5.31.4 Timeout*
This optional parameter specifies a timeout interval in seconds that
Radiator will wait
for when try
On 11/19/2012 10:47 PM, Ricardo Martinez wrote:
> Question : When it says “…Radiator will wait for when trying to contact
> the SQL server…” this means that a */select/* is a CONTACT???
Hello Ricardo,
there is a contact before the select. The contact succeeds but the
subsequent query (DELYREQ) t
On 11/19/2012 10:13 AM, Murat Bilal wrote:
>
> GroupMemberAttr OSC-AVPAIR
Hello Murat,
note that you have set GroupMemberAttr to OSC-AVPAIR here.
>
>
> AuthColumnDef 1, OSC-Group-Identifier, reply
Here you are adding OSC-Group-Identifier to the reply. Maybe this
Is there another more safe way to do the BackOff. What I'm trying to do
is when a SQLquery is Timeout by Radiator mark the server as "down" and do
the next AuthBy Clause.
I saw a pair of question about the same issue near 2002 :
http://www.open.com.au/pipermail/radiator/2002-October/005289.html
P
There is also other post about the same issue :
http://www.open.com.au/pipermail/radiator/2011-April/017237.html
-Mensaje original-
De: Ricardo Martinez [mailto:rmarti...@redvoiss.net]
Enviado el: lunes, 19 de noviembre de 2012 18:36
Para: 'Heikki Vatiainen'; 'radiator@open.com.au'
Asun
Hi ,
I try this :
AuthSelect select PASSWORD,TACACSGROUPID from SUBSCRIBERS
and define
AuthColumnDef 0, User-Password, check
AuthColumnDef 1, OSC-Group-Identifier, reply
I got ERR: Execute failed for 'select PASSWORD,TACACSGROUPID from SUBSCRIBERS':
Unknown column 'TACACSGROUPID' in 'fiel
On 11/20/2012 09:18 AM, Murat Bilal wrote:
> AuthSelect select PASSWORD,TACACSGROUPID from SUBSCRIBERS
> and define
> AuthColumnDef 0, User-Password, check
> AuthColumnDef 1, OSC-Group-Identifier, reply
>
> I got ERR: Execute failed for 'select PASSWORD,TACACSGROUPID from
> SUBSCRIBERS': Unk
After changing my schema.I insert a user murat with passw murat and
TACACSGROUPID group3.Debug gets crazy.Endless loop as shown below:
Radius::AuthSQL REJECT: Bad Password: DEFAULT4303 [murat]
Tue Nov 20 09:52:31 2012: DEBUG: Query to 'dbi:mysql:radius:localhost': 'select
PASSWORD,TACACSGROUPID
14 matches
Mail list logo
