Gigaword support

[David Roze]

Hi,

Glad to know Gigawords support has been added in the CVS. The method with 
extra field is quick
and easy for most of us but I agree it's always better not to change the
backend structure...
That's pretty much what I had to do to append accounting values at regular
intervals: compute the values first. See 
http://www.netexpertise.eu/en/FreeRadius/DailyAcct.html

Thanks for your input

David
----
http://www.netexpertise.eu


Hi,

> Thank you! It would be nice if FreeRadius could have more support for
> Gigawords built in!

FYI: CVS just got a commit that includes Gigawords support for the mySQL
backend. It behaves pretty much like the one in postgresql, which, for the
record, has had Gigawords support included since long time ago.

The behaviour is different from that in the quick-n-dirty HOWTO that was
referenced in this thread: the correct octet value is computed out of the 
two
attributes Acct-*-Gigawords and Acct-*-Octets and the result is saved in the
Acct*Octets column in radacct. No seperate column to catch the Gigawords is
necessary. IOW: it just works now. If the client sends Gigawords, your
accounting table will contain the 64-bit value.

For FreeRADIUS 2.0, this obsoletes the steps

"Mysql Table Modification" and
"Freeradius Update"

in

http://www.netexpertise.eu/en/FreeRadius/GigaWords.html

I.e.: just configure your NAS, the server side will handle it just fine.

Greetings,

Stefan Winter