(RADIATOR) Attribute Type/Value in dictionary

Frank Danielson fdanielson at csky.com
Tue May 31 12:42:26 CDT 2005


The attribute name such as VendorAttr1 or VendorAttr2 is just there to make
it easier for humans to understand. The actual attribute is sent by number.
If the RADIUS client sends a VSA with vendor id 123456 and attribute number
3 it could have been called anything on the originating end.

There really isn't a dynamic way to build a dictionary but if you see errors
like 

ERR: Attribute number 3 (vendor 123456) is not defined in your dictionary

in you log files the bext way to get rid of them is to add an entry to your
dictionary. It doesn't matter too much what the name is unless you need to
use that attribute for something.

VENDORATTR	123456	Vendor123456_Attribute3			3
string

Frank Danielson
Infrastructure Architect

ClearSky Mobile Media
56 E. Pine St.
Orlando, FL 32801
USA

fdanielson at csky.com

-----Original Message-----
From: Michael Harsh [mailto:Michael.Harsh at billingconcepts.com]
Sent: Tuesday, May 31, 2005 12:36 PM
To: 'radiator at open.com.au'
Subject: (RADIATOR) Attribute Type/Value in dictionary


Hello,

I have a question about defining Attribute values for VSA's in the
dictionary. 

In my experience so far, the VSA values have to be the same in my dictionary
as what another Radius proxy or client has defined for me to be able to
recognize them. For instance, I have a VSA defined in my dictionary as:

VENDORATTR	123456	VendorAttr1			1	string
VENDORATTR	123456	VendorAttr2			2	integer

...and if a proxy or client has them defined as:

VENDORATTR	123456	VendorAttr1			2	string
VENDORATTR	123456	VendorAttr2			3	integer

... I get messages in my log such as:

ERR: Attribute number 3 (vendor 123456) is not defined in your dictionary.

So, my question is, can these Attribute values be defined dynamically so it
doesn't matter to me what a client or downstream proxy has his values
defined as?

Thanks,
Mike

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.


More information about the radiator mailing list