"Mike Smith" <[EMAIL PROTECTED]> wrote: > I am having trouble with usage based statistics because freeradius stores > its Acct-Input-Octets and Acct-Output-Octets octets in an integer.
The RFC's specifiy that those attributes go into a 32-bit integer in the RADIUS packet. FreeRADIUS is therefore limited by the RFC's. > While this is great for Dial-up monitoring it a bit of a problem for ADSL > when the Input and Output values often exceed 4294967295 bytes > at which point it resets to 0. FreeRADIUS has no control over that. > I have asked our provider to send us the Gigawords attribute but they > do not support it. So my question is are the Freeradius developers > working on a solution to this one at the moment, or is this a complete > rewrite into another language to overcome it? There is no real solution, other than having the provider send the Gigawords attribute. FreeRADIUS can't log information it doesn't have. What may *help* is that if your provider sends accounting packets quickly enough (like every 10 minutes), to keep track of the *last* value for Access-Input-Octets. If the new value is smaller than the old one, yuo can "guess" that it rolled over, and add 2^32 to the new value. It's a hack, but it will help. It won't be perfect, though. > Anyone know a way round it other than me writing a daemon that > collects the data and then passes it to freeradius afterward. Collects *what* data? You just said that the provider wasn't sending Gigawords attributes to you. Why would another daemon be able to do something that FreeRADIUS can't? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
