On Mon, Jun 04, 2012 at 10:02:01AM -0400, Luo, Frank Y.F. Mr. wrote:
Also about the username, you are right on the Mac address - I
misread it - but I do see unreadable accounting log like this
one in the packet. Is this something fixable at NAS?
Nothing looks wrong with the packet below.
thanks. will do some research. But I guess I can not send this as syslog entry
to a syslog server, right?
Also about the username, you are right on the Mac address - I misread it - but
I do see unreadable accounting log like this one in the packet. Is this
something fixable at NAS?
Frank
On 06/04/2012 04:02 PM, Luo, Frank Y.F. Mr. wrote:
thanks. will do some research. But I guess I can not send this as syslog entry
to a syslog server, right?
yes, you can - just configure linelog to send the wanted variables to
syslog..
--
Jens Weibler
IT-Services
Hochschule Darmstadt
oops, yes it is described in the config file - thanks anyway
On Jun 4, 2012, at 10:10 AM, Jens Weibler wrote:
On 06/04/2012 04:02 PM, Luo, Frank Y.F. Mr. wrote:
thanks. will do some research. But I guess I can not send this as syslog
entry to a syslog server, right?
yes, you can - just
Is there a way to send accounting log to syslog instead of detail file in
radacct?
Also instead of sending it to sql db, i tried to use sql-file but it results in
a lot of sql command (we really don't want to run the sql command later).
INSERT INTO radacct (AcctSessionId, UserName
On 30/05/12 18:00, Luo, Frank Y.F. Mr. wrote:
Is there a way to send accounting log to syslog instead of detail
file in radacct?
See linelog
Also instead of sending it to sql db, i tried to use sql-file but it
results in a lot of sql command (we really don't want to run the sql
command
Um. Ignore this. Wrong list :-(
On 22/03/2012 09:51, Traiano Welcome traiano.welc...@mtnbusiness.co.za
wrote:
Hi List
I've been seeing the following in the messages log of my freebsd syslog
server for quite some time now:
---
Mar 20 12:19:12 syslog2 syslog-ng[35313]: I/O error occurred while
Hi Matthew Newton,
Thank you very much for quick response!
The problem is solved by patching the rlm_linelog. Now everything is fine!
--
View this message in context:
http://freeradius.1045715.n5.nabble.com/Eduroam-F-ticks-and-syslog-tp5457972p5459564.html
Sent from the FreeRadius - User
Hi,
On Sun, Feb 05, 2012 at 06:31:02PM +0400, Andranik Hayrapetyan wrote:
It sends f-ticks to syslog, and syslog place f-ticks in /var/log/massage
withe many other log information.
How can I set here facility for syslog (local0 eg.) , to be able to control
the f-ticks and place them
Hello.
I am running 2.1.10. Is it possible to log to files and syslog (both)?
Regards
Mika
--
View this message in context:
http://freeradius.1045715.n5.nabble.com/Logging-to-destination-files-AND-syslog-tp5010771p5010771.html
Sent from the FreeRadius - User mailing list archive at Nabble.com
Mika wrote:
Hello.
I am running 2.1.10. Is it possible to log to files and syslog (both)?
No. Use something like rsyslog to send logs to multiple destinations.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
I have a requirement to get successful and failed radius
authentication logs from FreeRADIUS to a SIEM for audit purposes. I
have updated the config to log to syslog, but I need more information
than is currently appearing.
Example:
Sep 29 10:40:56 radiusserver radiusd[13806]: Login incorrect
On 29 Sep 2011, at 18:51, Tremaine Lea wrote:
I have a requirement to get successful and failed radius
authentication logs from FreeRADIUS to a SIEM for audit purposes. I
have updated the config to log to syslog, but I need more information
than is currently appearing.
Example:
Sep 29
, Tremaine Lea wrote:
I have a requirement to get successful and failed radius
authentication logs from FreeRADIUS to a SIEM for audit purposes. I
have updated the config to log to syslog, but I need more information
than is currently appearing.
Example:
Sep 29 10:40:56 radiusserver radiusd[13806
El 23/05/11 14:30, Alan DeKok escribió:
Angel L. Mateo wrote:
...
reference = %{%{Packet-Type}:-format}
Which is *always* the request packet. Use %{reply:Packet-Type} for
the reply.
You'll have to find a way to switch the reference based on request or
reply. Maybe configure
Hello,
I'm trying to configure my freeradius server (version 2.1.8 running in
a ubuntu 10.04 server) to log access request results to syslog. My
configuration is:
authorize {
...
sistemas_syslog
...
}
accounting {
...
sistemas_syslog
Angel L. Mateo wrote:
...
reference = %{%{Packet-Type}:-format}
Which is *always* the request packet. Use %{reply:Packet-Type} for
the reply.
You'll have to find a way to switch the reference based on request or
reply. Maybe configure two versions of the linelog module.
Alan
Alan DeKok al...@deployingradius.com wrote:
are there any plans to add logging to *remote* syslog servers to the
rlm_linelog module? Would be kinda cute; we want to log authentication
results to a central statistics collection host - and going through
re-send on the local syslog instance
Hi,
are there any plans to add logging to *remote* syslog servers to the
rlm_linelog module? Would be kinda cute; we want to log authentication
results to a central statistics collection host - and going through
re-send on the local syslog instance is a superfluous extra step.
Greetings,
Stefan
Stefan Winter wrote:
are there any plans to add logging to *remote* syslog servers to the
rlm_linelog module? Would be kinda cute; we want to log authentication
results to a central statistics collection host - and going through
re-send on the local syslog instance is a superfluous extra step
On 08/25/2010 09:51 PM, mack ragan wrote:
Hi,
I have freeradius v2.0.5. I modified the log{} section of radiusd.conf
to send logs to syslog-ng. In syslog-ng, I filter them out to a log
collector. This seems to be working well. Now, I would like to get
detail and auth to the log collector
mack ragan wrote:
Hi,
I have freeradius v2.0.5. I modified the log{} section of radiusd.conf
to send logs to syslog-ng. In syslog-ng, I filter them out to a log
collector. This seems to be working well. Now, I would like to get
detail and auth to the log collector. Anyone know
Thanks for the replies. I was afraid that the format of detail wouldn't
allow syslog. I suppose detail can be sent to mysql though, right?
Is it possible within the radius log, where it logs successful or failed
logins, to also include the client's IP address along with the MAC?
On Thu, Aug
gtcoldfire wrote:
Thanks for the replies. I was afraid that the format of detail wouldn't
allow syslog. I suppose detail can be sent to mysql though, right?
No.
Is it possible within the radius log, where it logs successful or failed
logins, to also include the client's IP address along
Hi,
Thanks for the replies. I was afraid that the format of detail wouldn't
allow syslog. I suppose detail can be sent to mysql though, right?
No.
unless, eg using the buffered-sql virtual server. in which case detail
files can go to SQL
Is it possible within the radius log, where
Alan Buxey wrote:
unless, eg using the buffered-sql virtual server. in which case detail
files can go to SQL
Well, no. Accounting can go to SQL. But that doesn't mean writing
the detail files to SQL. And it doesn't need the buffered-sql virtual
server.
Alan DeKok.
-
List
Hi,
I have freeradius v2.0.5. I modified the log{} section of radiusd.conf to
send logs to syslog-ng. In syslog-ng, I filter them out to a log
collector. This seems to be working well. Now, I would like to get detail
and auth to the log collector. Anyone know if this is possible?
Thanks
Further to my previous query I've got global server messages being
syslogged to my log hosts.
However, all of my radius magic happens inside virtual servers, which
live in sites-available. I haven't been able to get any syslog packets
sent from within these virtual servers.
I've tried
Jonathan Gazeley wrote:
However, all of my radius magic happens inside virtual servers, which
live in sites-available. I haven't been able to get any syslog packets
sent from within these virtual servers.
The log section is global. See raddb/sites-available/README for a
definitive list
On 07/06/2009 04:35 PM, Alan DeKok wrote:
Jonathan Gazeley wrote:
However, all of my radius magic happens inside virtual servers, which
live in sites-available. I haven't been able to get any syslog packets
sent from within these virtual servers.
The log section is global. See
the
server to not start:
no, the log section is global - and therefore cannot go into
a virtual server - it fails if you do that (as you've seen)
Ultimately what I'm after is the ability to send detail logs to syslog
rather than have them written to a file. Perhaps I've been asking the
wrong
On 07/06/2009 05:02 PM, a.l.m.bu...@lboro.ac.uk wrote:
Ultimately what I'm after is the ability to send detail logs to syslog
rather than have them written to a file. Perhaps I've been asking the
wrong questions so far, or in the wrong way :)
whoa. thats completely different to what
-users-bounces+ted.behling=htc.hargray@lists.freer
adius.org] On Behalf Of Jonathan Gazeley
Sent: Monday, July 06, 2009 12:15 PM
To: FreeRadius users mailing list
Subject: Re: Syslog and FreeRADIUS
On 07/06/2009 05:02 PM, a.l.m.bu...@lboro.ac.uk wrote:
Ultimately what I'm
@lists.freeradius.org
[mailto:freeradius-users-bounces+ted.behling=htc.hargray@lists.freeradius.org]
*On Behalf Of *Jonathan Gazeley
*Sent:* Monday, July 06, 2009 12:15 PM
*To:* FreeRadius users mailing list
*Subject:* Re: Syslog and FreeRADIUS
On 07/06/2009 05:02 PM, a.l.m.bu...@lboro.ac.uk wrote
that i dont know why you'd want to cripple your config by relying on syslog
and such dumb technologies for transfer of such details.
FoE, FC, ATAoE, NFSv4, iSCSI etc
however, ANOTHER way would be to have a backend RADIUS server that sites
on a system with the big fat disksthis RADIUS server would
Jonathan Gazeley wrote:
For a start I want to syslog the stuff that usually goes into radius.log
- so the messages when the server starts (which are already being
syslogged successfully) and the summary line (Auth: Login OK) printed
after an authentication (which are currently not being sent
Hi all,
I've decided to move logging on my radius boxes to a pair of syslog
servers, rather than stored locally. I'm using rsyslog to send the logs
over the network.
I follow this guide http://wiki.freeradius.org/Syslog_HOWTO but it seems
to be for an old version of FreeRADIUS. I have
Jonathan Gazeley wrote:
I've decided to move logging on my radius boxes to a pair of syslog
servers, rather than stored locally. I'm using rsyslog to send the logs
over the network.
It's a good tool.
I follow this guide http://wiki.freeradius.org/Syslog_HOWTO but it seems
to be for an old
Hi,
OK - so I'm using an proxy setup and need better logging.
Sample messages
Jun 23 13:54:59 localhost radiusd[23703]: Login OK: [rmayberr] (from
client 0.0.0.0/0 port 1812)
Assuming that 0.0.0.0/0 is coming from the clients file. Adding individual
clients isn't an option.
I want this
OK - so I'm using an proxy setup and need better logging.
Sample messages
Jun 23 13:54:59 localhost radiusd[23703]: Login OK: [rmayberr] (from
client 0.0.0.0/0 port 1812)
Assuming that 0.0.0.0/0 is coming from the clients file. Adding individual
clients isn't an option.
I want this log to
JR Mayberry wrote:
Ideas how to get this accomplished?
Edit the source code to make the log message configurable.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hello, I re-open that old (05.09.2008) thread ...
I still really need to log radiusd in order to debug a timeout problem
in our eduroam infrastructure.
the problem is that radiusd is in production and runing it with -X is
too verbious
I want to log though syslog or direct log files some
hi,
why not use the raddebug functionality so you can debug the live server
when you want
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
a.l.m.bu...@lboro.ac.uk a écrit :
hi,
why not use the raddebug functionality so you can debug the live server
when you want
alan
good advice, don't know that tools but it seems interesting
however I'am not sure it is available in my version ?
freeradius-2.0.3-3.el5
how can I check, where
Hi,
good advice, don't know that tools but it seems interesting
however I'am not sure it is available in my version ?
freeradius-2.0.3-3.el5
how can I check, where to find a doc ?
no. not available - you need to run 2.1.4 for these new features
alan
-
List info/subscribe/unsubscribe? See
(05.09.2008) thread ...
I still really need to log radiusd in order to debug a timeout problem
in our eduroam infrastructure.
the problem is that radiusd is in production and runing it with -X is
too verbious
I want to log though syslog or direct log files some of the radiusd -X
informations
Hello,
Running FreeRadius 2.0.5, with the following log related config:
logdir = syslog
log {
log_destination = syslog
syslog_facility = local7
stripped_names = no
auth = yes
auth_badpass = no
auth_goodpass = no
}
I've found lots of conflicting
Phillip Heller wrote:
I've found lots of conflicting info among the wiki, documentation, and
list suggesting different statements (log_destination=, destination=),
and perhaps outside of log{}.
The configuration files contain the most up-to-date description of the
configuration.
I did look
hello
I can run debug log by starting radiusd -X , but for production, I want
logs to go to a file and not stdout .
When I start radiusd without -X I only get very few logs, how can I have
equivalent to -X log with syslog or a log file ?
or a least get more log the the very few ones I get
I can run debug log by starting radiusd -X , but for production, I want
logs to go to a file and not stdout .
http://linuxbasics.org/course/book/chap_05
for now with that config I only get 2 lines in radiusd.log when I log in
802.X EAP-ttls , telling:
Sep 5 10:42:30 radiustux radiusd[14619]:
and what I want: the
Username, the ldap servers used to autheticate him (we have 3
directories depending on the @domain ), the IP adresse assigned and the
vlan assigned .
from the -X I found these kind of logs which are relevant to me, how can
I get them in syslog or logfile or linelog
and the
vlan assigned .
from the -X I found these kind of logs which are relevant to me, how can
I get them in syslog or logfile or linelog ?
rad_check_password: Found Auth-Type EAP
rlm_ldap: performing user authorization for procacci
lm_ldap: (re)connect to ldap1.int-evry.fr:389, authentication 0
I'm unsure here why syslog would be a bad idea in the case of FreeRADIUS.
However, there is also another option, the SQL logging options... Perhaps
those may be handy as well?
//anders
On 30/07/2008 13:39, Alan DeKok [EMAIL PROTECTED] wrote:
Mustapha Bouikhif wrote:
I want to send acct logs
Anders Holm wrote:
I'm unsure here why syslog would be a bad idea in the case of FreeRADIUS.
syslog is generally for one-line log messages. Not for gigabytes of
traffic. Accounting logs generate gigabytes of traffic, and do not need
the overhead of syslog.
However, there is also another
Mustapha Bouikhif wrote:
Is there a simple way to send accounting logs (of FR 2.0.5) to syslog ?
I mean the various detail files: auth_log, reply_log,
pre||post_proxy_log ...
You REALLY don't want to do that. It's a very bad idea.
It is possible to append them to radius.log (who can
Alan DeKok a écrit :
Mustapha Bouikhif wrote:
Is there a simple way to send accounting logs (of FR 2.0.5) to syslog ?
I mean the various detail files: auth_log, reply_log,
pre||post_proxy_log ...
You REALLY don't want to do that. It's a very bad idea.
It is possible to append
syslog.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi folks,
Is there a simple way to send accounting logs (of FR 2.0.5) to syslog ?
I mean the various detail files: auth_log, reply_log,
pre||post_proxy_log ...
It is possible to append them to radius.log (who can be maintained by
syslog) but i think is a bad idea.
thanks for any clues
Stuart Kendrick wrote:
Starting RADIUS server: radiusd: Error: Unknown syslog chosen but no
facility spedified
Grab a CVS checkout, it should be fixed.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
hi,
i'm installing freeradius-2.0.0 and seeing the following when i try to start
radiusd:
Starting RADIUS server: radiusd: Error: Unknown syslog chosen but no facility
spedified
relevant lines from radiusd.conf:
logdir = ${localstatedir}/log/radius
log_destination = syslog
log
[EMAIL PROTECTED] wrote:
I've upgraded to FreeRADIUS Version 1.1.7 now and logging seems to be
working but I'd like to be able to get more usable data.
I nthe /etc/syslog.conf file I have this entry:
...
From the syslog server I see this data:
Oct 17 19:11:16 radius radiusd(pam_unix)[15776
[EMAIL PROTECTED] wrote:
I'm running freeradius 1.0.1
Why? Upgrade. Now.
on CentOS 4.4 and I'm trying to get the
radius to log to a syslog server. I followed the example Syslog_HOWTO
but its not working. I was hoping that someone else might know the
answer / fix.
Upgrade.
Alan
log file
local1.*/var/log/radius/radius.log
From the syslog server I see this data:
Oct 17 19:11:16 radius radiusd(pam_unix)[15776]: authentication
failure; logname= uid=95 euid=95 tty= ruser= rhost=
Oct 17 19:12:06 radius radiusd(pam_unix)[15776]: authentication
Hi all,
I'm running freeradius 1.0.1 on CentOS 4.4 and I'm trying to get the
radius to log to a syslog server. I followed the example
Syslog_HOWTO but its not working. I was hoping that someone else
might know the answer / fix.
Thanks in Advance,
-
List info/subscribe/unsubscribe? See
Andreas Wetzel wrote:
I installed freeRadius 1.1.6 on a FreeBSD 6.2-RELEASE system from the ports
collection, and am trying to get it to log via syslog. I followed the
instructions from the wiki for configuring radiusd to use syslog, but when
radiusd starts, I get the following:
1.1.6
Jay Banks wrote:
Here is the same problem, found in the archives for this list, which was
posted back in January of 2004:
BUG?? Couldn't open syslog/radius.log for logging: Not a directory
Problem Summary: radiusd: radiusd: Couldn't open syslog/radius.log for
logging: Not a directory
Hi
I installed freeRadius 1.1.6 on a FreeBSD 6.2-RELEASE system from the ports
collection, and am trying to get it to log via syslog. I followed the
instructions from the wiki for configuring radiusd to use syslog, but when
radiusd starts, I get the following:
# radiusd -f -l syslog
Sun Jul 1
# radiusd -f -l syslog
Sun Jul 1 10:40:09 2007 : Info: Starting - reading configuration files
...
radiusd: Couldn't open syslog/radius.log for logging: Permission denied
(rlm_eap_tls: Loading the certificate file as a chain)
radiusd: Couldn't open syslog/radius.log for logging
Jay Banks wrote:
# radiusd -f -l syslog
Sun Jul 1 10:40:09 2007 : Info: Starting - reading configuration files
...
radiusd: Couldn't open syslog/radius.log for logging: Permission denied
(rlm_eap_tls: Loading the certificate file as a chain)
radiusd: Couldn't open syslog/radius.log
set to
RADLOG_SYSLOG in src/main/radiusd.c. After radlog_dest has been set up
there,
no more such error messages appear, and log goes correctly to syslog as it
should.
Andreas
Yes, I think you are right. I did some research and see other people have
had the same problem.
Here is the same
Perhaps this might help -- Jay-=-=-=-=-=Didn't know freeradius did syslog,
cool. Anyway, just tried it out on
freebsd 5.4. In man radiusd, it shows that when using -l syslog, there is
also -g to specify the facility, where it also shows the default is
daemon.
You will need to edit /etc
Hello,
I want to log all the freeradius (v 1.1.3) logs to syslog (syslog-ng).
I 've already added this to my syslog-ng.conf :
filter f_radiusd { match (radiusd); };
destination radiuslogs { file(var/log/radiusd.log); };
log { source (src); filter(f_daemon); filter(f_radiusd);
destination
Hi Mark,
Wednesday, May 23, 2007, 2:47:10 PM, you wrote:
logdir = syslog
[...]
rlm_detail: Failed to create directory syslog/radacct: No such file or
directory
LOGDIR means... log dir :
regards,
Claudiu Filip
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list
Claudiu,
I know what logdir means :)
But according to the Syslog_Howto from the wiki,
http://wiki.freeradius.org/Syslog_HOWTO :
Modify /etc/raddb/radiusd.conf:
logdir = syslog
log_destination = syslog
Because of the logdir entry above, you must locate all references to
${logdir}, comment
Hi Mark,
it seems that you forgot a line with
radacctdir = ${logdir}/radacct
if you have no line with radacctdir, then add one with the correct
path.
best regards,
Claudiu Filip
@: [EMAIL PROTECTED]
Http://www.globtel.ro
T:+40344880100
F:+40344880113
-
List
Claudiu,
I've got that line in my config, with the exact same path..
Grtz,
Mark
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Mon 02 Apr 2007, Archie Holland wrote:
I'm preparing to transition from NavisRadius to FreeRadius. NavisRadius
allowed me to log stop/start events via syslog. Is there any _EASY_ way
to emulate this behavior in FreeRadius?
rlm_acctlog in cvs head...
--
Peter Nixon
http
I'm preparing to transition from NavisRadius to FreeRadius. NavisRadius
allowed me to log stop/start events via syslog. Is there any _EASY_ way to
emulate this behavior in FreeRadius?
--
= The Net That Works!
Archie Hollandhttp
Archie Holland wrote:
I'm preparing to transition from NavisRadius to FreeRadius.
NavisRadius allowed me to log stop/start events via syslog.
Is there any _EASY_ way to emulate this behavior in FreeRadius?
Run a Perl script, and have it write to syslog.
There is a syslog module
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hey,
we start the radiusd in debugging mode and with the following line in
rc.local we now just get the loggin attempts into the radius.log:
tail -f /var/log/radius/radius_complete.log | grep --line-buffered \:\
Login /var/log/radius/radius.log
hey @all,
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
We start radiusd with daemontools and with these parameters:
loggeropt=logger -p local6.info -t radiusd -s
ARGS=-Afxyz
Michael Messner [EMAIL PROTECTED] wrote:
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
Because it's in debugging mode. Output goes to STDOUT, and not to
radius.log.
any
tail -F radius.log | logger
- Original Message -
From: Michael Messner [EMAIL PROTECTED]
To: freeradius-users@lists.freeradius.org
Sent: Thursday, November 16, 2006 3:10 PM
Subject: logging to normal radius.log and syslog
hey @all,
for testing we write the complete debugging
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alan DeKok schrieb:
Michael Messner [EMAIL PROTECTED] wrote:
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
Because it's
: logging to normal radius.log and syslog
hey @all,
for testing we write the complete debugging messages to syslog into a
special file but with this method the loggin to the normal radius.log
file won't work anymore!
We start radiusd with daemontools and with these parameters:
loggeropt
Michael Messner [EMAIL PROTECTED] wrote:
Because it's in debugging mode. Output goes to STDOUT, and not to
radius.log.
sure, we need the possibility to analyze the files
Then why are you running the server in debugging mode, with output
goind to STDOUT?
I think this would be very
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hey,
Michael Messner wrote:
Kevin Bonner wrote:
I don't believe it was added to the 1.1.X branch, so the CVS head and
nightly
snapshots are the only way to use the syslog logging method. Wait for 2.0
or
try one of the other suggestions
hey kenneth,
Kenneth Grady wrote:
try ...
log_destination = syslog
log {
syslog_facility = daemon
}
not working :-(
mIke
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Thursday 05 October 2006 08:07, Michael Messner wrote:
hey kenneth,
Kenneth Grady wrote:
try ...
log_destination = syslog
log {
syslog_facility = daemon
}
not working :-(
mIke
I don't believe it was added to the 1.1.X branch, so the CVS head and nightly
snapshots
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hey Kevin,
Kevin Bonner wrote:
On Thursday 05 October 2006 08:07, Michael Messner wrote:
hey kenneth,
Kenneth Grady wrote:
try ...
log_destination = syslog
log {
syslog_facility = daemon
}
not working :-(
mIke
I don't believe
hey freeRADIUS users,
I'm trying to syslog the radius-messages with freeradius 1.1.2!
Now I've added the line
log_destination = files
to the radiusd.conf, and I also tried to start the radius with the
parameter -lsyslog but nothing goes to syslog!
Any ideas?!?
thanks mIke
-
List info
Michael Messner [EMAIL PROTECTED] wrote:
to the radiusd.conf, and I also tried to start the radius with the
parameter -lsyslog but nothing goes to syslog!
That doesn't really work in 1.1.x
Alan DeKok.
--
http://deployingradius.com - The web site of the book
http
hey alan,
Alan DeKok wrote:
Michael Messner [EMAIL PROTECTED] wrote:
to the radiusd.conf, and I also tried to start the radius with the
parameter -lsyslog but nothing goes to syslog!
That doesn't really work in 1.1.x
any workarounds available?
thanks mIke
-
List info/subscribe
On Wednesday 04 October 2006 12:27, Michael Messner wrote:
hey alan,
Alan DeKok wrote:
Michael Messner [EMAIL PROTECTED] wrote:
to the radiusd.conf, and I also tried to start the radius with the
parameter -lsyslog but nothing goes to syslog!
That doesn't really work in 1.1.x
any
try ...
log_destination = syslog
log {
syslog_facility = daemon
}
Michael Messner wrote:
hey freeRADIUS users,
I'm trying to syslog the radius-messages with freeradius 1.1.2!
Now I've added the line
log_destination = files
to the radiusd.conf, and I also tried to start
or -x log to the logfile?
I have toyed with setting logdir to 'syslog' in the radiusd.conf file.Alan said in a note to the list on Sept 6 that this feature didn't work in 1.1.3, but would in 2.0I find it actually works pretty well IF you use the -x -xx or -X flag. The output that usually goes
Lin Richardson [EMAIL PROTECTED] wrote:
Is there any way to squish the user password in the -xx output? Are there
any hidden/undocumented setting for radiusd.conf that do that?
Run a shell script to root through the output nuke the passwords.
Or, hack the code locally.
You'll see that
Is there any way to
squish the user password in the -xx output? Are there any
hidden/undocumented setting for radiusd.conf that do that?
radiusd -Xx |
sed -e s/\([pP]\)assword.*/\1assword masked/
This is a
tweak from something Alan suggested to me It gets rid of most of the
passwords
fvt3 [EMAIL PROTECTED] wrote:
Can we send radius log to a syslog? If so, how can I
accomplish this. I am using the latest freeradius
version..
It doesn't really work in 1.1.3. It will work in 2.0
Alan DeKok.
--
http://deployingradius.com - The web site of the book
http
Can we send radius log to a syslog? If so, how can I
accomplish this. I am using the latest freeradius
version..
I try changing logdir=syslog but not successful...
Thanks in advance..
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best
1 - 100 of 143 matches
Mail list logo
