Hello Gordon -
At 9:59 +1300 01/2/20, Gordon Smith wrote:
>We're currently setting up Platypus as well.
>
>One radius server can talk to as many NAS's as you like - just set then up
>to auth to the same server.
>I'm looking at keeping the Radiator server separate from Platypus and using
>perl scripts to update the radius database, and sending accounting info back
>from radius to Platypus. The idea is not to load one server up excessively,
>which could interfere with authentication.
>
In general terms, you should always have at least two Radiator hosts
and configure your NAS(s) to use one as the primary radius host and
the other as the secondary radius host. This is for redundancy in the
face of one of your Radiator hosts going down. Of course, both
Radiator hosts can connect to the same backend SQL/Platypus host,
which I agree should be on a seperate machine (preferably with
hot-swap RAID disks).
hth
Hugh
--
NB: I am travelling this week, so there may be delays in our correspondence.
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
