2012-07-24 - Re: [GRASE-Hotspot] Remaining Data bug?

Header Data

From: Tim White <ti***8@gmail.com>
Message Hash: 80066b834e5897a9c6c4846e96ad4ad1b9e999cc4c594e2d014403863d533af6
Message ID: <500F09CF.4080501@gmail.com>
Reply To: <CAA-jMMTk3PrebQjqd39kJOOffuOeQzWHuLOP1D-Z+C0CXy6k4Q@mail.gmail.com>
UTC Datetime: 2012-07-24 13:47:11 UTC
Raw Date: Wed, 25 Jul 2012 06:47:11 +1000

Raw message 

Hi Bob.

Quoting my previous email today.
>
> There was some posts to the list a little while ago about the 4Gb data 
> limit. It's a limitation with Freeradius, and as I've not had a 
> computer for the last 3-4 months, I've not been able to even tackle it.
> So far, the solution for now is to limit your ticket sizes to 4Gb. I 
> know it sucks, but apparently it's been a freeradius bug for a long time.

Changing the chillilib.js file only changes what is displayed on the 
status page. The reason the change shows things properly, is we fetch 
user information from 2 locations, one from the chilli session, and one 
from the database. It's the chilli session information that will affect 
the session, hence we try and use as much data from that when possible.

In terms of updating. Just do "sudo apt-get update; sudo apt-get 
upgrade" and it'll upgrade for you. And yes, any changed files will need 
to be "restored" as Debian will overwrite all files in a new package.

Tim

On 25/07/12 01:43, Bob Hunt wrote:
> Hi Tim,
>
> I installed grase-repo_1.3_all.deb onto a Ubuntu 11.10 server and I'm 
> generally very impressed. Thank you for all the great work.
>
> I've been working on customizing Grase up to suit my needs and have 
> found what I think may be a bug which shows the wrong info in the 
> "Remaining Data" field of the ../grase/uam/mini page and also carries 
> through to prematurely cause the user to get shut out with a 
> "Bandwidth Exceeded" message. (I'd prefer it to say "Data Quota 
> Exceeded" as I usually think of bandwidth as a measure of throughput 
> or speed).
>
> I tracked down the issue to line 1124/5 of 
> /usr/share/grase/uam/js/chillilib.js, where changing both instances of 
> "chilliController.session.maxTotalOctets" to 
> "chilliController.user_details.monthlyusagelimit" seems to make it 
> behave (almost) properly. The issues I still see remaining after the 
> change are that when the data limit is exceeded, the data in the field 
> shows up as 'unlimited' and the user is not disconnected and refused 
> access until next attempted login.
>
> There is also what seems to be a copy of the same file located at 
> /usr/share/grase/uam/chillilib.js, but changing this file doesn''t 
> seem to have any effect on behaviour, but I guess it could affect 
> behaviour in places I haven't seen.
>
> I see that grase-repo_1.4_all.deb is now available. I'm guessing that 
> this will simply install over the top of my existing Grase install, 
> but that I'd need to back up any customized file changes I've already 
> made to my existing install first.
>
> Best Regards,
>
> Bob
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Grase-hotspot mailing list
> Gr***t@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/grase-hotspot

Thread