Hello Philip -
On Tue, 28 Sep 1999, Philip Buckley wrote:
> Hi everyone,
>
>
> Has anyone ever setup GRIC with RADIATOR before but gric
> not being the default realm. I have a situation where I am running gric
> aim traveller on the same machine as radiator. The situation is, is
> there away to tell radiator which port to access the gric traveller on
> because I thinking it is looking for radius authentication on the
> default ports. Therefore I am not getting any users authenticated.
There are two aspects to your problem. The first is accepting radius requests
from GRIC - this is accomplished with a normal Client clause listening on the
AuthPort and AcctPort specified in the configuration file. The second
aspect is forwarding requests from Radiator to GRIC - this is done with an
AuthBy RADIUS which can include an AuthPort and AcctPort specification. See
Sections 6.25 and 20.0 in the Radiator 2.14.1 reference manual.
You just need to make sure that GRIC and Radiator are configured for different
ports (1645/1646 for one, and 1812/1813 for the other?).
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
NT, Rhapsody
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
