syslog detail accounting
peter at crypt.co.nz
Thu Jun 12 20:14:34 CEST 2014
On 13/06/2014 4:47 AM, "Munroe Sollog" <mus3 at 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/
> -----END PGP SIGNATURE-----
> List info/subscribe/unsubscribe? See
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Freeradius-Users