On 13/06/2014 4:47 AM, "Munroe Sollog" <mus3@lehigh.edu> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I currently have freeradius 2.1.12 on a cent6 system. It is only being
used to collect accounting
data for a VPN. The RADIUS auth is happening somewhere else. The detail logs are currently being stored in /var/log/radius/radacct/<client IP>/detail-<daily-file>. However, while radius itself is logging to syslog, this detail file is not using syslog. My ultimate goal is to be able to forward all of these detail accounting logs to a central syslog server for analysis. My current solution is I have a daemon that watches all of the files, slurps it up and re-emits it as syslog data to an rsyslog server.
There are a number of patches online that add syslog support to the linelog module. That's what we run on 2.1.12 for our usage logging and it works well (apart from when the syslog server falls over which can be a pain). Google for them. They aren't hard to find.
I am hoping there is a way to configure freeradius to do this so I can
dismantle my hack.
- - Munroe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQEcBAEBAgAGBQJTmdlmAAoJEPbbZiWCKDVCT88IAOzyHdS4wh1I4dsTAhCA+2e6 +Uty2U67YK3qRB3ZZ5MyZsmh1btIdwY9FqrbvHZJJrurMaekgI9sLaCwulbpfQC9 /TcJx7UqfWOSs+bJwk45sKOtB/DW9oC6KiBdaNXJzRPxg1KycptfEk25l+Qku84e sPEkH7lc4Agop7xdhEfftzPDnuDAulwIPCJcDKHl9jrKA76wgd+JTkH5CIZxLYH0 ow4teLwqozIRbD/BD3bFgrbK5y2w1jGMkBxKs1uf9M1p1gKbaYEL71ZUSBWF/2nx FmF6c2IMh2THYvKy4jK2BMWAp8e/r2Xc6KtmSAevQdSAMDNkH2CDIa5WsWbiuhs= =py0p -----END PGP SIGNATURE----- - List info/subscribe/unsubscribe? See