Didn't get the message through the list for some reason - replying
indirectly.
When FarmSize is set, the workers message via Gossip backend (currently
Redis) about reachability of the next hop. By default all workers use
Status-Server probes. However, it's likely that this probing is
excessive, so you should try something like this:
# see goodies/farmsize.cfg for a full example
<Gossip>
# Parameters
</Gossip>
<AuthBy RADIUS,RADSEC,HASHBALANCE,etc.>
Gossip
UseStatusServerForFailureDetect
KeepaliveTimeout 5
NoKeepaliveTimeoutForChildInstances
# Other parameters
</AuthBy>
To summarise: with the above one worker (instance #1) does the probing
and uses Redis to keep the other workers informed about the next hop
reachability.
Thanks,
Heikki
--
Heikki Vatiainen <[email protected]>
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, TACACS+, PAM, Active Directory,
EAP, TLS, TTLS, PEAP, WiMAX, RSA, Vasco, Yubikey, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, etc.
_______________________________________________
radiator mailing list
[email protected]
https://lists.open.com.au/mailman/listinfo/radiator
