On Sat, 23 Aug 2008 07:04:11 +0200
Alan DeKok [EMAIL PROTECTED] wrote:
Aaron Spanik wrote:
*snip*
I suggest getting access. Sorry... but it's the simplest way to debug
things when something is going wrong.
Always. But sometimes one is forced to prove something is wrong before
the
Aaron Spanik wrote:
As you no doubt know, once I used
%{proxy-request:Packet-Dst-Ip-Address} I started seeing exactly what I
wanted to see in my logs.
Yup.
That sounds excellent; I will check out the GIT version. Can you
comment on how long it is likely to take before those features make
I apologize in advance if this question is answered in the
documentation, but if it is, I haven't been able to find it.
I have the following setup:
- Client daemon running on host A
- FreeRADIUS 2.0.4 server running on host A proxying auth requests
- Two Remote RADIUS servers serving
Aaron Spanik wrote:
Recently, however, there has been reason to suspect that the two remote
RADIUS servers are behaving inconsistently with each other (i.e. auth
fails on one and then immediately succeeds on the other).
Unfortunately, I have zero access to the remote RADIUS servers and
Hi Folks,
You'll probably think this question is a bit nuts.
With FreeRadius 1.01 on FreeBSD 5.3, is there any way of logging all
authentication requests to radius.log EXCEPT requests from a particular
username?
Or alternatively, log all authentication requests EXCEPT those from a
Lisa Casey [EMAIL PROTECTED] wrote:
With FreeRadius 1.01 on FreeBSD 5.3, is there any way of logging all
authentication requests to radius.log EXCEPT requests from a particular
username?
Or alternatively, log all authentication requests EXCEPT those from a
particular client (this would
Anders Karlsson [EMAIL PROTECTED] wrote:
I'm wondering if there's a way to log all the error logs ( like failed
logins and so on ) into a mysql table instead of the standard radius
logfile ?
Not at this time.
As always, patches are welcome.
Alan DeKok.
-
List
7 matches
Mail list logo
