RE: Mulitple radius.log files
Anson Rinesmith [EMAIL PROTECTED] wrote: I am trying to set up a scenario with an Ascend NAS. Using freeradius 0.7.0 You really should upgrade. I agree, but when I used 0.9.3 I got the sql instantiation error. I was thinking if I put a line in the files {} section of radiusd.conf, that I could make a separate radius.log file based on what realm I proxied to or Called-Station-ID. The server does not support that. I don't know why you would think that the radiusd.log file is configured in the files module. Where is it configured? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Mulitple radius.log files
Anson Rinesmith [EMAIL PROTECTED] wrote: I am trying to set up a scenario with an Ascend NAS. Using freeradius 0.7.0 You really should upgrade. I was thinking if I put a line in the files {} section of radiusd.conf, that I could make a separate radius.log file based on what realm I proxied to or Called-Station-ID. The server does not support that. I don't know why you would think that the radiusd.log file is configured in the files module. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Mulitple radius.log files
I am trying to set up a scenario with an Ascend NAS. Using freeradius 0.7.0 as a proxy on FreeBSD 5.2, I can successfully test authentication with ntradping. I use the users file to do proxying based on Called-Station-ID, sending different dialed numbers to different radius servers. I am getting Auth: Login OK and Auth: Login incorrect messages to my radius.log file. I was thinking if I put a line in the files {} section of radiusd.conf, that I could make a separate radius.log file based on what realm I proxied to or Called-Station-ID. Ive done some trial and error, but nothing works. Am I on the right track? Where would I put such a command, or am I just missing what I should change? logdir = ${localstatedir}//%{Called-Station-ID}/radius.log is the most logical think Ive tried. Anson Rinesmith
RE: Mulitple radius.log files
Okay, did my cut/paste botch that The most logical thing Ive tried was in files { logdir = ${localstatedir}/log/radius/%{Called-Station-Id} } Something similar to whats in detail {} where the detail file goes in a directory based on the Client-IP-Address -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Anson Rinesmith Sent: Friday, January 16, 2004 3:30 PM To: [EMAIL PROTECTED] Subject: Mulitple radius.log files I am trying to set up a scenario with an Ascend NAS. Using freeradius 0.7.0 as a proxy on FreeBSD 5.2, I can successfully test authentication with ntradping. I use the users file to do proxying based on Called-Station-ID, sending different dialed numbers to different radius servers. I am getting Auth: Login OK and Auth: Login incorrect messages to my radius.log file. I was thinking if I put a line in the files {} section of radiusd.conf, that I could make a separate radius.log file based on what realm I proxied to or Called-Station-ID. Ive done some trial and error, but nothing works. Am I on the right track? Where would I put such a command, or am I just missing what I should change? logdir = ${localstatedir}//%{Called-Station-ID}/radius.log is the most logical think Ive tried. Anson Rinesmith