Hello Deepak -
How nice to hear from you - I had some dealings with Sanjib when I was at
Connect.com.au and we ran the .np domain on behalf of Nepal.
On Wed, 05 Jul 2000, Deepak Shrestha wrote:
> Hi,
>
> I'm a bit confused about the way Gric AimTraveler server acts like a
> radius client. I presume that for the Radiator server to respond to
> requests sent to it from the Gric Aim Traveler, I need to have the
> <Client> clause specifying the shared secret.
>
> Can anyone describe to me how this works ( Gric AimTraveler as the client
> and Radiator Radius as the server).
>
There are two aspects to roaming (either GRIC or iPASS):
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.
The second aspect is when overseas travellers who are in Nepal use your dialup
service to connect back to their home service. This involves setting up a
<Realm DEFAULT> (or equivalent Handler) and using an AuthBy RADIUS within it to
proxy the requests to GRIC. This is essentially the same thing as pretending to
be a NAS.
If you have any other questions, I am always happy to help. And I am also
available for on-site installation and training - I have talked to Sanjib in the
past about coming to Kathmandu for a visit!!
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.
