I would like the requests to be handled in this fashion:
Suppose a user logs in with your example, "[EMAIL PROTECTED]".
First the realm is checked against any local Realm/Handler statements.
Then the first DEFAULT realm statement catches it and proxies it to a GRIC
radius server.
Finally, the second DEFAULT realm (hypothetically) statement catches it
and proxies it to a USOnline radius server.
If all of these fail, the radius request fails.
In this setup USOnline requests could be pretty slow to repond, but that's
ok, since GRIC is more expensive to our end-user.
Thanks,
Cory
Kitabjian, Dave [[EMAIL PROTECTED]] wrote:
> Hmm. Well, my question to you is, whom to you WANT to get the default
> realms? In other words, say you get a request from "[EMAIL PROTECTED]" --
> whom are you going to proxy it to: GRIC or USOnline?
>
> After you answer that question, we can answer your question.
>
> Dave
>
> > -----Original Message-----
> > From: Cory Visi [mailto:[EMAIL PROTECTED]]
> > Sent: Tuesday, May 22, 2001 11:26 AM
> > To: [EMAIL PROTECTED]
> > Subject: (RADIATOR) default realms
> >
> >
> > I'm currently attempting to implement both GRIC and USOnline roaming
> > setups. Both of these require me to use a default realm. As
> > far as I can
> > tell, Radiator only supports one default realm. Is this
> > correct? If not,
> > how do I get Radiator to recognize two or more entries for a
> > default realm
> > (currently it seems to use the last definition).
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
