Re: SqlCounter reload after initial authentication
As Alan said this happens since the remaining time was already sent to the NAS which causes the disconnection, although if the user added more time then after he was initially disconnected by the NAS the user may still login again for the remaining time (which is the delta - what he already added - what he already finihsed). Seems like a reasonable work-around for the user to simply re-connect for the remaining time. Regards, Liran. On Thu, Aug 12, 2010 at 10:07 AM, wrote: > > I'm using Freeradius + Chillispot+MySql for hotspot. Sqlcounter > noresetcounter works fine for prepaid access time, however the counter is > loaded only once when the user first authenticate. > This means that even if Max-All-Session changes after initial logon (as it > happens when the user adds more credit) the user is session is still > terminated at the end of the initial count down. > How can I force Freeradius sqlcounter to re-load and begin counting down > when Max-All-Session is updated after initial authentication? If this is not > possible any workaround or hacks to accomplish this behaviour will be > greatly appreciated. > Thanks. > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: SqlCounter reload after initial authentication
tadi...@verizon.net wrote: > I'm using Freeradius + Chillispot+MySql for hotspot. Sqlcounter > noresetcounter works fine for prepaid access time, however the counter is > loaded only once when the user first authenticate. > This means that even if Max-All-Session changes after initial logon (as it > happens when the user adds more credit) the user is session is still > terminated at the end of the initial count down. > How can I force Freeradius sqlcounter to re-load and begin counting down when > Max-All-Session is updated after initial authentication? If this is not > possible any workaround or hacks to accomplish this behaviour will be greatly > appreciated. You can't. The SQL counter module returns a Session-Timeout attribute to the NAS, and the *NAS* is the one enforcing the session length. If you update the database, the NAS doesn't know this, and still enforces the session length. Read the NAS documentation to see how it can extend existing sessions. If the documentation doesn't describe how to do it, it's impossible. And it's *not* a FreeRADIUS issue. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
SqlCounter reload after initial authentication
I'm using Freeradius + Chillispot+MySql for hotspot. Sqlcounter noresetcounter works fine for prepaid access time, however the counter is loaded only once when the user first authenticate. This means that even if Max-All-Session changes after initial logon (as it happens when the user adds more credit) the user is session is still terminated at the end of the initial count down. How can I force Freeradius sqlcounter to re-load and begin counting down when Max-All-Session is updated after initial authentication? If this is not possible any workaround or hacks to accomplish this behaviour will be greatly appreciated. Thanks. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
