And I actually tend to think that there's something more here than just
paying attention to the detailfile directive - since I don't see a Realm
attribute in the detail file for the users that are using a realm (if there
was no realm on the username I DO see 'Realm = NULL') and I don't get any
realm entries in the MySQL database either, even though there's a field for
them. (Instead, the realm is appended to the username in the User Name
field.) It's almost like the proxy module figures out there's a realm,
proxies the request properly, than promptly forgets that it was dealing with
a realm and logs (to detail, SQL, or both) just like it was a regular
username.
Chris Kalin
- Original Message -
From: Nathan Miller [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 05, 2001 11:47 AM
Subject: Realm Accounting (bump)
I hate to bring it up again; however, the last message never received a
response and this issue does seem to be an issue which has been reported
quite a few times in the past, and never recieved a valid response or fix
as yet to date.
Please see message dated: 11/29/01 Re: Realm accounting...
- copy of message
At 10:42 AM 11/10/2001 -0500, you wrote:
Chris A. Kalin [EMAIL PROTECTED] 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.
end copy
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
