> 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?
Our provider tells me they have no problems sending Input and Output
data fields upto very large sizes, Im presuming they are telling the truth. Therefore
in theory if I wrote my own daemon to sit on the port and collect the accounting
records, I can then place the Acct-Input-Octets and Acct-Output-Octets values
in variables that are of a type that can handle the size, I can then directly enter these
values into my database and forward a copy of the record to freeradius.
In theory of course I have no idea if this will work at the present time.
Acct-{Input,Output}-Octets are defined as 32-bit integers from the RFC. There's no way your provider could send you variables 'upto very large sizes', so there's no point in having any 'daemon' listening for them. If they will not be sending Acct-{Input,Output}-Gigawords they are lying.
I have spoken to them again and they appologise for giving me the wrong information. Anyway looks like im getting somewhere now as they are going to have to look into enabling Gigawards.
Thanks for the information.
Cheers
Mike
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
