Noted, thanks in advance.
-Danny
On Fri, Mar 1, 2013 at 11:04 PM, Arran Cudbard-Bell
a.cudba...@freeradius.org wrote:
Or are you talking about failing over between upstream proxy servers?
Does this mean a setup of Radius load balancing? I mean a few Radius
server that used by the same
Or are you talking about failing over between upstream proxy servers?
Does this mean a setup of Radius load balancing? I mean a few Radius server
that used by the same AP ? So from AP point of view i just need to point to
the master Ip address of the first radius server?
No. That's
Hi All,
Let say for example in our Wireless AP (access point) we can put 2 Radius
server in sequence, radiusA and radiusB. I know the AP will eventually look
at the 1st server, and if its not available (let say server is down) then
it will go to the 2nd radius server (I only assume this).
So is
Let say for example in our Wireless AP (access point) we can put 2 Radius
server in sequence, radiusA and radiusB. I know the AP will eventually look
at the 1st server, and if its not available (let say server is down) then it
will go to the 2nd radius server (I only assume this).
So
Hello,
This is what i want to do :
You're asking whether you can configure FreeRADIUS to inform the access
point that it should fail over to another server server after a given
number of timeouts/retries?
Thanks
Danny
--
Best Regards,
Danny
-
List info/subscribe/unsubscribe? See
Out of topic : All, btw how can i make sure that when i reply in this
mailing list it appears after the previous post ? I dont receieve any of
your reply in my email and i have to go to the archive list to reply this.
Thanks
--
Best Regards,
Danny
-
List info/subscribe/unsubscribe? See
On 1 Mar 2013, at 00:20, Danny Kurniawan danny.kurnia...@fairchildsemi.com
wrote:
Out of topic : All, btw how can i make sure that when i reply in this mailing
list it appears after the previous post ? I dont receieve any of your reply
in my email and i have to go to the archive list to
No worries, i receive this mailing list on my email now..
OK, so i also understand that we can only configure that from the AP side.
But unfortunately we cant find that in the Meraki AP ... let me check with
our vendor on it.
Thanks
Danny
On Fri, Mar 1, 2013 at 2:26 PM, Arran Cudbard-Bell
Arran,
* Let say for example in our Wireless AP (access point) we can put 2 Radius
server in sequence, radiusA and radiusB. I know the AP will eventually look at
the 1st server, and if its not available (let say server is down) then it will
go to the 2nd radius server (I only assume this). **
it in
production, but can confuse in case of a radius failure. When an
authentication failure happens, on the nas it appears that the radius
server is not responding, it shows a Radius timeout message, here is
the output of the radius debug:
The timeouts on the NAS are set WAY
, but
can confuse in case of a radius failure. When an authentication failure
happens, on the nas it appears that the radius server is not responding, it
shows a Radius timeout message, here is the output of the radius debug:
rad_recv: Access-Request packet from host 192.168.2.100 port 35710, id
disable me to put it in
production, but can confuse in case of a radius failure. When an
authentication failure happens, on the nas it appears that the radius
server is not responding, it shows a Radius timeout message, here is
the output of the radius debug:
The timeouts on the NAS are set WAY too
a Radius timeout message, here is
the output of the radius debug:
The timeouts on the NAS are set WAY too low.
Delaying reject of request 4 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
rad_recv: Access-Request packet from host 192.168.2.100 port 35710,
id=86
authorize {
...
ldap {
# I don't understand next line:
fail = 1
}
if (fail) {
do_not_respond
}
...
}
Hi,
just for someone who will search answer later:
finally I found the explanation in
Hi,
I've used freeradius-1.1.3-1.6.el5 with openldap backend on my old
system. When OpenLDAP server was down, client requested the Freeradius
doesn't get any response and then requested another radius server.
Now, after upgade to freeradius-2.1.9-3.el6, the behavior has changed.
When backend LDAP
rss ln wrote:
It seems like it is correct behavior, but is it possible to change it
as before? When backend OpenLDAP is down, freeradius should not
respond to client?
Read raddb/policy.conf. Look for do_not_respond
Alan DeKok.
-
List info/subscribe/unsubscribe? See
Read raddb/policy.conf. Look for do_not_respond
Hello Alan,
Thank you, it solved the issue. I'm just not sure if I've implemented
it in right way:
authorize {
ldap {
# I don't understand next line:
fail = 1
}
if (fail) {
rss ln wrote:
Thank you, it solved the issue. I'm just not sure if I've implemented
it in right way:
If it works, don't worry about it.
If you want to continue worrying, read man unlang
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
:
Callis wrote:
I see a lot of radius timeout on my cisco router while
the
ping times is 10ms and my radius timeout is set to 50.
Is there any error message in file radius.log ?
--
Nicolas Baradakis
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info
The duplicate records increase to the extent that it
sometimes kills my radius server. What could be the
cause
of the timeout.
On Thu, 8 Sep 2005 15:27:34 +0200
Nicolas Baradakis [EMAIL PROTECTED] wrote:
Callis wrote:
I see a lot of radius timeout on my cisco router
while
the
ping
Hi all
I have freeradius-1.0.1-1 (with Petr Nixon's patch)
running on FC-3 and using a postgresql backend to collect
cisco AAA (stop only) records. My cisco IOS is 12.3(2)T2.
I see a lot of radius timeout on my cisco router while the
ping times is 10ms and my radius timeout is set to 50
Callis wrote:
I see a lot of radius timeout on my cisco router while the
ping times is 10ms and my radius timeout is set to 50.
Is there any error message in file radius.log ?
--
Nicolas Baradakis
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
22 matches
Mail list logo
