Well, I fixed this issue. The dictionary I had was in wimax format not normal dictionary format. David From: freeradius-users-bounces+david.peterson=acc-corp.net@lists.freeradius.org [mailto:freeradius-users-bounces+david.peterson=acc-corp.net@lists.freeradiu s.org] On Behalf Of David Peterson Sent: Thursday, March 17, 2011 12:22 PM To: FreeRadius users mailing list Cc: Alan DeKok Subject: RE: Sending attribute with sub-attributes What does this tech mean by this? Description: cid:image001.jpg@01CBE4CE.A494EB50 -----Original Message----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: Wednesday, March 16, 2011 5:02 PM To: David Peterson-WirelessConnections; FreeRadius users mailing list Subject: Re: Sending attribute with sub-attributes David Peterson wrote:
After some excellent tutelage from Mr. Wiechman, I am getting
different access-accept. However, it's showing Breezecom attributes
which seem out of place.
edit the "dictionary" file, and delete the "dictionary.alvarion" reference. Also, do "git pull" from the master branch. Some fixes went in today.
Is there another dictionary that is driving the Breezecom-Attr or does
Freeradius just figure out its Alvarion and assign that internally?
Alvarion has ~3 incompatible vendor-specific dictionaries. And each is broken in weird and wonderful ways. Alan DeKok.
