On 20.11.2020 15.53, Frank Danielson wrote:
Thanks for pointing out the change that allows the use MaxTargetHosts. We’ll update to 4.25 and use that for now.
The patch packages for 4.25 now have an udpated that fixes the problem with infinite retires. Similar to HASHBALANCE, the retry logic is handled by chooseHost() within the balance algorithm. In short: it keeps track of hosts it has already tried instead of just keeping a count of them.
These changes do not affect MaxTargetHosts. It's still available for configurations where the count of possible next hop hosts exceeds the reasonable number, limit being typically the time taken, of forwarding attempts.
Thanks again for reporting this! 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
