(RADIATOR) TimeBanking

[Ronan Eckelberry]

    If you have some customers that are limited by time and some that
are not, you will need to setup multiple "AuthBy" clauses (1 for each
type).  I would recommend using handlers and also setting some sort of
"ReplyAttribute".  Something like "CLASS=LIMITED and CLASS=UNLIMITED".
That way the handlers can tell which authby to use for which.  If you
are still having problems I can send you a snip of my config to point
you in the direction.
 
    The TIMELEFT field should be a reply in your Auth and set as the
"Session-Timeout".  Something like:
 
AuthSelect select PASSWORD,PORTLIMIT,STATICIP,SIMLOGIN,TIMELEFT from
LIMITED_20HRS where USERNAME='%n' AND ACTIVE='Y'
        AuthColumnDef 0,User-Password,check
        AuthColumnDef 1,Port-Limit,reply
        AuthColumnDef 2,Framed-IP-Address,reply
        AuthColumnDef 3,Simultaneous-Use,check
        AuthColumnDef 4,Session-Timeout,reply
 
    If Session-Timeout is a negative number, the customer should not be
able to log on.  I know I receive quite a bit of messages in my logs
that look like:
 
Fri May 31 15:49:53 2002: ERR: There is no value named -49063 for
attribute Session-Timeout. Using 0.
 
    And the next time they attempt to log in, they are denied access.
As for why they were a llowed to stay on for the amount of time that
they did to make it a negative number, I have no clue.  Possibly lost
STOP packets.  That is a question that I have been meaning to ask, but
have not gotten around to.
 
    And yes, I have my limited and unlimited customers seperated into
different tables and an AuthBy for each table.
 
    Again, if you are still having trouble I can send my config.  I just
haven't done it yet because that is a lot to paste into a message and
might get confusing.
 
-Ronan

 
-----Original Message-----
From: Jaskaran Singh [mailto:jsingh at fdu.edu] 
Sent: Friday, 31 May, 2002 10:44
To: 'Ronan Eckelberry'
Subject: RE: (RADIATOR) TimeBanking


Hey Ronan
I appreciate, you pointed me towards the right direction, I implemented
the solution, but I have a problem now, even when the TIME_LEFT column
is negative
I get authorized any suggestions. One more Question, I am using LDAP to
do authentication and the TIME_LEFT thing as the last SQL check, so does
that mean that I have to add my entire LDAP users into another user
table and set Max_Time limits on them.
I appreciate your input.
Thanks
Jack
 
 
-----Original Message-----
From: Ronan Eckelberry [mailto:radiator at gowebco.com] 
Sent: Thursday, May 30, 2002 6:33 PM
To: 'Jaskaran Singh'; radiator at open.com.au
Subject: RE: (RADIATOR) TimeBanking
 
Jack,
 
    Take a look at the mailing list archives and look for
"AcctSQLStatement"  You should find quite a few in there matching what
you are looking for.  That is the statement that is mostly used to
"update" the MySQL row when the user logs off.....If you cannot see what
you are looking for, I can send my config (Secrets and Addresses removed
to protect the guilty), and you may be able to go off of it.  I would
recommend checking the archives first though.  There is SOOOOOO much
info in there from Hugh and the other contributors.  Also, as Hugh said,
the goodies directory has a lot in it, particularly the
"/goodies/blocktime.txt" example.
 
 
-Ronan
 
-----Original Message-----
From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] On
Behalf Of Jaskaran Singh
Sent: Thursday, 30 May, 2002 15:58
To: radiator at open.com.au
Subject: (RADIATOR) TimeBanking
Hi,
Could anyone please lead me in the direction of the documentation as to
how to setup a maximum time and time left for a user in mysql database.
Thanks 
Jack
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20020531/24e11202/attachment.html>