RE: Reporting from logs

2012-09-26 Thread Leal, Paulo
Many thanks for the responses, think SQL is the way forward and then query the database. Cheers Paulo -Original Message- From: Matthew Newton [mailto:m...@leicester.ac.uk] Sent: 25 September 2012 14:39 To: FreeRadius users mailing list Subject: Re: Reporting from logs Hi, On Tue

Reporting from logs

2012-09-25 Thread Leal, Paulo
Hi guys, We are new to eduroam and we are using FreeRadius for authentication and connection to national proxies. Just wondering what kind of reporting you have managed to get out from the FreeRadius logs, we wanted some user friendly reports with user numbers, success and failed attempts,

Re: Reporting from logs

2012-09-25 Thread Michael Schwartzkopff
Hi guys, We are new to eduroam and we are using FreeRadius for authentication and connection to national proxies. Just wondering what kind of reporting you have managed to get out from the FreeRadius logs, we wanted some user friendly reports with user numbers, success and failed

Re: Reporting from logs

2012-09-25 Thread Phil Mayers
On 25/09/12 14:00, Leal, Paulo wrote: Hi guys, We are new to eduroam and we are using FreeRadius for authentication and connection to national proxies. Just wondering what kind of reporting you have managed to get out from the FreeRadius logs, we wanted some user friendly reports with user

Re: Reporting from logs

2012-09-25 Thread Matthew Newton
Hi, On Tue, Sep 25, 2012 at 02:00:10PM +0100, Leal, Paulo wrote: Just wondering what kind of reporting you have managed to get out from the FreeRadius logs, we wanted some user friendly reports with user numbers, success and failed attempts, what realms were used and numbers, even possibly

Re: Reporting from logs

2012-09-25 Thread Phil Mayers
On 25/09/12 14:39, Matthew Newton wrote: The best way to go is probably SQL, but this works well and is plenty fast enough for us without having the added complexities of a database running as well. Having said that, all logs are now rad-relayed to a central RADIUS server for the web site, so I

Re: Reporting from logs

2012-09-25 Thread Matthew Newton
Hi, On Tue, Sep 25, 2012 at 03:00:26PM +0100, Phil Mayers wrote: On 25/09/12 14:39, Matthew Newton wrote: How do you relay post-auth? That's one of the main reasons we still use rlm_sql_log, as opposed to the built in detail listener. Pure total hackery. linelog can include '\n' in the

Re: Reporting from logs

2012-09-25 Thread Phil Mayers
On 25/09/12 15:34, Matthew Newton wrote: Hi, On Tue, Sep 25, 2012 at 03:00:26PM +0100, Phil Mayers wrote: On 25/09/12 14:39, Matthew Newton wrote: How do you relay post-auth? That's one of the main reasons we still use rlm_sql_log, as opposed to the built in detail listener. Pure total

Re: Reporting from logs

2012-09-25 Thread Matthew Newton
On Tue, Sep 25, 2012 at 04:28:56PM +0100, Phil Mayers wrote: On 25/09/12 15:34, Matthew Newton wrote: linelog can include '\n' in the output so can simlulate the detail module for given attributes. The relayed auth packets are sent on the wire as acct packets... You, sir, win a prize!

Re: Reporting from logs

2012-09-25 Thread Alan DeKok
Phil Mayers wrote: I almost wonder if an rlm_inject might not be generally useful; in particular, we could generate our simulated accounting internally to the radius servers, rather than via an SQL procedure: modules { inject fake_acct { See raddb/sites-available/originate-coa