This looks much better to me. Here is the radsniff I see. Let me know if you see anything wrong. Access-Accept Id 125 172.16.4.14:1812 -> 172.16.4.2:1812 +4692.752 Attr-26.12394.1 = 0x76707773 Attr-26.12394.1 = 0x31 WiMAX-Packet-Data-Flow-Id = 1 WiMAX-Direction = Bi-Directional WiMAX-Transport-Type = Ethernet WiMAX-Uplink-QOS-Id = 1 WiMAX-Downlink-QOS-Id = 1 WiMAX-ClassifierID = 2 WiMAX-Classifer-Priority = 1 WiMAX-Classifer-Direction = Bi-Directional WiMAX-VLAN-ID = 100 WiMAX-QoS-Id = 1 WiMAX-Schedule-Type = Best-Effort WiMAX-Traffic-Priority = 3 WiMAX-Maximum-Sustained-Traffic-Rate = 528999 EAP-Message = 0x03080004 Message-Authenticator = 0x44413c890084a6a99bccbccb706db53b User-Name = "{sm=1}1A55E1D4FE74456AA54F73E92B6D1CFA" Attr-26.24757.5 = 0x9338be5f458fe769b4c537a19863e421b558ef983a2d87ff0c7262a32a32f9b1187bd4cd2f 5f961fbb1f34d201a7ab6b4b1c4c91af86040d852d2919e9cfa53de70bb55910d38e0716f0ed e9c8e120788469 The first two attributes come from this file created by Ben W. # -*- text -*- ############################################################################ ## # # Alvarion VSAs for use with Alvarion WiMAX ASN-GW # # This does conflict with the default Alvarion dictionary file included # with FreeRADIUS and may break existing functionality if the current # dictionaries are used to support an existing Alvarion Breezecom or # Breezenet installation. # # $Id$ # ############################################################################ ## VENDOR Alvarion 12394 BEGIN-VENDOR Alvarion ATTRIBUTE Alvarion-R3-IF-Descriptor 1 tlv ATTRIBUTE Alvarion-R3-IF-Name 1.1 string ATTRIBUTE Alvarion-R3-IF-ID 1.2 integer ATTRIBUTE Alvarion-PDFID 1.3 string ATTRIBUTE Alvarion-IPv4-Address 1.4 ipaddr # IPv4 subnet mask plus bit-width mask ATTRIBUTE Alvarion-IPv4-Netmask 1.5 octets ATTRIBUTE Alvarion-DGW-IPv4-Address 1.6 ipaddr # Container for DHCP options delivery in DHCP Proxy mode. ATTRIBUTE Alvarion-DHCP-Option 2 tlv ATTRIBUTE Alvarion-Ref-R3-IF-Name 2.1 string ATTRIBUTE Alvarion-DHCP-Option-Container 2.2 string END-VENDOR Alvarion Is there anything that needs to be coded to support these? David -----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.