P.S a worse scenario unfolds when the downstream host is responding to Auth
(and Status-Server), but not to Accounting. In this case Accounting is still
being load-balanced to the downstream host, but all requests enter an infinite
re-transmit loop until they are accepted.
With high volumes of
Hi,
I have found an issue where the "Retries" clause is ignored when using
UseStatusServerForFailureDetect with "AuthBy LOADBALANCE".
In a scenario where a downstream proxy becomes unresponsive requests enter a
re-transmit loop until the next Status-Server keepalive detects the host has
failed
We have been requested to try and loadbalance requests to a Campus department
with their own Radius (IAS) server for their wireless users. We currently
proxy to them from our Radiator server(s) for their users, however, their
current server cannot handle to load. They have added 2 new servers
