--- Forwarded mail from [EMAIL PROTECTED]
Date: Fri, 12 Jan 2001 08:10:20 +1100 (EST)
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: BOUNCE [EMAIL PROTECTED]: Non-member submission from [Cory Visi
<[EMAIL PROTECTED]>]
>From mikem Fri Jan 12 08:10:14 2001
Received: by oscar.open.com.au (8.9.0/8.9.0) id IAA20140
for [EMAIL PROTECTED]; Fri, 12 Jan 2001 08:10:13 +1100 (EST)
>Received: from mail1.discovernet.net (mail1.discovernet.net [206.165.166.15])
by perki.connect.com.au with ESMTP id IAA08955
(8.8.8/IDA-1.7 for <[EMAIL PROTECTED]>); Fri, 12 Jan 2001 08:00:07 +1100
(EST)
Received: from mail1.discovernet.net (mail1.discovernet.net [206.165.166.15])
by perki.connect.com.au with ESMTP id IAA08955
(8.8.8/IDA-1.7 for <[EMAIL PROTECTED]>); Fri, 12 Jan 2001 08:00:07 +1100
(EST)
Received: from localhost (visi@localhost)
by mail1.discovernet.net (8.9.1/8.9.1) with ESMTP id QAA24186
for <[EMAIL PROTECTED]>; Thu, 11 Jan 2001 16:00:09 -0500
Date: Thu, 11 Jan 2001 16:00:08 -0500 (EST)
From: Cory Visi <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: some unknown vendor attributes and another dictionary-related question
In-Reply-To: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Previously, I was using Radiator to do authentication with our USR
HiperArc unit. We have recently started using an external dialup source to
offload some of the call volume. This external source happens to be using
Ascend gear so I had to make some changes to the dictionary file.
I started with dictionary.usr then took all the Vendor 529
(Ascend) VENDORATTR lines from dictionary.ascend2 and stuck them on the
bottom.
After doing this, I still have a few vendor attributes that I can't find
in any dictionaries (even the latest: 10-Jan-2001 17:26).
This is coming from our USR HiperARC (this has always been a problem):
Thu Jan 11 12:08:58 2001: ERR: Attribute number 1 (vendor 9) is not
defined in your dictionary
These are coming from an external Ascend unit:
Thu Jan 11 12:04:12 2001: ERR: Attribute number 86 (vendor 529) is not
defined in your dictionary
Thu Jan 11 12:04:12 2001: ERR: Attribute number 13 (vendor 529) is not
defined in your dictionary
Thu Jan 11 13:03:17 2001: ERR: Attribute number 66 (vendor 529) is not
defined in your dictionary
Thu Jan 11 13:03:17 2001: ERR: Attribute number 67 (vendor 529) is not
defined in your dictionary
In addition, I was able to get most of the Ascend vendor attributes
however they all map to attribute names Ascend-*. Is there a way to
have this integrate with normal Radiator variables so I don't have to
change my accounting information? What am I missing here?
For instance, for users calling into the Ascend gear, there is no Connect
speed or Modulation Type in the session database. My Query string for the
session database uses "Connect-Speed" and "Modulation-Type". I'm guessing
that this data is coming from the Ascend gear, but getting placed in an
Ascend-* variable, so how would I "map" this over to the usual
respective Radiator attributes?
Thanks for any help you can provide,
Cory Visi
DiscoverNet, Inc.
(203) 351-1178
---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.
