Hello Deepak -
On Wed, 05 Jul 2000, Deepak Shrestha wrote:
> Hi Hugh,
> Its nice to hear from you too. Yes right, yarrina.connect.com.au is still
> the pri ns for np till date.
>
> There are still few things that confuse me regarding Gric.
>
> > The first is the Client side as you mention. When your customers are
> > travelling overseas and they want to connect back to you, the GRIC central
> > server will forward the requests to you and you must have a Client clause
> > configured as you have stated with a shared secret. This is essentially the
> > same thing as for any other NAS.
>
> I already have Gric Traveler running in different ports and uses its own
> users file. Why does the Client side of Gric have to communicate with the
> Radiator server when it has its own users (only roaming users) file? Only
> the Radiator communicates with the Gric Traveler when proxying for
> international users who use our NAS. I hope I'm right at this! Who does
> the authenticating part when our customers want to connect back to us when
> abroad? Is it Gric or Radiator?
>
The answer depends on how you want to operate. Most people want to use a single
user database for everything, so they have the GRIC server query Radiator which
in turn queries the user database. If you would rather have a different
database for GRIC, then you can continue to do what you are doing currently.
> We are planning to purchase Radiator Radius Server and RAdmin for all our
> AAA needs. I look forward for your help.
>
I'm always ready to help.
regards
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.
