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 the ChilliSpot-Max-Total-Octets quota and the Idle-Timeout does not appear to work. How does radius send a stop session command to the coovachilli router, perhaps that's where the issues is? Regards Carl
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, perhaps that’s where the issues is?
FreeRADIUS doesn't send a stop session command. 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, perhaps that’s where the issues is?
FreeRADIUS doesn't send a stop session command. Alan DeKok. - Thanks Alan, The Freeradius database holds the ChilliSpot-Max-Total-Octets amount so I thought it was to do with Freeradius. I gather though that coovachilli must read this amount and pass it on to the router. List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Fri, Oct 14, 2011 at 9:57 AM, OzSpots - Carl Sawers <carl@ozspots.com.au> 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 Alan, The Freeradius database holds the ChilliSpot-Max-Total-Octets amount so I thought it was to do with Freeradius.
Radius (including freeradius) simply sends the attributes it's configured to do. So if it sends ChilliSpot-Max-Total-Octets, and you've verified that it's the correct attribute (e.g. by looking at dictionaries on /usr/share/freeradius/*, and comparing them to what chilli/coova expects), then that's pretty much it. Whether the NAS respects it or not doesn't really concern radius.
I gather though that coovachilli must read this amount and pass it on to the router.
coovachilli and chillispot are captive portal acess controller. They act as NAS. They don't need to "pass" anything to any router. I suggest you try running coova/chilli in debug mode and see what it says. Also look at their soure code. I remembered a long time ago wondering why chilli ignores Acct-Interim-Interval. Turns out chilli will silently ignore that attribute if the value is <= 60s. So something similar might be happening in your case. -- Fajar
participants (3)
-
Alan DeKok -
Fajar A. Nugraha -
OzSpots - Carl Sawers