On Sun, Nov 9, 2008 at 6:00 AM, Venkatesh K <kaevee@gmail.com> wrote:

Hi Liran,

On Sun, Nov 9, 2008 at 4:16 AM, liran tal <liransgarage@gmail.com> wrote:
> Hey Venkatesh,
>
> On Fri, Oct 31, 2008 at 2:26 AM, Venkatesh K <kaevee@gmail.com> wrote:
>>
>> rlm_sqlcounter has one more limitation. In version 1.1.7, the maximum
>> counter value was limited to <2G whereas in 2.1.1 it seems to be <4G.
>> This imposes an artificial limitation of maximum of 4GB of downloads.
>> I had a workaround where I patched rlm_sqlcounter to limit the per
>> session downloads to 4GB if allowed usage exceeds 4GB.
>
> Sorry for the late reply.
> I applied your patch and now data counters work as expected with a minor
> exception, the 2Gb limit
> as you have stated previously. Possibly you could also post the patch for
> the 2Gb/4Gb limit?
> I'm hoping it's compatible with FR 1.1.7 as well.
>

It is ok. I am happy to know it works for you. I will email you a
patch for 1.1.7 in couple of days. The patch is going to impose
certain limitations on you. The maximum return value should be less
than unsigned integer(32bit). The maximum reply value for data will be
limited to 4GB even if actual value is more than 4GB. So, there will
be a per session limit of 4GB though user is authorized to transfer
more data.

So the check value of the attribute remains a number bigger than 4GB, for example an 8GB

limit but the reply attribute that is sent will contain a value of <= 4GB due to the limit?

Thanks,

Liran.