Re: [RADIATOR] ERR: Attribute number 101

2010-06-29 Thread Adam Gerson
They sent me: # Bluesocket vendor specific VENDOR BLUESOCKET 9967 ATTRIBUTE BlueSocketRole 100 string BLUESOCKET ATTRIBUTE Bluesocketap101 string BLUESOCK I see from the examples VENDORATTR, should it be changed to: # Bluesocket vendor specific VENDOR BL

Re: [RADIATOR] ERR: Attribute number 101

2010-06-25 Thread Hugh Irvine
Hello Adam - The dictionary is the file that contains all of the RADIUS attribute definitions for the standard set plus all the vendor specifics. The error you show is due to a missing vendor-specific for vendor 9967 which is listed as Bluesocket. You should ask Bluesocket for their vendor-sp

Re: [RADIATOR] ERR: Attribute number 101

2010-06-25 Thread Kurt Jaeger
Hi! > Bluesocket is what we use. > > What is a radius dictionary and whats it used for? What would I do with > it once I got it? Radius packets are binary encodings of Type-Key-Value attribute sets. There are standard radius attributes and there are enterprise (vendor) specific attributes. The

Re: [RADIATOR] ERR: Attribute number 101

2010-06-25 Thread Adam Gerson
Bluesocket is what we use. What is a radius dictionary and whats it used for? What would I do with it once I got it? Adam -- Adam Gerson Assistant Director of Technology Columbia Grammar and Prep School phone. 212-749-6200 ex. 321 fax. 212-428-6806 ager...@cgps.org http://www.cgps.org On 6/

[RADIATOR] ERR: Attribute number 101

2010-06-25 Thread Adam Gerson
I see this a lot in my logs. Is that a problem? Fri Jun 25 00:07:45 2010: ERR: Attribute number 101 (vendor 9967) is not defined in your dictionary Fri Jun 25 00:34:45 2010: ERR: Attribute number 101 (vendor 9967) is not defined in your dictionary Fri Jun 25 01:00:46 2010: ERR: Attribute numbe