--- Forwarded mail from [EMAIL PROTECTED]
Date: Thu, 15 Feb 2001 03:40:23 +1100 (EST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: BOUNCE [EMAIL PROTECTED]: Non-member submission from
[[EMAIL PROTECTED]]
>From mikem Thu Feb 15 03:40:19 2001
Received: by oscar.open.com.au (8.9.0/8.9.0) id DAA16347
for [EMAIL PROTECTED]; Thu, 15 Feb 2001 03:40:18 +1100 (EST)
From: [EMAIL PROTECTED]
>Received: from mail.verkkotieto.com (brown.verkkotieto.com [212.86.0.22]) by
perki.connect.com.au with ESMTP id DAA25164
(8.8.8/IDA-1.7 for <[EMAIL PROTECTED]>); Thu, 15 Feb 2001 03:33:49 +1100
(EST)
Received: from mail.verkkotieto.com (brown.verkkotieto.com [212.86.0.22]) by
perki.connect.com.au with ESMTP id DAA25164
(8.8.8/IDA-1.7 for <[EMAIL PROTECTED]>); Thu, 15 Feb 2001 03:33:49 +1100
(EST)
Received: from black.verkkotieto.com (black.verkkotieto.com [212.86.0.14])
by mail.verkkotieto.com (8.9.3+Sun/8.9.3) with ESMTP id SAA23495
for <[EMAIL PROTECTED]>; Wed, 14 Feb 2001 18:33:33 +0200 (EET)
Date: Wed, 14 Feb 2001 18:33:32 +0200 (EET)
X-X-Sender: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: Different static IP for different Clients
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi,
We have 2 NAS's for dial-in purposes and mostly IPs
are assigned from pool. Couple of users need static IPs.
These users call single number and their calls are forwarded
to either of NAS's. Because of lack of proper routing
protocol we decided to give them two static IP:s depending
of which NAS they end up to.
So we've made a users file for them that uses check-item
Client-Id to give them correct IP. Users file has
two occurances for the user, one for each NAS (see below).
Problem is that when user comes from client1, radiator seems
to process the second user line also ending up with reject
(see log clip). If user comes from client2, Client-Id check
item is matched and user gets ip2.
I can see the reason why it happens and also have postauthhook
to deal with situation, but postauthhook isn't as maintainable
as users file.
I'm using Radiator 2.16 (don't touch if it works...)
Any suggestions?
Thanks in advance,
Petri
-----------------------------------------------------------
<users>
user Auth-Type = CheckSystem, Group = access, Client-Id = client1
Service-Type = Framed-User,
Framed-Protocol = PPP,
Framed-IP-Netmask = 255.255.255.255,
Framed-IP-Address = ip1
user Auth-Type = CheckSystem, Group = access, Client-Id = client2
Service-Type = Framed-User,
Framed-Protocol = PPP,
Framed-IP-Netmask = 255.255.255.255,
Framed-IP-Address = ip2
</users>
<log>
Wed Feb 14 17:50:39 2001: DEBUG: Radius::AuthFILE REJECT: Client-Id does
not match
</log>
---End of forwarded mail from [EMAIL PROTECTED]
--
Mike McCauley [EMAIL PROTECTED]
Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW
24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au
Phone +61 3 9598-0985 Fax +61 3 9598-0955
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory etc etc
on Unix, Win95/8, 2000, NT, MacOS 9, 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.
