I have followed what looks to be the proper format, but I am getting an error:
Errors reading dictionary: dict_init: /usr/local/share/freeradius/dictionary.wimax[209]: END-TLV WiMAX-Classifier does not match any previous BEGIN-TLV Which is very clear, thanks for the awesome debug info. Here is the question: The TLV I am working on has sub-tlv's which has additional sub-tlv's. Am I misreading something or is there a specific method for this scenario: ATTRIBUTE TLV-1 1 tlv BEGIN-TLV1 ATTRIBUTE SUBTLV1 1 tlv BEGIN-SUBTLV1 ATTRIBUTE TLVSOMETHING 1 string END-SUBTLV1 END-TLV1 David -----Original Message----- From: Ben Wiechman [mailto:wiechman.li...@gmail.com] Sent: Wednesday, January 12, 2011 9:13 PM To: David Peterson-WirelessConnections; FreeRadius users mailing list Subject: RE: Sub-TLV's Yes. See /etc/raddb/dictionary There are useful notes in your main dictionary file as well, in RHEL type distros as /usr/share/freeradius/dictionary (or look to see the file that is included under /etc/raddb/dictionary Ben > -----Original Message----- > From: freeradius-users- > bounces+wiechman.lists=gmail....@lists.freeradius.org > [mailto:freeradius-users- > bounces+wiechman.lists=gmail....@lists.freeradius.org] On Behalf Of > David Peterson > Sent: Tuesday, January 11, 2011 10:19 AM > To: FreeRadius users mailing list > Subject: RE: Sub-TLV's > > Let's just say that it appears to be Vendor specific. As I can't > release details, is required to be in a dictionary file in order to > work properly? > > David > > -----Original Message----- > From: Ben Wiechman [mailto:wiechman.li...@gmail.com] > Sent: Tuesday, January 11, 2011 10:36 AM > To: David Peterson-WirelessConnections; FreeRadius users mailing list > Subject: RE: Sub-TLV's > > Quick SQL dump: > > INSERT INTO `radgroupreply` (`id`, `groupname`, `attribute`, `op`, > `value`) > VALUES (208, 'WiMAX_Test3', 'WiMAX-QoS-Id', ':=', '101'), (209, > 'WiMAX_Test3', 'WiMAX-Service-Class-Name', ':=', 'DATA'), (210, > 'WiMAX_Test3', 'WiMAX-Schedule-Type', ':=', 'Best-Effort'), (211, > 'WiMAX_Test3', 'WiMAX-Traffic-Priority', ':=', '1'), (212, > 'WiMAX_Test3', 'WiMAX-Maximum-Sustained-Traffic-Rate', ':=', > '512000'), (213, 'WiMAX_Test3', 'WiMAX-Reduced-Resources-Code', ':=', > '1'), (214, 'WiMAX_Test3', 'WiMAX-QoS-Id', '+=', '102'), (215, > 'WiMAX_Test3', 'WiMAX-Service-Class-Name', '+=', 'DATA'), (216, > 'WiMAX_Test3', 'WiMAX-Schedule-Type', '+=', 'Best-Effort'), (217, > 'WiMAX_Test3', 'WiMAX-Traffic-Priority', '+=', '1'), (218, > 'WiMAX_Test3', 'WiMAX-Maximum-Sustained-Traffic-Rate', '+=', > '400000'), (219, 'WiMAX_Test3', 'WiMAX-Reduced-Resources-Code', '+=', > '1'), (220, 'WiMAX_Test3', 'WiMAX-Packet-Data-Flow-Id', ':=', '21'), > (221, 'WiMAX_Test3', 'WiMAX-Service-Data-Flow-Id', ':=', '21'), (222, > 'WiMAX_Test3', 'WiMAX-Direction', ':=', 'Uplink'), (223, > 'WiMAX_Test3', 'WiMAX-Activation-Trigger', ':=', '15'), (224, > 'WiMAX_Test3', 'WiMAX-Transport-Type', ':=', 'IPv4-CS'), (225, > 'WiMAX_Test3', 'WiMAX-Uplink-QOS-Id', ':=', '101'), (226, > 'WiMAX_Test3', 'WiMAX-Uplink-Classifier', ':=', 'permit in any src any > dst any priority 1'), (227, 'WiMAX_Test3', > 'WiMAX-Packet-Data-Flow-Id', ':=', '22'), (228, 'WiMAX_Test3', > 'WiMAX-Service-Data-Flow-Id', ':=', '22'), (229, 'WiMAX_Test3', > 'WiMAX-Direction', ':=', 'Downlink'), (230, 'WiMAX_Test3', > 'WiMAX-Activation-Trigger', ':=', '15'), (231, 'WiMAX_Test3', > 'WiMAX-Transport-Type', ':=', 'IPv4-CS'), (232, 'WiMAX_Test3', > 'WiMAX-Downlink-QOS-Id', ':=', '102'), (233, 'WiMAX_Test3', > 'WiMAX-Downlink-Classifier', ':=', 'permit in any src any dst any > priority 1'); > > Working example using a Wichorus ASN-GW. > > As Alan said, you can check the dictionary. I'm not familiar with that > TLV so you might have to add it to the dictionary if it is post > Release 1.3. > > Ben > > > -----Original Message----- > > From: freeradius-users- > > bounces+wiechman.lists=gmail....@lists.freeradius.org > > [mailto:freeradius-users- > > bounces+wiechman.lists=gmail....@lists.freeradius.org] On Behalf Of > > David Peterson > > Sent: Tuesday, January 11, 2011 9:26 AM > > To: 'FreeRadius users mailing list' > > Subject: RE: Sub-TLV's > > > > OK perhaps an example of what I need to reply might be in order. I > > have to send a WiMAX TLV WIMAX-Packet-Flow-Descriptor with say all > > four sub- tlv's. > > Would I format the reply as such: > > > > Sub-tlv1 := value > > Subtlv2 += value2 > > > > > > Also, do you know if there is a TLV named R3-IF-Descriptor? I can't > > seem to locate it, it should be a newer WiMAX TLV. > > > > 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 Alan DeKok > > Sent: Tuesday, January 11, 2011 10:08 AM > > To: David Peterson-WirelessConnections; FreeRadius users mailing > > list > > Subject: Re: Sub-TLV's > > > > David Peterson wrote: > > > Is there support for Sub-TLV attributes currently > > > > Some. See dictionary.wimax > > > > > and if so, can someone > > > point me to documentation on how to format a reply for them? > > > > Just use the name, like any other attribute. > > > > Alan DeKok. > > - > > List info/subscribe/unsubscribe? See > > http://www.freeradius.org/list/users.html > > > > - > > List info/subscribe/unsubscribe? See > > http://www.freeradius.org/list/users.html > > > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html