-----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. 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-----
Munroe Sollog wrote:
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.
I would suggest another solution. Syslog is meant for line-oriented log messages. The detail file is definitely *not* that.
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.
I am hoping there is a way to configure freeradius to do this so I can dismantle my hack.
If you need to move files from one machine to another, use "scp". Syslog is absolutely the wrong approach. Alan DeKok.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/12/2014 02:06 PM, Alan DeKok wrote:
Munroe Sollog wrote:
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.
I would suggest another solution. Syslog is meant for line-oriented log messages. The detail file is definitely *not* that.
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.
I am hoping there is a way to configure freeradius to do this so I can dismantle my hack.
If you need to move files from one machine to another, use "scp". Syslog is absolutely the wrong approach.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
scp is a batch process, the goal is to get the data (connecting IP, given IP, and username) into logstash (like splunkd) so that real-time analysis can be performed on the data. The linelog option seems like a resonable one. Do you know what version I would have to upgrade to in order to not have to apply the patch and rebuild? - - Munroe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBAgAGBQJTmfVUAAoJEPbbZiWCKDVC79cIAJIYB1xAq+Fjo5K0Ih29P0P1 tJm5aqJC0vmLVCrDOSQZidsiMbYUPN4PrLu2H20yVwuPz04EplNX14YnmsQdzp66 g/nc+pBQ552W+GXOLVUmtzdrs+B6rmA+6h+CuUna/oeIPLfhb8z7qZTFDk/Fv40N q5V7+YJojytfUoBDGy/kNNtAlGSdHVURjS8gk8zOSu65AgFZj+P6hYPD4WTG/ZsH qzzAHgUzckoYS0gUHIgtWW6uD7RKYqiwe+LKrYk711bWXISMAb/OuuGdrVmPsC4z 3HGVjwTgmiMa1wKmH1PsiQCiANqnOG+luB819O7TsKW3LWuTgNVPote6XOYDzM0= =kwZ/ -----END PGP SIGNATURE-----
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
On 13/06/2014 6:19 AM, "Alan DeKok" <aland@deployingradius.com> wrote:
Peter Lambrechtsen wrote:
There are a number of patches online that add syslog support to the linelog module.
Huh? The linelog module supports syslog.
Not in 2.1.12 without a patch.
Alan DeKok. - List info/subscribe/unsubscribe? See
On 12 Jun 2014, at 19:37, Peter Lambrechtsen <peter@crypt.co.nz> wrote:
On 13/06/2014 6:19 AM, "Alan DeKok" <aland@deployingradius.com> wrote:
Peter Lambrechtsen wrote:
There are a number of patches online that add syslog support to the linelog module.
Huh? The linelog module supports syslog.
Not in 2.1.12 without a patch.
and you'd rather patch 2.1.12, and presumably rebuild the packages instead of using 2.2.5 because? Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
On 13/06/2014 6:54 AM, "Arran Cudbard-Bell" <a.cudbardb@freeradius.org> wrote:
On 12 Jun 2014, at 19:37, Peter Lambrechtsen <peter@crypt.co.nz> wrote:
On 13/06/2014 6:19 AM, "Alan DeKok" <aland@deployingradius.com> wrote:
Peter Lambrechtsen wrote:
There are a number of patches online that add syslog support to the linelog module.
Huh? The linelog module supports syslog.
Not in 2.1.12 without a patch.
and you'd rather patch 2.1.12, and presumably rebuild the packages
instead of using 2.2.5 because? Because my employer somehow deems that more acceptable. Crazy I know and not what I personally would prefer to do. But RedHat seemed happy to support us if I did that. The inner working of a telcos mind and what is of a higher risk than other options never fails to surprise me.
Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS Development Team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
- List info/subscribe/unsubscribe? See
Hi,
Because my employer somehow deems that more acceptable. Crazy I know and not what I personally would prefer to do. But RedHat seemed happy to support us if I did that. The inner working of a telcos mind and what is of a higher risk than other options never fails to surprise me.
do you want the 2.1.12 -> 2.2.5 bug fix list? alan
participants (5)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Arran Cudbard-Bell -
Munroe Sollog -
Peter Lambrechtsen