Hi Lachlan,
you can use PostAuthHook which allows you to do anything you wish with
reply, strip Framed-Ip-Address attribute for example.
hooks.txt file contains full information how to do it.
MM> --- Forwarded mail from [EMAIL PROTECTED]
MM> Date: Thu, 28 Dec 2000 17:40:13 +1100 (EST)
MM> From: [EMAIL PROTECTED]
MM> To: [EMAIL PROTECTED]
MM> Subject: BOUNCE [EMAIL PROTECTED]: Non-member submission from ["Lachlan
MM> Fletcher" <[EMAIL PROTECTED]>]
>>From mikem Thu Dec 28 17:40:09 2000
MM> Received: by oscar.open.com.au (8.9.0/8.9.0) id RAA10847
MM> for [EMAIL PROTECTED]; Thu, 28 Dec 2000 17:40:09 +1100 (EST)
>>Received: from mail.ausisp.com (mail.ausisp.com [203.2.239.72]) by
MM> perki.connect.com.au with ESMTP id RAA07567
MM> (8.8.8/IDA-1.7 for <[EMAIL PROTECTED]>); Thu, 28 Dec 2000 17:19:33 +1100
MM> (EST)
MM> Received: from mail.ausisp.com (mail.ausisp.com [203.2.239.72]) by
MM> perki.connect.com.au with ESMTP id RAA07567
MM> (8.8.8/IDA-1.7 for <[EMAIL PROTECTED]>); Thu, 28 Dec 2000 17:19:33 +1100
MM> (EST)
MM> Received: from lfletcher (nm1.geko.net.au [203.2.239.20])
MM> by mail.ausisp.com (8.9.3/8.9.3) with SMTP id RAA25385
MM> for <[EMAIL PROTECTED]>; Thu, 28 Dec 2000 17:19:32 +1100 (EST)
MM> envelope-from <[EMAIL PROTECTED]>
MM> From: "Lachlan Fletcher" <[EMAIL PROTECTED]>
MM> To: <[EMAIL PROTECTED]>
MM> Subject: AuthBy SQL
MM> Date: Thu, 28 Dec 2000 17:21:30 +1100
MM> Message-ID: <[EMAIL PROTECTED]>
MM> MIME-Version: 1.0
MM> Content-Transfer-Encoding: 7bit
MM> X-Priority: 3 (Normal)
MM> X-MSMail-Priority: Normal
MM> X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
MM> In-Reply-To: <a04320401b67039c892d5@[10.1.1.30]>
MM> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
MM> Importance: Normal
MM> Content-Type: text/plain;
MM> charset="iso-8859-1"
MM> Hi,
MM> I was wondering if anyone may be able to help here.
MM> I want to use "AuthColumnDef" option with "AuthSelect" in "AuthBy SQL".
MM> My problem is with reply items. Some users need more reply items than
MM> others.
MM> For example, our permanent modem customers get given a single fixed IP
MM> address of their own, where our standard dial-up customers do not, and the
MM> NAS server assigns them one from it's own IP range.
MM> So, we have a field in our database call "IPADDRESS" and every customer has
MM> this field. Normally, the customer does not have an IP, and their field is
MM> NULL, however those with fixed IP's will have a value in this field.
MM> How can we tell radiator to send the reply item ONLY if the field is not
MM> null, and ignore it otherwise? Sending the reply item with no value just
MM> causes a dialup error.
MM> We have several other options like this that we have to use.
MM> Does anyone have any suggestions?
MM> Kind Regards,
MM> Lachlan.
>> -----Original Message-----
>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
>> Behalf Of Hugh Irvine
>> Sent: Thursday, 28 December 2000 10:36
>> To: Bryn Wm. Moslow; [EMAIL PROTECTED]
>> Subject: Re: (RADIATOR) UNIX groups and NAS restrictions
>>
>>
>>
>> Hello Bryn -
>>
>> At 15:55 -0800 00/12/21, Bryn Wm. Moslow wrote:
>> >I could swear up and down that I once saw an example of this
>> either in the
>> >Radiator reference or the FAQ but I can no longer dig it up:
>> >
>> >I need to refuse logins on certain NAS's for explicit UNIX
>> groups. For the
>> >sake of precision I'll also describe it this way: I need to
>> allow users in
>> >certain UNIX groups to ONLY log in to certain NAS's. Either way works for
>> >me.
>> >
>> >I got the impression that this may be possible using
>> NAS-Address-Port-List
>> >in a creative way but I remember seeing a really simple, direct way of
>> >doing it. Suggestions or directional assistance?
>> >
>>
>> Probably the simplest way to do this is with an AuthBy FILE:
>>
>> # configuration to check NAS and UNIX groups
>>
>> <Client .....>
>> Identifier XXXX
>> .....
>> </Client>
>>
>> <AuthBy UNIX>
>> Identifier CheckUnix
>> .....
>> </AuthBy>
>>
>> <AuthBy FILE>
>> Identifier CheckUsers
>> Filename %D/users
>> ....
>> </AuthBy>
>>
>> <Realm ....>
>> ....
>> AuthBy CheckUsers
>> ....
>> </AuthBy>
>>
>>
>> And in the users file:
>>
>> # %D/users
>>
>> someuser NAS-Identifier = XXXX, Auth-Type = CheckUnix, Group = .....
>>
>> ......
>>
>>
>> If you have any questions please ask.
>>
>> hth
>>
>> Hugh
>>
>>
>>
>>
>>
>> --
>>
>> 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.
>>
>> ===
>> 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.
>>
MM> ---End of forwarded mail from [EMAIL PROTECTED]
With respect,
Pavel A Crasotin
____________________________________
OJSC SeverTransCom
40/13 Sobinova, Yaroslavl, 150000, Russia
Tel/Fax: +7 (0852) 47-71-70, 47-69-49
+7 (0852) 72-17-28, 72-17-38
===
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.
