I'm using LDAP for authentication and authorization across several radius servers. I'm thinking that using a single mysql server for accounting from all my radius servers might be a significant advantage over using multiple detail files on multiple servers and parsing these detail files with a script. Before I dive into this, I'd like to get opinions from others who are using mysql for accounting:
1) anyone using mysql for accounting only - using another authentication and authorization? If so is the setup as simple as using the sql schema included with freeradius and just including "sql" in the accounting section of the radiusd.conf file? 2) are there significant gains to be made in terms of access to data and report generation using mysql over perl scripts or other programs written to parse the detail file and generate flat files with relevant information? My guess is that with a mysql database of accounting data, I should be able to access just about any kind of information I wanted from a properly formed sql query (like ip address usage data, time-on-line information for customers and just about any other kind of trending data I could imagine). Am I correct in that assumption or are there significant hurdles to using a mysql accounting-only system that I should be aware of? 3) If the idea of using mysql as an accounting system makes sense, are there existing tools that anyone knows of that are already written to generate various reports on radius accounting data? Thanks, Mike - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
