Failover fails in proxy.conf
Santiago Balaguer García
santiagoawa at hotmail.com
Tue Jun 16 10:32:39 CEST 2009
> > With the primary server everything works fine, but my problem is when I
> > force to switch to fallover server (I switch off IP 1.2.3.4 machine) my
> > freeradius server does not change to request 1.2.3.5 server.
>
> How hard have you tried? It does not mark home server as dead on the first
> packet that doesn't get answered. Have a look at proxy.conf and dead and
> zombie times.
Sincerely I do not know how to mark a home server as 'dead'.
The only way is response_window = 5 ('dead' after five seconds, I think).
See my new proxy.conf
#######################################
home_server primary_server {
type = auth+acct
ipaddr = 1.2.3.4
port = 1812
secret = mysecret
require_message_authenticator = no
response_window = 5
zombie_period = 30
revive_interval = 900
status_check = status-server
check_interval = 60
num_answers_to_alive = 3
}
home_server secondary_server {
type = auth+acct
ipaddr = 1.2.3.5
port = 1812
secret = mysecret
require_message_authenticator = no
response_window = 5
zombie_period = 30
revive_interval = 900
status_check = status-server
check_interval = 60
num_answers_to_alive = 3
}
home_server_pool roam_pool {
type = fail-over
home_server = primary_server
home_server = secondary_server
}
realm myrealm.com {
nostrip
pool = roam_pool
}
_________________________________________________________________
Chatea sin límites en Messenger con la tarifa plana de Orange
http://serviciosmoviles.es.msn.com/messenger/orange.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20090616/6a70cfdc/attachment.html>
More information about the Freeradius-Users
mailing list