Hello Elias -
You can make both GRIC and iPASS work for incoming requests from
your users who are travelling overseas, with Client clauses for both
services.
However, unless you know which realms to forward to which
service (or unless you create two special realms, one for each
service), you will only be able to forward outbound requests to one
service or the other. This is because there is only one DEFAULT
realm, as you have discovered.
hth
Hugh
At 9:27 +0700 28/4/3, Elias wrote:
Hi,
Is there a way to make radiator work with both GRIC and iPASS services? Currently our GRIC roaming is already working, but we are having trouble getting iPASS to work. Our current setup forwards all non-local realms to GRIC. How can I include iPASS into this setup? Thanks for you help.
<Realm DEFAULT>
<AuthBy RADIUS>
Host xxxxxx
Secret xxxxxxx
AuthPort 1645
AcctPort 1646
Retries 1
AddToReply Framed-Protocol = PPP,\
Service-Type = Framed-User,\
Framed-IP-Netmask = 255.255.255.255,\
Framed-Routing = Listen,\
Framed-MTU = 1500,\
Framed-Compression = Van-Jacobson-TCP-IP
</AuthBy>
</Realm>
- Elias -
--
NB: I am travelling this week, so there may be delays in our correspondence.
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.
