Re: Execute some action when user terminate session

2012-03-29 Thread Alan DeKok
Lorenzo Milesi wrote: > I need to perform several queries on radacct to make statistics about user > connection, duration and so on. > Since executing some queries can be time consuming it's not advisable that I > run them on the radius database, so I'm considering copying all or some > informat

Execute some action when user terminate session

2012-03-29 Thread Lorenzo Milesi
Hi. I need to perform several queries on radacct to make statistics about user connection, duration and so on. Since executing some queries can be time consuming it's not advisable that I run them on the radius database, so I'm considering copying all or some informations from radacct somewhere

Re: terminate session

2011-10-13 Thread Fajar A. Nugraha
On Fri, Oct 14, 2011 at 9:57 AM, OzSpots - Carl Sawers wrote: > OzSpots - Carl Sawers wrote: >> The user can also go over the ChilliSpot-Max-Total-Octets quota and >> the Idle-Timeout does not appear to work. > >  Then it's a chillispot problem.  It has nothing to do with FreeRADIUS. > Thanks Ala

RE: terminate session

2011-10-13 Thread OzSpots - Carl Sawers
OzSpots - Carl Sawers wrote: > The user can also go over the ChilliSpot-Max-Total-Octets quota and > the Idle-Timeout does not appear to work. Then it's a chillispot problem. It has nothing to do with FreeRADIUS. > How does radius send a stop session command to the coovachilli router, > perh

Re: terminate session

2011-10-13 Thread Alan DeKok
OzSpots - Carl Sawers wrote: > The user can also go over the ChilliSpot-Max-Total-Octets quota and the > Idle-Timeout does not appear to work. Then it's a chillispot problem. It has nothing to do with FreeRADIUS. > How does radius send a stop session command to the coovachilli router, > perhap

terminate session

2011-10-13 Thread OzSpots - Carl Sawers
Hi All, I am using the latest freeradius and coovachilli and am having a terminate session problem. Some user sessions are not stopping, the session time shown in the DB stops but the user does not logout and there is also no reason given in the DB for termination... The user can also go over