I am having issue with this portion of the dictionary. The packet shows as malformed and is for some reason sending two tlv's that seem to be mangled or merged somehow. Here is how I have this portion of my dictionary.wimax setup.
ATTRIBUTE WiMAX-R3-IF-Descriptor 26 tlv ATTRIBUTE WiMAX-R3-IF-Name 26.1 string ATTRIBUTE WiMAX-R3-IF-ID 26.2 octets ATTRIBUTE WiMAX-PDFID 26.3 short ATTRIBUTE WiMAX-IPv4-addr 26.4 ipaddr ATTRIBUTE WiMAX-IPv4-Netmask 26.5 ipaddr ATTRIBUTE WiMAX-DGW-IPv4-addr 26.6 ipaddr ATTRIBUTE WiMAX-DHCP-Option 26.7 tlv ATTRIBUTE WiMAX-Ref-R3-IF-Name 26.7.1 string ATTRIBUTE WiMAX-DHCP-Option-Container 26.7.2 string I am sending WiMAX-R3-IF-Name = "vpws" WiMAX-PDFID = 1 However the length of the attribute seems wrong at least according to wireshark. Any thoughts would be very helpful. David From: freeradius-users-bounces+david.peterson=acc-corp....@lists.freeradius.org [mailto:freeradius-users-bounces+david.peterson=acc-corp.net@lists.freeradiu s.org] On Behalf Of David Peterson Sent: Monday, March 14, 2011 9:58 AM To: FreeRadius users mailing list Subject: RE: Sending attribute with sub-attributes I think I may be getting closer. What should I define this as in the dictionary: TLV ID 1 for Ref-R3-IF-Name TLV Description Reference name to bind the specified DHCP option with the particular R3-IF-Descriptor/ Service Group - specific for Multi-host scenario. Length 2 + Variable Value ASCII string I am currently using "string" and getting an unhandled integer length (which may just be a wireshark issue) David -----Original Message----- From: freeradius-users-bounces+david.peterson=acc-corp....@lists.freeradius.org [mailto:freeradius-users-bounces+david.peterson=acc-corp.net@lists.freeradiu s.org] On Behalf Of David Peterson Sent: Monday, March 14, 2011 9:08 AM To: FreeRadius users mailing list Subject: RE: Sending attribute with sub-attributes AHh ok great! It appears I am on v2.2. Should I be on 3.0 to support the sub-sub tlvs needed for this NAS? David -----Original Message----- From: freeradius-users-bounces+david.peterson=acc-corp....@lists.freeradius.or freeradius-users-bounces+g [mailto:freeradius-users-bounces+david.peterson=acc-corp.net@lists.freeradiu s.org] On Behalf Of Alan DeKok Sent: Monday, March 14, 2011 9:05 AM To: David Peterson-WirelessConnections; FreeRadius users mailing list Subject: Re: Sending attribute with sub-attributes David Peterson wrote: > I am working on the same issue, likely with the same NAS vendor. Is > the order important? Yes. List them in order of attribute number, lowest to highest. Basically, the same order that they are in the dictionary. > I am also seeing some "uknown attributes" in my pcap file. No... the pcap *viewer* you're using doesn't support the WiMAX attributes. This is not surprising. Wireshark grabbed the dictionaries from FreeRADIUS a few years ago, and haven't updated them since. > Perhaps I > am on the wrong build. How do I verify if I am compiling 3.0 version? $ radiusd -v Alan DeKok. - List info/subscribe/unsubscribe? See <http://www.freeradius.org/list/users.html> http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See <http://www.freeradius.org/list/users.html> http://www.freeradius.org/list/users.html
<<attachment: wimax.png>>
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html