Hello Christian -
On Tue, 30 May 2000, [EMAIL PROTECTED] wrote:
> hi there,
>
> i was trying to make the auth-module from ipass.
> ipass is succesfully installed... after trying to compile i got following
> error. does someone know the reason ?
>
Have you installed the IpassPerl software?
http://www.open.com.au/radiator/downloads/IpassPerl-1.5.tar.gz
Also note the realease notes for Radiator 2.16 regarding iPASS.
"Due to changes in policy by iPASS, the preferred method of
interoperating with iPASS outbound is now to proxy to the iPASS radius
server. Altered documentation to suit."
> IpassPerl-1.5 > perl Makefile.PL
> Note (probably harmless): No library found for -lip
> Note (probably harmless): No library found for -lssl
> Note (probably harmless): No library found for -lcrypto
> Writing Makefile for Ipass
> root@p700:/home/steger/ipass/IpassPerl-1.5 > make
> cc -c -I/usr/ipass/include -Dbool=char -DHAS_BOOL -I/usr/local/include -O2
> -pipe -DVERSION=\"1.5\" -DXS_VERSION=\"1.5\" -fpic
> -I/usr/lib/perl5/5.00503/i586-linux/CORE Ipass.c
> Ipass.xs: In function `XS_Ipass_remote_auth':
> Ipass.xs:389: structure has no member named `called_number'
> Ipass.xs:389: structure has no member named `called_number'
> Ipass.xs:389: structure has no member named `called_number'
> Ipass.xs: In function `XS_Ipass_remote_auth_chap':
> Ipass.xs:446: structure has no member named `called_number'
> Ipass.xs:446: structure has no member named `called_number'
> Ipass.xs:446: structure has no member named `called_number'
> Ipass.xs: In function `XS_Ipass_remote_acct':
> Ipass.xs:517: structure has no member named `called_number'
> Ipass.xs:517: structure has no member named `called_number'
> Ipass.xs:517: structure has no member named `called_number'
> Ipass.xs:520: structure has no member named `called_number'
> Ipass.xs:520: structure has no member named `called_number'
> Ipass.xs:520: structure has no member named `called_number'
> make: *** [Ipass.o] Error 1
>
> the second question here:
> in fact that hopefully the module is working well, can i simply add it in
> but it between my REALM DEFAULT ?
>
> after <auth sql>?
>
> like:
> <authby sql>
> <authby ipass>
>
> should that work ?
>
It is more usual to use Realms when implementing roaming, something like this:
<Realm your.realm>
<AuthBy SQL>
....
</AuthBy>
</Realm>
<Realm DEFAULT>
<AuthBy IPASS>
....
</AuthBy>
or
<AuthBy RADIUS>
....
</AuthBy>
</Realm>
This is because the outbound requests must have userids of the form
[EMAIL PROTECTED]
If you are not using Realms currenly for your own users, you can use the
DefaultRealm construct in your Client clauses to append it.
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.
