(RADIATOR) Wi-Fi and Session Timeout

[Camilo Echeverry]

By now I've done this: (and is working :)

I use a (goodies dir) hook to get the inner authentication attributes
this hook keeps record of last user authentication in a table
(RADLASTAUTH) with a timestamp and other data (username, nas-type,
nas-port. etc)
So when Radiator receives a reauthentication, the hook calculates the
period of time between the current and the previous reauthentication
and substracts it from the user's account.
if the users time remain becomes zero (or negative) the hook returns 
main::REJECT
as you see, I mus to do at least three sql queries to the Database

Does somebody have a better/faster idea ..?

Thanks,
On Thu, 10 Mar 2005 17:19:01 -0500, Camilo Echeverry <camilin at gmail.com> wrote:
> I've Tried to find the Service-Type attribute within the authentication packets
> but had no luck
> Also tried the Ascend-Maximum-Time attribute but the AP also uses it
> as reauthentication Time.
> 
> So I'll explain (with more words) what I want to do:
> We are planning to sell Wi-Fi connection by Megabytes (thats another
> story) and by prepaid Time (this is the current story)
> So we need disconnect the user when his prepaid time is over,
> this is pretty easy with the modem connections using the Session-Timeout Attr.
> 
> We store all the auth and acct data in an Oracle DB.
> I'm using an ORACLE trigger which substracts time from the users
> account with each "Stop" based on the Session-Time Attr, but the only
> way (I know) to get such Stop is when the user gets disconnected
> so: if a user stays connected forever, there will be no way to disconnect him.
> 
> Any Idea .?
> 
> 
> On Thu, 10 Mar 2005 09:25:56 +0000, Roy Badami
> <roy.badami at globalgraphics.com> wrote:
> > >>>>> "Camilo" == Camilo Echeverry <camilin at gmail.com> writes:
> >
> >     Camilo> Or is there some kinf of identifier which makes the
> >     Camilo> difference between the first authentication and the
> >     Camilo> subsecuent Reauthentications.
> >
> > IME, the Cisco AP will set Service-Type=Login-User on the initial
> > authentication, and Service-Type=Authenticate-Only on the
> > reauthentication.
> >
> >         -roy
> >
> >
> 
> --
> :wq
> ----------------------
> Camilo Echeverry
> ----------------------
> 


-- 
:wq
----------------------
Camilo Echeverry
----------------------

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.