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?
We are planning to purchase Radiator Radius Server and RAdmin for all our
AAA needs. I look forward for your help.
Regards,
Deepak
===
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.
