Re: Your maximum never usage time has been reached
Thanks Alan
the easyhotsort people have leveraged, from what i can see, chillispot and FreeRADIUS for their solution. as such, they are the ones who are first in line to fix things....I dont see why the volunteers in FreeRADIUS should deal with the random logic and code from a 3rd party solution.
Fair call.
This only occurs for users where the check-name attribute is "Max-All-MB". If there is no check for this attribute then the user can
are you checking the the attribute EXISTS - in which case it will always be the case unless is only exists if another system make it so (from reading accounting) or is is supposed to be a comparison with a value.
If I create a user where the attribute does NOT exist then I can authenticate but cannot keep the user to the total data allowance (see below as why this is required). If I create a user where the attribute does exist then after the accounting record is created in the radacct table then subsequent attempts to authenticate fail. Maybe it's time to read the source code for the counter module :(
sorry, dont care for captive portals - I'm all about 802.1X and proper systems and dont beleive that customers should be limited to small amounts of data allowance - its 2010.... 1998 have called and want their business model back.
Yeah - I'd rather provide an unlimited data allowance too but in this case it is not possible. I've taken on the task (as a volunteer) to provide a hotspot for a community group's conference and the only broadband access we have at the venue is via a 3G mobile service (limited to 3GB in a month) :( Additional data is priced at $100/GB !! David
Hi,
Maybe it's time to read the source code for the counter module :(
the documentation should be more than enough.....if the rest of the config is fine, then the issue is that you are setting some attribute as a comparison ... := which would always be true. you need to set it as a value check instead eg >= alan
Thanks for your help Alan Although your hint was not quite right (the correct operator is ":=") it did point me in the right direction. The value stored in the database for the check was in MB and the sql query in the counter.conf file was summing accounting records which are stored in octets (bytes). So a quick change to the query and it's now working fine. Once again - many thanks David On 01/06/10 00:08, Alan Buxey wrote:
Hi,
Maybe it's time to read the source code for the counter module :(
the documentation should be more than enough.....if the rest of the config is fine, then the issue is that you are setting some attribute as a comparison ... := which would always be true. you need to set it as a value check instead eg>=
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
Although your hint was not quite right (the correct operator is ":=") it did point me in the right direction. The value stored in the database for the check was in MB and the sql query in the counter.conf file was summing accounting records which are stored in octets (bytes).
ah! well, I'll make a mental note of that situation
So a quick change to the query and it's now working fine.
cool.
Once again - many thanks
thats okay - glad to be of help alan
participants (3)
-
Alan Buxey -
David Moorhouse (FR) -
freeradius＠moorhouse.net.nz