Here's another one for you :)
# Procera
VENDOR Procera 12913
VENDORATTR 12913 Procera-Local-User-Name 1 string
On 28/09/12 07:18, Mike McCauley wrote:
Hi,
Added to dictionary.
Thanks.
Cheers.
On Thursday, September 27, 2012 01:30:48 PM Caporossi, Steve G. wrote:
We have a system that
Hi,
Thanks. Added to the latest patch set.
Cheers.
On Thursday, October 04, 2012 10:56:11 AM Lucas Hazel wrote:
Here's another one for you :)
# Procera
VENDOR Procera 12913
VENDORATTR 12913 Procera-Local-User-Name 1 string
On 28/09/12 07:18, Mike McCauley wrote:
Hi,
Added to
We have a system that required these being added to the radius dictionary.
Thought I'd pass it along in case anyone else needed them.
#
# Opnet
#
VENDOR Network-Physics 7119
VENDORATTR 7119NetworkPhysics-Attribute33 string
Thanks,
Steve
smime.p7s
Description:
Hi,
Added to dictionary.
Thanks.
Cheers.
On Thursday, September 27, 2012 01:30:48 PM Caporossi, Steve G. wrote:
We have a system that required these being added to the radius dictionary.
Thought I'd pass it along in case anyone else needed them.
#
# Opnet
#
VENDOR Network-Physics 7119
On 06/07/2011 08:09 PM, Heikki Vatiainen wrote:
On 06/06/2011 07:27 PM, Bruno Tiago Rodrigues wrote:
Hello Bruno and others,
[about attributes 119-123 and possible others too]
I was wondering if this could be fixed (or at least documented) on the
next releases.
I'll check about adding
Dear all
The standard radiator dictionary file specifies at least a pair of
invalid entries sharing the same ID.
Apparently, Ascend defines a set of attributes on the global (IANA
assigned) range.
ATTRIBUTEX-Ascend-FCP-Parameter119string -
conflicts with Digest-Domain
Hi,
Grrr. ascend dictionaries stomp all over IANA space - attributes
126-132 are also munged up (used by IANA assign Operator-Name space
stuff - which we in eduroam would like to use widely)
alan
___
radiator mailing list
radiator@open.com.au
Hi,
FYI
The dictionary in Radiator 3.7.1 contains an error regarding a Unisphere
(Juniper) ERX attribute.
This VSA is a string, not an integer.
VENDORATTR 4874Unisphere-Service-Bundle31 integer
rgds, \\Jan
-
Jan
Hello Jan -
Many thanks - I will fix this for the next release.
regards
Hugh
On 17/11/2003, at 10:40 PM, Munkhammar Jan wrote:
Hi,
FYI
The dictionary in Radiator 3.7.1 contains an error regarding a
Unisphere
(Juniper) ERX attribute.
This VSA is a string, not an integer.
VENDORATTR 4874
HelloJan,
Thanks for this report. We have now fixed it for the next release and uploaded
a new dictionary to the 3.7.1.patches area.
Cheers.
On Tue, 18 Nov 2003 08:16 am, Hugh Irvine wrote:
Hello Jan -
Many thanks - I will fix this for the next release.
regards
Hugh
On 17/11/2003, at
I have installed, and appear to have running Radiator (3.6-1) with mysql
(3.23.56-1.80) on Redhat 8.0
When i try and restart the radiator daemon, i get the following
message:
Starting Radiator: Coulsdn't create dictionary from './dictionary'.
Check log for more information: Inappropriate ioctl
Hello Chris -
How have you installed Radiator?
And can you send me a copy of your configuration file and the trace 4
debug showing what is happening?
You can also check the FAQ and the mailing list archive:
www.open.com.au/radiator/faq.html
www.open.com.au/archives/radiator
regards
Hugh
Ignore that - I found them!
Sorry to waste bandwidth - it's been a long day.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
Hello Zia -
Vendor 4874 is Unisphere, vendor 2352 is Redback, and vendor 0 is the
standard RFC numbers.
I think you will find that almost all (if not all) of these attributes
are defined in the Radiator 3.4 dictionary(s).
regards
Hugh
On Sunday, Dec 8, 2002, at 01:13 Australia/Melbourne,
Message-
|From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
|Sent: Sunday, December 08, 2002 5:12 PM
|To: [EMAIL PROTECTED]
|Cc: [EMAIL PROTECTED]
|Subject: Re: (RADIATOR) dictionary and attribute
|
|
|
|Hello Zia -
|
|Vendor 4874 is Unisphere, vendor 2352 is Redback, and vendor 0 is the
|standard
Sorry about the prev. mail without subject.
|-Original Message-
|From: Ziaur Rahman [mailto:[EMAIL PROTECTED]]
|Sent: Saturday, December 07, 2002 10:12 PM
|To: [EMAIL PROTECTED]
|Subject:
|
|
|
|Hi,
|
|I am getting a lot of following ERR in the logs:
|
|Sat Dec 7 22:00:40 2002: ERR:
Hi
I keep getting too many of Attribute not defined in your dictionary - when
can I get a dictionary
that has all these attributes?
I have these types of Nases.
-Cisco AS5300
-Total Control
Tue Nov 19 15:59:32 2002: ERR: Attribute number 105 (vendor 429) is not
defined in your dictionary
Tue
Hello -
Vendor 429 is USR, and you will find many USR dictionary definitions in
the file dictionary.usr.
You should add the vendor-specifics to the standard Radiator dictionary
with your favourite text editor.
After changing the dictionary you will need to restart Radiator so the
new
I keep getting this error message:
Attribute number 151 is not defined in your dictionary
But it does appear to be in the dictionary file:
# grep 151 dic*
dictionary:VALUE Ascend-Disconnect-Cause localAdmin
151
Any ideas what I should be looking for to find this issue?
Hi,
we finally got radiator working fine for a while and then we started to get
all these dictionary errors:
Sat Sep 15 17:16:24 2001: ERR: Attribute number 77 (vendor ) is not defined
in your dictionary
Sat Sep 15 17:16:24 2001: ERR: Attribute number 30 (vendor 5) is not defined
in your
Hello Roger -
On Saturday 15 September 2001 17:21, Roger Mangraviti wrote:
Hi,
we finally got radiator working fine for a while and then we started to get
all these dictionary errors:
Sat Sep 15 17:16:24 2001: ERR: Attribute number 77 (vendor ) is not defined
in your dictionary
Sat Sep
Hello Todd -
This is incorrect for two reasons. The first is that Client clauses are
global clauses (they don't go in Handlers), and the second is that you can
only specify a single global dictionary file.
You should start with the file called dictionary in the Radiator
distribution and add
Is it legal to assign dictionary files within client statements?
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
Well to assign dictionary files in client or in handlers that have clients..
Handler
%D/DictionaryFile dictionary.ascend
Client blah
settings...
/Client
Client blah2 # Same Modem type
Hello,
Is there someone, who has managed to get a grab on following attribute
numbers, as an addition to the existing dictionaries provided with Radiator?
I'm looking for the following ones:
Vendor 429 (attribute 39051)
Vendor 1397446990 (attribute 69)
I'ld also like to know, whether there is
To find what vendor a vendor number refers to, you have to take a look at:
ftp://ftp.isc.org/in-notes/iana/assignmets/enterprise-numbers
These are the enterprise numbers assigned by IANA to use as private OID's
in SNMP and LDAP/X.500. They are also used as Radius Vendor numbers.
In SNMP and
Hello Andy -
If you are always getting the same attribute numbers in your errors, you can
put a dummy entry in the dictionary file so that at least the attribute gets
translated. Use your favourite text editor, but when you do find the correct
definitions please let us know so we can add
Is there a separate data dictionary for the CVX boxes?
I know that the CVX attributes appear in the standard
large dictionary, but I want to build a custom dictionary
which only contains dictionary.ascend, dictionary.redback
and the CVX attributes. I noticed someone posted a CVX
dictionary to
Hello John -
On Friday 27 April 2001 09:59, John Coy wrote:
Is there a separate data dictionary for the CVX boxes?
I know that the CVX attributes appear in the standard
large dictionary, but I want to build a custom dictionary
which only contains dictionary.ascend, dictionary.redback
and
Hugh,
Thanks for the feedback. I did upgrade to 2.18.1, appreciate the
hint about the dictionary file. I did end up doing basically
what you suggested -- started with the dictionary file and removed
the VSA's I didn't need and added the redback ones. All in all
I should be set.
Thanks,
John
My bad..
thx :)
-a
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Hugh Irvine
Sent: woensdag 28 maart 2001 8:17
To: Andy De Petter; Radiator Mailing
Subject: RE: IMPORTANT - Re: (RADIATOR) dictionary question
Hello Andy -
I think you may
Hi guys,
I was just wondering, whether someone knows, whether you can have some kinds
of "aliases", in your dictionary? For example, if you'ld want to support:
ATTRIBUTE attname1999 ipaddr
BUT you'ld also want another attribute, to point to the same one:
ATTRIBUTE
Hi Andy -
At 10:31 +0200 01/3/27, Andy De Petter wrote:
Hi guys,
I was just wondering, whether someone knows, whether you can have some kinds
of "aliases", in your dictionary? For example, if you'ld want to support:
ATTRIBUTE attname1999 ipaddr
BUT you'ld also want
Hello Andy -
I think you may have misunderstood my previous message.
It is entirely possible to map multiple names to the same numeric
attribute number (indeed the latest Radiator dictionary does this).
However, the last such definition will be the only one that is used
for the mapping from
radiator 2.17.1
mysql 3.22.32
cisco 5300
for almost every single call, i get the following error in my log file:
22/01/2001 23:24
There is no value named h323-disconnect-cause=10 for
attribute cisco-h323-disconnect-cause. Using 0.
however, in my dictionary file:
VENDORATTR
Hello Ken -
I would like to see a trace 4 debug showing what is happening with
the packets that cause this log message.
thanks
Hugh
At 9:45 -0500 01/1/23, Ken Sain wrote:
radiator 2.17.1
mysql 3.22.32
cisco 5300
for almost every single call, i get the following error in my log file:
ECTED]]
Sent: Tuesday, January 23, 2001 9:45 AM
To: [EMAIL PROTECTED]
Subject: (RADIATOR) dictionary issue - log complains of missing values
radiator 2.17.1
mysql 3.22.32
cisco 5300
for almost every single call, i get the following error in my
log file:
22/01/2001 23:24
t: Tuesday, January 23, 2001 9:45 AM
To: [EMAIL PROTECTED]
Subject: (RADIATOR) dictionary issue - log complains of missing values
radiator 2.17.1
mysql 3.22.32
cisco 5300
for almost every single call, i get the following error in my
log file:
22/01/2001 23:24
On Wed, 24 Jan 2001, Hugh Irvine wrote:
The best way to deal with this is in a hook, in which you would do
the additional processing to check any cisco-h323... attribute and
correct the value to be in the format that the dictionary expects.
i have a couple of friends at cisco, one of
On Wed, 24 Jan 2001, Hugh Irvine wrote:
Hello Ken, Hello Dave -
The best way to deal with this is in a hook, in which you would do
the additional processing to check any cisco-h323... attribute and
correct the value to be in the format that the dictionary expects.
terriblly gross, but
PROTECTED]'
Subject: (RADIATOR) Dictionary for Cisco Voip VSAs ??
I asked once before if anyone knew where to find the
dictionary for Cisco's
Voip VSA's, and no one replied.
So, I'm asking once more, since if no one replies by tomorrow, I will
probably have to type it all in myself
Can anyone tell me how to fix this...
Mon Jan 8 13:52:16 2001: ERR: Attribute number 121 (vendor ) is not
defined in
your dictionary
I get these over and over. We use Platypus (ODBC) to connect to the
User Database
Thank you,
Eric Elliston
Network Administrator
--Neosmart.com
What dictionary are you using?
This definition is from the standard Radiator dictionary (which you can just
cut and paste into whatever dictionary you are using).
ATTRIBUTE Ascend-Modem-SlotNo 121 integer
hth
Hugh
--
Radiator: the most portable, flexible
Does anyone know where I can get the Dictionary.ascend2 file???
Thanks
Eric
===
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.
Hello Eric -
On Thursday 28 December 2000 10:28, Eric Elliston wrote:
Does anyone know where I can get the Dictionary.ascend2 file???
All of the dictionary files are included in the distribution main directory.
BTW - the latest version of Radiator is 2.17.1.
regards
Hugh
--
Radiator:
Hello,
Is there a way to define a
dictionary for two different config files? So whenI have 'include
this.cfg' to the end of the primary config file it will use the dictionary
included in 'this.cfg'?
Thanks,
Cliff
nasreq-ext-radiuspract-01.txt
This document also refers to the manufacturer as the source for the Radius
attributes.
However, the standard Radiator dictionary should already have most of what you
need, and if you need to add any attributes it is very simple with any text
editor. You might also post
dictionary
-Original Message-
From: Hugh Irvine [SMTP:[EMAIL PROTECTED]]
Sent: Miércoles 10 de Mayo de 2000 19:06
To: Cortney Thompson; [EMAIL PROTECTED]
Subject: Re: (RADIATOR) Dictionary Blues
Hello Cortney -
On Thu, 11 May 2000, Cortney Thompson wrote:
I have been
529) is
not defined in your dictionary
-Original Message-
From: Hugh Irvine [SMTP:[EMAIL PROTECTED]]
Sent: Miércoles 10 de Mayo de 2000 19:06
To: Cortney Thompson; [EMAIL PROTECTED]
Subject: Re: (RADIATOR) Dictionary Blues
Hello Cortney -
On Thu, 11 May 2000
Hello Cortney -
On Thu, 11 May 2000, Cortney Thompson wrote:
I have been doing testing with Radiator proxy, and I just recently started
to get the following errors every time someone tries to log in. Has anyone
seen this before. I am using the dictionary.ascend2.
Wed May 10 00:22:28
Hi,
I'm logging all connections on a MSSQL server. But i'm trying to log the
integer value instead of the text associated with him in the dictionary
file. My ideal was to comment the VALUE lines of the dictionary file.
Will it work? If not, does anybody have any hint?
E.G.:
Original Dictionary
Hello Guilherme -
On Wed, 17 Nov 1999, Guilherme Maranhão wrote:
Hi,
I'm logging all connections on a MSSQL server. But i'm trying to log the
integer value instead of the text associated with him in the dictionary
file. My ideal was to comment the VALUE lines of the dictionary file.
Will
WIth the Lucent PM3's the standard dictionary seems to work fine, but the
std dictionary gives errors with Cisco 5200's:
Fri Jun 25 08:18:10 1999: ERR: Attribute number 195 (vendor ) is not
defined in your dictionary
Fri Jun 25 08:18:10 1999: ERR: Attribute number 190 (vendor ) is not
defined in
Hello,
We are getting two different sets of data for connection speed
from radiator and merit radius. here is an example.
Merit radius:
Tue Jun 15 15:23:55 1999
User-Name = "core77"
NAS-IP-Address = 207.240.142.3
Acct-Status-Type = Start
Hi Oliver,
I suspect this is related to the USR attribute numbering issues discussed in
the Radiator FAQ at http://www.open.com.au/radiator/faq.html#29
Hope that helps.
Cheers.
On Jun 15, 5:37pm, O Stockhammer wrote:
Subject: (RADIATOR) (Radiator) dictionary files for USR seem off.
Hello
Hi Lon,
On Mar 19, 12:52pm, Lon R. Stockton, Jr. wrote:
Subject: (RADIATOR) dictionary to use?
A recent reply to the list made me question my choice of dictionary.
I've got USR TC gear, and just assumed that I needed to be using the
"dictionary.usr" file. So I did, an
56 matches
Mail list logo
