This is an optional integer that specifies the waiting time,
in seconds, for Status-Server request. If no reply is received within time
KeepaliveNoreplyTimeout defines, the Status-Server
request is marked as lost.
If this is not used, the used parameter
value depends on the AuthBy you are using:
<AuthBy RADCSEC>:
NoreplyTimeout value is used instead.<AuthBy RADIUS>:
RetryTimeout value is used instead.
Usually it is recommendable to have a smaller value for
KeepaliveNoreplyTimeout and larger value for
NoreplyTimeout or RetryTimeout.
The Status-Server receiver is on the next host and the reply comes
quickly. To have a short waiting time for
KeepaliveNoreplyTimeout, the possible failure
situation is discovered quickly and request is rerouted to another server.
The Access-Request or Accounting-Request receivers may be located on many
hops away and it is possible that it take longer time to get the replies
from them.
Here is an example of using both
KeepaliveNoreplyTimeout and
NoreplyTimeout in <AuthBy
RADSEC>:
<AuthBy RADSEC>
NoreplyTimeout 10
KeepaliveNoreplyTimeout 3
</AuthBy>
To use this example with
<AuthBy RADIUS>, you must use
Retrytimeout instead of
NoreplyTimeout.
