> Brian Kolaci <[EMAIL PROTECTED]> wrote: > > I know it has support for users & accounting logging. > > Then why did you ask that exact question?
I didn't. Bryan did, I was answering that one. > > > I'd like to know if it has support for authentication logging > > I don't know what you mean by that. > > 'Who logged in' comes from accounting logs. I don't see why you > would need to log authentication requests. The authentication packet comes in and is ACK'd. The accounting packet was lost. Unfortunetly, this happens *alot*. Every day I need to use radzap to kill the logins that the accounting Stop packets were lost. So I'm sure there are instances where the Start packets are lost as well. > > That isn't currently supported (no default SQL statements), but > there's no reason why you can't write your own SQL statements to log > authentication requests. Yes, but to do so with the sql module? Is that possible? Or do I need to maintain a separate database connection pool? I do not (nor wish to) use sql for the users information (radcheck, radreply, etc). I only want it for the accounting (for planning) and for authentication logging. > > > I'd like to have all the info in the radius.log file in the > > database, > > I don't think that's a good idea. The radius.log file contains a > LOT of other log messages, too. > > > which then assures we have a record of all successes & failures for > > both billing and for support folks to see the incorrect passwords the > > user is entering. > > You can do this via custom SQL statements. But is this for authentication packets or accounting packets? I want to *log* the authentication request/response, but use files to hold the authentication information. With 0.6 it didn't seem possible with the sql module. Thanks, Brian - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
