[RADIATOR] Lock Tacacs server to master instance

Hugh Irvine hugh at open.com.au
Thu Dec 10 03:39:55 UTC 2020


Hi Patrik -

The way I do this is with a single instance of Radiator configured for TACACS, and have this instance proxy the derived RADIUS requests to a second instance with Farmsize enabled.

This keeps the TACACS sessions operating correctly against a single process, and also allows multiple processing threads behind it.

hope that helps

Hugh



> On 8 Dec 2020, at 20:12, Patrik Forsberg <patrik.forsberg at globalconnect.se> wrote:
> 
> Hello (again),
> 
> Is it possible to lock <Server TACPLUS> into the master instance when using FarmSize ?
> 
> It seems that the session issue with tacacs+ becomes an issue when using FarmSize too not just moving between servers or restarting processes.. and yes I do have "AllowAuthorizeOnly" but that doesn't seem to help.
> 
> ---
> Best Regards,
> Patrik Forsberg
> _______________________________________________
> radiator mailing list
> radiator at lists.open.com.au
> https://lists.open.com.au/mailman/listinfo/radiator


--

Hugh Irvine
hugh at open.com.au

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER, SIM, etc. 
Full source on Unix, Linux, Windows, macOS, Solaris, VMS, NetWare etc.



More information about the radiator mailing list