Hello Alan - Yes absolutely - you typically want authentication to operate as quickly as possible, and its usually a fairly lightweight lookup operation.
Accounting on the other hand is less time-critical and usually involves more processing to store the records. Therefore it makes sense to have these operations running in separate processes. Ie. …. # Authentication Instance Configuration # Listen for authentication requests only AuthPort 1645, 1812 AcctPort ….. …. # Accounting Instance Configuration # Listen for accounting requests only AuthPort AcctPort 1646, 1813 ….. regards Hugh > On 17 Oct 2015, at 23:39, Alan Buxey <a.l.m.bu...@lboro.ac.uk> wrote: > > >BTW - it is generally a good idea to >have separate authentication and > >>accounting instances as well (ie. one >Windows service for authentication > >on >1645 and/or 1812, and another >Windows service for accounting on >1646 > >and/or 1813). > > I'm guessing this is also true for Unix/linux/solaris installs too? > > alan -- Hugh Irvine h...@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, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
