Hi
A few of ous users have been complaining that they occassionaly
get access denied on login, but most of the times they go through.
I decided to log the passwords and see if they send the wrong password,
but i notice that the password field in the log files is in some funny
characters
eg,
Hi Bennie -
Most people set the trace level to 3 for normal operation.
regards
Hugh
On Tue, 9 Jul 2002 14:30, Bennie Warren wrote:
I have a question on Trace level. Should that be set to 0 in a
configuration file when all is working? Oh and yes OS X is really nice.
Bennie
On 7/8/02
Hello James -
Yes this has changed in Radiator 3.1 - I suggest you upgrade.
regards
Hugh
On Tue, 9 Jul 2002 13:21, James Wiegand wrote:
Just to clarify, because under section 6.30 RewriteUsername is not listed,
even though it is shown in section 6.45, is it legal to have a
RewriteUsername
Hello -
This looks a lot like modem noise, usually caused by modems that have not
synced properly.
regards
Hugh
On Tue, 9 Jul 2002 17:21, [EMAIL PROTECTED] wrote:
Hi
A few of ous users have been complaining that they occassionaly
get access denied on login, but most of the times they
This looks a lot like modem noise, usually caused by modems that have not
synced properly.
Well, I had a configuration whereby the NAS talks to a proxy radius server,
and based on the called_station_id, your request is sent to the appropriate
radius server.
The interesting thing is that,
if i wanted to use ClientListSQL, how would I do this?
thanks,
shon
-Original Message-
From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 08, 2002 7:27 PM
To: Shon Stephens; '[EMAIL PROTECTED]'
Subject: Re: (RADIATOR) which attribute?
Hello Shon -
You would do something
I've recently upgraded two machines to 3.0. I'm now getting the following
error sporadically:
our program
/usr/bin/radiusd -config_file /etc/radiator/radius.cfg -dictionary_file
/etc/radiator/dictionary
exited unexpectedly with exit status 0,
signal number 0 and dump indication 0.
The
On Tue, 9 Jul 2002, Brian Morris wrote:
From: Karl Gaissmaier [EMAIL PROTECTED]
you should tell us what Authentication schemes you wil be using. I think
the performance is only comparable using the same auth schemes.
We have radiator running under Solaris 9.
Charly,
I am hoping to
Hi,
I had the same problem. A new notification (mail) kept popping into my
mailbox
almost every 2 seconds. I had to turn of the restartWrapper.
I got the same problem when I tried to use the restartWrapper with BIND 9.2
on my
(same) RedHat 7.2 server.
I am interested in the solution.
Regards,
Hello Shon -
You should use a GetClientQuery in your ClientListSQL clause.
This is explained in section 6.6.2 in the Radiator 3.1 manual.
(doc/ref.html).
regards
Hugh
On Wed, 10 Jul 2002 01:32, Shon Stephens wrote:
if i wanted to use ClientListSQL, how would I do this?
thanks,
shon
Hello -
In this case the problem is probably incorrect shared secrets.
regards
Hugh
On Tue, 9 Jul 2002 21:15, [EMAIL PROTECTED] wrote:
This looks a lot like modem noise, usually caused by modems that have not
synced properly.
Well, I had a configuration whereby the NAS talks to a
Hello Leon -
There are two problems here -
the first is that the port number that radiusd is trying to open is already in
use by another program or another instance of radiusd
the second is that you have not installed the new version of Radiator
correctly and the get_port subroutine is not
Hello Tunde -
Your problem sounds like you do not have the Foreground parameter set. You
have to do this with any program restartWrapper starts, because this is how
it keeps track of the process its running. Ie. if the program exits (or
detaches in the background) restartWrapper will start a
Hugh,
I understand the problem with the ports. However I do believe I have the
correct install of Radius. Concider:
[root@nashrad01 log]# tail -n 30
/usr/lib/perl5/site_perl/5.6.0/Radius/Util.pm
}
$s =~ s/^\s*//; # Strip leading white space
}
return @ret;
}
We upgraded our accounting server from radiator 2.19, to 3.1
yesterday.
We're using it with a Cisco 3000 VPN server. Before the update the
Tunnel-Client-Endpoint appearing as in this entry:
Tunnel-Client-Endpoint = 10.243.3.57
After the upgrade it looks like this:
15 matches
Mail list logo
