[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freeradius-users
Subject:    Re: Realm accounting...
From:       Nathan Miller <nmiller_lists () visp ! net>
Date:       2001-11-29 21:29:00
[Download RAW message or body]

At 10:42 AM 11/10/2001 -0500, you wrote:
>"Chris A. Kalin" <cak@netwurx.net> wrote:
> > >   Have you looked at the configuration of the 'detail' module in
> > > 'radiusd.conf' ?
> >
> > detail {
> >                 detailfile = ${radacctdir}/%{Client-IP-Address}/detail
> >                 detailperm = 0660
> >         }
> >
> > Haven't changed it from what it was out of the box, except making 
> detailperm
> > 660 instead of 600.
>
>   Read 'doc/rlm_detail'  YOu can configure the detail directory to be
>pretty much anything you want.
>


I read this whole thread, and I think the problem Chris was originally 
trying to point out was never addressed.  I have duplicated his issue, and 
in fact, wish it worked myself.

The primary issue _not_ being where to log standard detail files, but where 
it logs proxied detail files.   The issue appears that the line in 
proxy.conf "detailfile += /path/to/detail" is being ignored.

What I notice is, when a proxy request comes in, freeradius (11/08/01 
snapshot) will successfully proxy the request and the accounting packet to 
the remote server.  Can't complain about that.  But us, being the 
wholesaler want to keep track of usage time of this proxy customer's 
usage.  And we need to do it by isp of course.  So what we need is for all 
requests being proxied to be dumped into a separate location rather than 
the location specified by "detailfile" in radiusd.conf.

I assume the difference between "+="  and just "=" on this line would mean 
the += would also log to the specified file as well as the detailfile 
specified in radiusd.conf.




[prev in list] [next in list] [prev in thread] [next in thread]