total data transfer size

[Oguzhan Kayhan]

>> It might signify that you're using AcctOutputOctets only, instead
>> of combining them with AcctOutputGigawords.
>>
>
> Indeed. Integers in RADIUS are unsigned 32bit. This leaves room for
> integers between 0 and 4,294,967,295. I believe there was also an
> issue in earlier chillispot versions where internally the octets were
> counted on signed integers, reducing the max (positive) value by
> half. CoovaChilli now uses an unsigned 64bit value of which the upper
> 32bits are put in giga attributes (if needed).
>


So, i found a webpage describing to combine octets with gigawords,
for a crosscheck i wonder if the following is enough for using gigawords..

Adding the following to mysql.

ALTER TABLE radacct CHANGE AcctInputOctets AcctInputOctets BIGINT(20);
ALTER TABLE radacct CHANGE AcctOutputOctets AcctOutputOctets BIGINT(20);

And replacing '%{Acct-Input-Octets}'  in sql.conf with
'%{Acct-Input-Gigawords:-0}'  << 32 | '%{Acct-Input-Octets:-0}'

(and also outpout octets too)

Or do i have to do smthing more?

Or should i follow a different way?



>> Which brings me to another question: Why on earth does Coova
>> reverse InputOctets and OutputOctets when compared with Chillispot?
>>
>
> Regrettable, yes. But, not without reason. It's just at the time the
> motivation was  compatibility with commercial hotspot gear we were
> using. You can always go back with the option 'swapoctets'. See:
>
> http://coova.org/wiki/index.php/CoovaChilli/RADIUS
>
> David
>