Thanks for pointing in the right direction with rlm_sqlcounter. I think I have it working correctly, but I am not seeing how the following situation can be accounted for.
The Max-All-Session attribute is working great if I want to allow a user to buy a block of time and they can use it in increments. But say I want a user to be able to buy a block of time that will expire at a certain time regardless of how long they spend online during that time. Can you give me an idea of the direction I should go to accomplish this? Thanks again for the help and please excuse my ignorance as I am just muddling through this. Thanks, will -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alan DeKok Sent: Monday, July 18, 2005 4:35 PM To: FreeRadius users mailing list Subject: Re: newbie questions using freeradius as wifi access point "Will Carter" <[EMAIL PROTECTED]> wrote: > 1. I have a separate database from radius that authenticates the user's > login/password. I delete all rows from from radcheck for this user. I delete > all rows from radreply for this user. I add back a radcheck record and > radreply session-timeout record that corresponds to how much time left that > they have paid for. Now I log them in (using an xml command to my nas). Wow... why not just use the "sqlcounter" module, which keeps track of all of this for you? > The underlying problem with this set up is that ... it's unnecessarily complicated. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
