Townsley, I had several problems with SQL accouting, from zero-timed sessions to really high numbers (millions of minutes in a session). I reversed to flat file logging and them import in a batch everyday to the database. Works like a charm.
Plus, I was unable to open the number of sockets that I have to for some unknown bug that wasnt fixed til 0.5. Regarding the "UDP-nature" thing, theres not much that we can do, ask your dial providers to increase the number of retries and timeouts for accouting packets, that may fix most of your problems... Laters, Edgard Castro > -----Original Message----- > From: J. S. Townsley [mailto:[EMAIL PROTECTED]] > Sent: Monday, March 18, 2002 2:24 PM > To: [EMAIL PROTECTED] > Subject: Accurate Accounting? > > > > I'd just like to get a feel for how all of you are doing your > accounting. > I need an accurate accounting method so that I can watch my > users sessions > more closely when they are reaching peak usage on some of my networks. > > I've always used SQL for this, but I have more and more > sessions with zero > accountstoptime and zero acctsessiontime. I do realize some > of this is > just due to the nature of UDP but it still seems a bit excessive. > > I've had this problem with multiple dialup wholesalers, and > even my own > legacy POP's. My previous radius implementation with SBR had > this same > problem. > > So, how do you guys handle it? Still doing accounting with detail > records? I guess I could look and see if my detail records > are in sync > with my SQL accounting. > > --JST > > > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
