[RADIATOR] RADIUS limit on accounting data

[Michael Harlow]

Hi,

I've struck an issue with my accounting data, where it wraps. Initially the database refused the INSERT  once it exceeded a signed 4-byte integer (2Gb). I changed the database to bigint, and so it can now handle 8-byte integers. Now however it wraps at unsigned 4-byte integer (4G). I've traced it down to the value in the RADIUS packet coming into Radiator. My NAS is doing the wrap. 

Before I hassle the vendor (Cisco WiSM), does the RADIUS protocol allow for a larger accounting attribute, or does all NAS have this 4G limit?  The raw dump of the attribute seems to be something like 2f 06 xx xx xx xx, where the 2f (or which ever it is) is the attribute identifier, the 06 seems to be the total length of the attribute, and the last 4 bytes are the value. Can accounting appear as eg 2f 0a xx xx xx xx xx xx xx xx or will the RADIUS standard, and Radiator barf?

A student can exceed the 4G value in a single wireless session on 54M 802.11g network in just over an hour. Who knows how many minutes on 802.11n before the accounting becomes invalid!

Thanks, Michael

-----------------------------------------------------------------
Yesterday is history, tomorrow is a mystery, but today is a gift.
That is why it is called the present. [Oogway - Kungfu Panda]
-----------------------------------------------------------------
Michael Harlow                     Private Bag 69
Network Engineer                   Hobart Tasmania 7001
IT Resources                       Ph  03 6226 1812
University of Tasmania             Mob 0438 26 1812
Michael.Harlow at utas.edu.au         Fx  03 6226 7171
-----------------------------------------------------------------