[RADIATOR] AuthRADSEC: StatusServerNoreplyTimeout needed instead of NoreplyTimeout

[Heikki Vatiainen]

On 3.9.2017 0.00, Karl Gaissmaier wrote:

> The timeout for proxied radius packets MUST NOT be mixed with timeouts 
> for StatusServer checks.
> 
> What's your opinion about this topic?

Good idea. This is now in patches. It's now possible to have a separate 
timeout for Status-Server probes. If it is not set, the default is to 
use NoreplyTimeout which is the current behaviour.

> Btw, the whole process for failover and missing retries (as in 
> AuthRADIUS) to the same (working) upstream server should be refactored 
> for AuthRADSEC.

Yes, there's a lot of similar functionality which may receive work in 
the future.

Thanks,
Heikki

-- 
Heikki Vatiainen <hvn at open.com.au>

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.