Hello Randy -
On Fri, 12 May 2000, Randy Cosby wrote:
> We recently merged with a couple smaller ISP's. Currently one is running
> off RadiusNT, another off of a livingston radius. I would like to have all
> our dialup pops pointing to just one radius eventually. The first logical
> step seems to be using Radius as a proxy for all the other radius servers.
>
> Users do not log in with realms. So we might have a user "smith" on two or
> more of the radius servers.
>
> What's the best way to deal with this? I can think of some ways to do a
> fallthrough based on a "primary" radius being that of the original ISP, then
> down to the others if it fails, but we might get into some real problems
> with slow responses from the other radius servers bogging down our
> radiator.
>
> I'm sure I'm not the first to tackle this. Any hints?
>
You've got a couple of options. The first would be to use the "DefaultRealm"
parameter in your Client clauses if the different NAS's correspond to the
different original ISP's, then you could use normal Realms with corresponding
AuthBy RADIUS clauses to proxy the requests. Alternatively, you could have the
different groups calling different phone numbers at the PoP's, and then set up
Handler's corresponding to the different Called-Station-Id's with the same
AuthBy RADIUS clauses as above for proxying.
hth
Hugh
--
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.
