2012-06-19 - Re: [GRASE-Hotspot] 5Gb ticket problem

Header Data

From: Timothy White <ti***8@gmail.com>
Message Hash: 6d786c4181a5dd2f1eb83a4e38427bcaf4119e66f9422678bbec0fa88d51126e
Message ID: <CAESLx0+oMYGFDUvCThMAKdgiP2TVKLxaw6w-99SmZPFKNwdbvQ@mail.gmail.com>
Reply To: <1340111505.99254.YahooMailNeo@web161403.mail.bf1.yahoo.com>
UTC Datetime: 2012-06-19 17:38:20 UTC
Raw Date: Wed, 20 Jun 2012 08:38:20 +0800

Raw message 

Just done some investigations relating to this. Turns out it's a
limitation in Freeradius. See
http://freeradius.1045715.n5.nabble.com/Problem-with-rml-sqlcounter-with-GigaByte-datavolume-td4455164.html

When I have my development machine in a few weeks, I'll look at diving
into the freeradius code and patching it to work. I'll also see if I
can find some sort of workaround to make it work properly for older
code. There is a ticket already regarding the display of 5Gb tickets,
I assume you probably filed it. http://trac.grasehotspot.org/ticket/38
I'll ether work on that ticket or link it to another one with the
freeradius issues.

Unfortunately I won't have a fix in the next few weeks as it seems
it'll require changes to freeradius. I've been trying hard to not
modify the components we use, so that there is less code we need to
maintain (we have a custom coova chilli version, but finally the
patches we've maintained have been integrated into coova chilli so our
coova chilli is now closer to the mainstream one!).

The best interim solution (not ideal I know) is to issue 4Gb tickets
and 1Gb tickets. Unfortunately there is not "transparent" interim
solution that I can work out, the work arounds other people have used
is to use rlm_perl to write their own handling code, which is not a
good way at all!
You'll notice it also has issues with displaying large volumes of
traffic uploaded/downloaded in the status window, this is a javascript
issue so I'll address that separately as well.

I'd personally not reached this limit before, as previously it was a
2Gb limit and when that was fixed I didn't know that it was now
limited at 4Gb. Most of the places I use the hotspot are time limited,
not data limited.

Thanks for bringing it to our attention, and sorry a fix won't be
available soon.

Tim

On Tue, Jun 19, 2012 at 9:11 PM, tim storey <ts***s@yahoo.com> wrote:
> Hi Tim
>
> The range of tickets I offer my clients includes a 5 Gb ticket. The mini
> screen unfortunately shows such tickets as being 4 Gb in size (although the
> status and admin screens reflect the correct value) and when such a ticket
> hits the 4 Gb limit Grase prevents the customer from logging in again due to
> the data volume being exceeded.
>
> My low-tech work-around is to give those customers a free 1 Gb ticket in
> exchange for their unusable 5th Gig, but I would really like to not have to
> do the extra admin.
> I would also like to offer 10 Gb tickets (and larger) to my heavy
> downloaders, but cannot do so until this issue is resolved.
>
> ------------------------------------------------------------------------------
> 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