On Sat 03 Feb 2007 23:57, John Brittain wrote:
radrelay copies accounting packets, not authentication packets. In
FreeRADIUS, the Login OK message appears in radius.log
ONLY when the
server sends an Access-Accept.
In any case, the radius.log file is informative, not
radrelay copies accounting packets, not authentication packets. In
FreeRADIUS, the Login OK message appears in radius.log
ONLY when the
server sends an Access-Accept.
In any case, the radius.log file is informative, not
definitive. If
you're using it for any purpose other
John Brittain wrote:
It's being used for incorrect logins and other information, and we had a
web page that pierced that file when a customer called with a problem.
Now, we have to look at both files to see the errors/information.
Having a web server parse (or even have read access to) the
Hello All!
FR Version: 1.1.3
OS Version: Fedora Core 5
cmd line for radrelay = /usr/bin/radrelay -n rad1_server -a
/var/log/radacct -d /etc/raddb detail.relay
We've recently switched to FreeRadius from Cistron, and we didn't have
this problem with Cistron. So, I'm hoping someone can help.
We
John Brittain wrote:
We are running 2 servers with radrelay. When a user gets authenticated
on server #1, it logs their Login OK in the radius.log file, but does
NOT log it on server #2 (and vise versa). So I would like to know if
there's a way to have the log files on both servers sync up?
5 matches
Mail list logo
