Hello Gordon -
I think the simplest thing to do is use the new proxy load balancing in
Radiator 2.18 (in alpha now if you would like to do some testing). In
addition you would use the proxy caching to continue authenticating if you
have a database problem and/or the latest AuthBy SQL feature that lets you
write to a flat file if the database is unavailable.
hth
Hugh
On Monday 26 February 2001 13:34, Gordon Smith wrote:
> I agree. I'm wondering if you could recommend a setup that would allow the
> radius servers to handle authentication whether the Plat server is there or
> not. I was thinking of using perl scripts to update both databases so that
> they would stay in sync (I just don't trust MS SQL... )
> I've got the radius backend in PostgreSQL. I see that Platypus will ftp a
> flat file off, but I'm just not familiar enough with the SQL side of things
> to work out the best way to sync database to database. Multiple accounting
> clauses and a cron job for user updates, maybe?
>
> Cheers,
> Gordon
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Hugh Irvine
> Sent: Tuesday, 20 February 2001 13:35
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: (RADIATOR) multiple POPs
>
>
>
> 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.
>
>
> ===
> 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.
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
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.
