|
>Some people
use a solution that does not use Session-Timeout at
>all. They run a daemon that checks the radutmp file every minute >or so and for every user logged in, checks their time credit in >the database and disconnects the account if it's over credit. > >This is quite a kludgy solution, IMHO. > >If you think about it, with Session-Timeout the only little >nuisance is that the user has to hangup to get the new >Session-Timeout. Is that really a big deal? How often does it >happen in real-life that the user is logged in and his account is >updated? > > >-- >Mojahed >System Administrator >Agni Systems Limited Thanks for your comments. Could you give me more
information about the How the
deamon can cut the session ? I mean, using what
type of protocol ? What is IMHO?
I already have the trigger that can tell me if the user spent whole the
credit, but I don't know how to tell the NAS that cut this session....
Thanx in advance!
Carlos
|
- Handling limt credit with Radius Carlos Lerma
- Re: Handling limt credit with Radius aland
- Re: Handling limt credit with Radius Carlos Lerma
- Re: Handling limt credit with Radius Mojahedul Hoque Abul Hasanat
- ./configure problems Carlos Lerma
- ./configure problems Joe Hayes
- RE: ./configure problems Jason Lixfeld
- Re: ./configure problems Joe Hayes
- Re: ./configure problems Chris Parker
- Re: ./configure problems Joe Hayes
- Re: ./configure problems Bill Campbell
- Re: Handling limt credit with Radius Andreas Faust
