Is there support for Sub-TLV attributes currently and if so, can someone point me to documentation on how to format a reply for them? David
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.net@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
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.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@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.net@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
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.lists@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.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@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.net@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
<snip> 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? <snip> If you're concerned about disclosing some proprietary thing, you can obviously tweak the dictionaries, code, etc. as necessary to meet your needs. You don't need to publish those tweaks except where required by any licenses, EULA's, etc. <font size="1"> <div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'> </div> "This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system." </font>
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.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@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.lists@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.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@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.net@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
OK its becoming clearer. It appears as though the vendor slightly modified WiMAX NWG Stage 3 Rel.1.3.0. I see that the dictionary file is NWG_R1_V1.2.1-Stage-3.pdf. Is there a newer version with the Rel. 1.3.0 attributes? David -----Original Message----- From: Ben Wiechman [mailto:wiechman.lists@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.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@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.lists@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.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@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.net@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
David Peterson wrote:
OK its becoming clearer. It appears as though the vendor slightly modified WiMAX NWG Stage 3 Rel.1.3.0. I see that the dictionary file is NWG_R1_V1.2.1-Stage-3.pdf. Is there a newer version with the Rel. 1.3.0 attributes?
Sure, send a patch. I fail to understand why people ask questions like this. Do you think there's some secret repository of dictionaries that *don't* get shipped with the server, and you have to ask for them? Alan DeKok.
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.lists@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.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@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.lists@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.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@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.net@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
Let me append this (with corrected proper syntax), the issue is not one sub-tlv but one sub and one sub-sub-tlv ATTRIBUTE TLV-1 1 tlv BEGIN-TLV TLV-1 ATTRIBUTE SUBTLV1 1 tlv BEGIN-TLV SUBTLV1 ATTRIBUTE SUB-SUB-TLV 1 tlv BEGIN-TLV SUB-SUB-TLV1 END-TLV SUB-SUB-TLV END-TLV SUBTLV1 END-TLV TLV1 -----Original Message----- 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: Friday, January 14, 2011 11:50 AM To: FreeRadius users mailing list Subject: RE: Sub-TLV's 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.lists@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.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@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.lists@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.com@lists.freeradius.org [mailto:freeradius-users- bounces+wiechman.lists=gmail.com@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.net@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
David Peterson wrote:
Let me append this (with corrected proper syntax), the issue is not one sub-tlv but one sub and one sub-sub-tlv
ATTRIBUTE TLV-1 1 tlv BEGIN-TLV TLV-1 ATTRIBUTE SUBTLV1 1 tlv BEGIN-TLV SUBTLV1 ATTRIBUTE SUB-SUB-TLV 1 tlv BEGIN-TLV SUB-SUB-TLV1 END-TLV SUB-SUB-TLV END-TLV SUBTLV1 END-TLV TLV1
Sub-TLVs are only supported for WiMAX. If you're updating a WiMAX dictionary, post it here so everyone else can use it. If it's a secret dictionary that you're not willing to share, then we have no reason to share, either. Go fix it yourself. Alan DeKok.
Understood. Here is the dictionary I am working with: The changes start at line 168. # -*- text -*- ############################################################################ ## # # WiMAX Forum # # Updated from NWG_R1_V1.2.1-Stage-3.pdf # # NWG_R1_V1.2-Stage-3.pdf # RADIUS discussion is on pp. 432-498 # WiMAX VSA's are on p. 450 and following. # # DHCP && MIP keys are on p.48 and following. # # WiMAX VSA's have a non-standard format: # # type 1 octet # length 1 octet # continuation 1 octet 0bcrrrrrrr # value 1+ octets # # If the high bit of the "continuation" field is set, then # the next attribute of the same WiMAX type should have it's # value concatenated to this one. # # The C bit MUST be zero for all small types. e.g. integer, # ipaddr, ipv6addr, etc. It MAY be set for "string" and "octet" # types. The maximum attribute length for "string" and "octet" # types is still 253 bytes, even with continuations. The WiMAX # specifications do not specify a maximum length, so we have chosen # to keep the traditional RADIUS maximum length here. # # The C bit MAY be 1 for TLV types. There is no restriction on # TLV length other than maximum packet size (a bit less than 4K). # # The rest of the bits in the "continuation" octet are reserved, # and MUST be zero. # # Each WiMAX VSA is packed into one Vendor-Specific attribute # with Vendor-Id of WiMAX. Multiple WiMAX sub-TLV's ARE packed # into one VSA with an encapsulating TLV. # # The WiMAX forum adds the following (non-standard) data types: # # byte - one-octet unsigned integer # short - two-octet unsigned integer in network byte order # signed - 4-octet signed integer in network byte order. # combo-ip - if length 4, is the same as the "ipaddr" type. # if length 16, is the same as "ipv6addr" type. # tlv - encapsulated sub-attributes # i.e. Vendor-Specific -> WiMAX TLV -> WiMAX sub-tlv. # ############################################################################ ## # # $Id$ # ############################################################################ ## VENDOR WiMAX 24757 format=1,1,c BEGIN-VENDOR WiMAX ATTRIBUTE WiMAX-Capability 1 tlv BEGIN-TLV WiMAX-Capability ATTRIBUTE WiMAX-Release 1 string ATTRIBUTE WiMAX-Accounting-Capabilities 2 byte ATTRIBUTE WiMAX-Hotlining-Capabilities 3 byte ATTRIBUTE WiMAX-Idle-Mode-Notification-Cap 4 byte # This is really a bitmap VALUE WiMAX-Accounting-Capabilities No-Accounting 0 VALUE WiMAX-Accounting-Capabilities IP-Session-Based 1 VALUE WiMAX-Accounting-Capabilities Flow-Based 2 # This is really a bitmap VALUE WiMAX-Hotlining-Capabilities Not-Supported 0 VALUE WiMAX-Hotlining-Capabilities Hotline-Profile-Id 1 VALUE WiMAX-Hotlining-Capabilities NAS-Filter-Rule 2 VALUE WiMAX-Hotlining-Capabilities HTTP-Redirection 4 VALUE WiMAX-Hotlining-Capabilities IP-Redirection 8 VALUE WiMAX-Idle-Mode-Notification-Cap Not-Supported 0 VALUE WiMAX-Idle-Mode-Notification-Cap Supported 1 END-TLV WiMAX-Capability ATTRIBUTE WiMAX-Device-Authentication-Indicator 2 byte ATTRIBUTE WiMAX-GMT-Timezone-offset 3 signed ATTRIBUTE WiMAX-AAA-Session-Id 4 octets # 32 octets in length ATTRIBUTE WiMAX-MSK 5 octets encrypt=2 ATTRIBUTE WiMAX-hHA-IP-MIP4 6 ipaddr ATTRIBUTE WiMAX-hHA-IP-MIP6 7 ipv6addr ATTRIBUTE WiMAX-DHCPv4-Server 8 combo-ip ATTRIBUTE WiMAX-DHCPv6-Server 9 combo-ip # MN-HA-CMIP4 = H(MIP-RK, "CMIP4 MN HA" | HA-IPv4 | MN-NAI), or # MN-HA-PMIP4 = H(MIP-RK, "PMIP4 MN HA" | HA-IPv4 | MN-NAI) ATTRIBUTE WiMAX-MN-hHA-MIP4-Key 10 octets encrypt=2 # MN-HA-CMIP4-SPI == MIP-SPI, or # MN-HA-PIMP4-SPI == MIP-SPI + 1 ATTRIBUTE WiMAX-MN-hHA-MIP4-SPI 11 integer # MN-HA-CMIP6 = H(MIP-RK, "CMIP6 MN HA" | HA-IPv6 | MN-NAI) ATTRIBUTE WiMAX-MN-hHA-MIP6-Key 12 octets encrypt=2 # MN-HA-CMIP6-SPI == MIP-SPI + 2 ATTRIBUTE WiMAX-MN-hHA-MIP6-SPI 13 integer # FA-RK = H(MIP-RK, "FA-RK") ATTRIBUTE WiMAX-FA-RK-Key 14 octets encrypt=2 # 160 bit random number ATTRIBUTE WiMAX-HA-RK-Key 15 octets encrypt=2 # SPI-CMIP4 ATTRIBUTE WiMAX-HA-RK-SPI 16 integer ATTRIBUTE WiMAX-HA-RK-Lifetime 17 integer # The same as MN-HA-CMIP4, etc. But in different packets. ATTRIBUTE WiMAX-RRQ-HA-IP 18 combo-ip ATTRIBUTE WiMAX-RRQ-MN-HA-Key 19 octets encrypt=2 ATTRIBUTE WiMAX-RRQ-MN-HA-SPI 20 integer ATTRIBUTE WiMAX-Session-Continue 21 integer ATTRIBUTE WiMAX-Beginning-Of-Session 22 integer ATTRIBUTE WiMAX-IP-Technology 23 integer VALUE WiMAX-IP-Technology Reserved-0 0 VALUE WiMAX-IP-Technology Reserved-1 1 VALUE WiMAX-IP-Technology PMIP4 2 VALUE WiMAX-IP-Technology CMIP4 3 VALUE WiMAX-IP-Technology CMIP6 4 VALUE WiMAX-IP-Technology Ethernet-CS 5 ATTRIBUTE WiMAX-Hotline-Indicator 24 string ATTRIBUTE WiMAX-Prepaid-Indicator 25 byte ATTRIBUTE WiMAX-PDFID 26 short ATTRIBUTE WiMAX-SDFID 27 short ATTRIBUTE WiMAX-Packet-Flow-Descriptor 28 tlv BEGIN-TLV WiMAX-Packet-Flow-Descriptor ATTRIBUTE WiMAX-Packet-Data-Flow-Id 1 short ATTRIBUTE WiMAX-Service-Data-Flow-Id 2 short ATTRIBUTE WiMAX-Service-Profile-Id 3 integer ATTRIBUTE WiMAX-Direction 4 byte VALUE WiMAX-Direction Reserved-0 0 VALUE WiMAX-Direction Uplink 1 VALUE WiMAX-Direction Downlink 2 VALUE WiMAX-Direction Bi-Directional 3 ATTRIBUTE WiMAX-Activation-Trigger 5 byte # bitmap ATTRIBUTE WiMAX-Transport-Type 6 byte VALUE WiMAX-Transport-Type Reserved-0 0 VALUE WiMAX-Transport-Type IPv4-CS 1 VALUE WiMAX-Transport-Type IPv6-CS 2 VALUE WiMAX-Transport-Type Ethernet 3 ATTRIBUTE WiMAX-Uplink-QOS-Id 7 byte ATTRIBUTE WiMAX-Downlink-QOS-Id 8 byte ATTRIBUTE WiMAX-Uplink-Classifier 9 string ATTRIBUTE WiMAX-Downlink-Classifier 10 string ATTRIBUTE WiMAX-Classifier 11 tlv BEGIN-TLV WiMAX-Classifier ATTRIBUTE WiMAX-ClassifierID 1 integer ATTRIBUTE WiMAX-Classifer-Priority 2 integer ATTRIBUTE WiMAX-Classifer-Protocol 3 integer ATTRIBUTE WiMAX-Classifer-Direction 4 byte VALUE WiMAX-Classifer-Direction Reserved-0 0 VALUE WiMAX-Classifer-Direction IN 1 VALUE WiMAX-Classifer-Direction OUT 2 VALUE WiMAX-Classifer-Direction Bi-Directional 3 VALUE WiMAX-Classifer-Direction FF 4 ATTRIBUTE WiMAX-Source-Specification 5 tlv BEGIN-TLV WiMAX-Source-Specification ATTRIBUTE WiMAX-Source-IPAddress 1 ipaddr ATTRIBUTE WiMAX-Source-IPAddressRange 2 combo-ip ATTRIBUTE WiMAX-Source-IPAddressMask 3 octets ATTRIBUTE WiMAX-Source-Port 4 octets ATTRIBUTE WiMAX-Source-Port-Range 5 octets ATTRIBUTE WiMAX-Source-Inverted 6 octets ATTRIBUTE WiMAX-Source-Assigned 7 octets END-TLV WiMAX-Source-Specification ATTRIBUTE WiMAX-Destination-Specification 6 tlv BEGIN-TLV WiMAX-Destination-Specification ATTRIBUTE WiMAX-Destination-IPAddress 1 ipaddr ATTRIBUTE WiMAX-Destination-IPAddressRange 2 combo-ip ATTRIBUTE WiMAX-Destination-IPAddressMask 3 octets ATTRIBUTE WiMAX-Destination-Port 4 octets ATTRIBUTE WiMAX-Destination-Port-Range 5 octets ATTRIBUTE WiMAX-Destination-Inverted 6 octets ATTRIBUTE WiMAX-Destination-Assigned 7 octets END-TLV WiMAX-Destination-Specification ATTRIBUTE WiMAX-IP-TOS/DSCP-Range-and-Mask 7 octets ATTRIBUTE WiMAX-VLAN-ID 8 integer ATTRIBUTE WiMAX-802.1p 9 octets END-TLV WiMAX-Classifier END-TLV WiMAX-Packet-Flow-Descriptor ATTRIBUTE WiMAX-QoS-Descriptor 29 tlv BEGIN-TLV WiMAX-QoS-Descriptor ATTRIBUTE WiMAX-QoS-Id 1 byte ATTRIBUTE WiMAX-Global-Service-Class-Name 2 string # 6 octets ATTRIBUTE WiMAX-Service-Class-Name 3 string ATTRIBUTE WiMAX-Schedule-Type 4 byte ATTRIBUTE WiMAX-Traffic-Priority 5 byte ATTRIBUTE WiMAX-Maximum-Sustained-Traffic-Rate 6 integer ATTRIBUTE WiMAX-Minimum-Reserved-Traffic-Rate 7 integer ATTRIBUTE WiMAX-Maximum-Traffic-Burst 8 integer ATTRIBUTE WiMAX-Tolerated-Jitter 9 integer ATTRIBUTE WiMAX-Maximum-Latency 10 integer ATTRIBUTE WiMAX-Reduced-Resources-Code 11 byte ATTRIBUTE WiMAX-Media-Flow-Type 12 byte ATTRIBUTE WiMAX-Unsolicited-Grant-Interval 13 short ATTRIBUTE WiMAX-SDU-Size 14 short ATTRIBUTE WiMAX-Unsolicited-Polling-Interval 15 short ATTRIBUTE WiMAX-Media-Flow-Description-SDP 16 string ATTRIBUTE WiMAX-R3-IF-Descriptor 17 tlv BEGIN-TLV WiMAX-R3-IF-Descriptor ATTRIBUTE WiMAX-R3-IF-Name 1 string ATTRIBUTE WiMAX-R3-IF-ID 2 octets # ATTRIBUTE WiMAX-PDFID 3 short ATTRIBUTE WiMAX-IPv4-addr 4 ipaddr ATTRIBUTE WiMAX-IPv4-Netmask 5 ipaddr ATTRIBUTE WiMAX-DGW-IPv4-addr 6 ipaddr END-TLV WiMAX-R3-IF-Descriptor ATTRIBUTE WiMAX-DHCP-Option 18 tlv BEGIN-TLV WiMAX-DHCP-Option ATTRIBUTE WiMAX-Ref-R3-IF-Name 1 string ATTRIBUTE WiMAX-DHCP-Option-Container 2 string END-TLV WiMAX-DHCP-Option VALUE WiMAX-Schedule-Type Best-Effort 2 VALUE WiMAX-Schedule-Type nrtPS 3 VALUE WiMAX-Schedule-Type rtPS 4 VALUE WiMAX-Schedule-Type Extended-rtPS 5 VALUE WiMAX-Schedule-Type UGS 6 VALUE WiMAX-Media-Flow-Type VoIP 1 VALUE WiMAX-Media-Flow-Type Robust-Browser 2 VALUE WiMAX-Media-Flow-Type Secure-Browser-VPN 3 VALUE WiMAX-Media-Flow-Type Streaming-Video 4 VALUE WiMAX-Media-Flow-Type Streaming-Live-TV 5 VALUE WiMAX-Media-Flow-Type Music-Photo-Download 6 VALUE WiMAX-Media-Flow-Type Multi-Player-Gaming 7 VALUE WiMAX-Media-Flow-Type Location-Based-Services 8 VALUE WiMAX-Media-Flow-Type Text-Audio-Books 9 VALUE WiMAX-Media-Flow-Type Video-Conversation 10 VALUE WiMAX-Media-Flow-Type Message 11 VALUE WiMAX-Media-Flow-Type Control 12 VALUE WiMAX-Media-Flow-Type Data 13 END-TLV WiMAX-QoS-Descriptor ATTRIBUTE WiMAX-Uplink-Granted-QoS 30 string ATTRIBUTE WiMAX-Control-Packets-In 31 integer ATTRIBUTE WiMAX-Control-Octets-In 32 integer ATTRIBUTE WiMAX-Control-Packets-Out 33 integer ATTRIBUTE WiMAX-Control-Octets-Out 34 integer ATTRIBUTE WiMAX-PPAC 35 tlv BEGIN-TLV WiMAX-PPAC ATTRIBUTE WiMAX-Available-In-Client 1 integer # Really a bitmap VALUE WiMAX-Available-In-Client Volume-Metering 1 VALUE WiMAX-Available-In-Client Duration-Metering 2 VALUE WiMAX-Available-In-Client Resource-Metering 4 VALUE WiMAX-Available-In-Client Pools 8 VALUE WiMAX-Available-In-Client Rating-Groups 0x10 VALUE WiMAX-Available-In-Client Multi-Services 0x20 VALUE WiMAX-Available-In-Client Tariff-Switch 0x40 END-TLV WiMAX-PPAC ATTRIBUTE WiMAX-Session-Termination-Capability 36 integer # Really a bitmap VALUE WiMAX-Session-Termination-Capability Dynamic-Authorization 1 ATTRIBUTE WiMAX-PPAQ 37 tlv BEGIN-TLV WiMAX-PPAQ ATTRIBUTE WiMAX-PPAQ-Quota-Identifier 1 octets ATTRIBUTE WiMAX-Volume-Quota 2 integer #kb ATTRIBUTE WiMAX-Volume-Threshold 3 integer #kb ATTRIBUTE WiMAX-Duration-Quota 4 integer #s ATTRIBUTE WiMAX-Duration-Threshold 5 integer #s ATTRIBUTE WiMAX-Resource-Quota 6 integer ATTRIBUTE WiMAX-Resource-Threshold 7 integer ATTRIBUTE WiMAX-Update-Reason 8 integer ATTRIBUTE WiMAX-Prepaid-Server 9 combo-ip ATTRIBUTE WiMAX-Service-Id 10 string ATTRIBUTE WiMAX-Rating-Group-Id 11 integer ATTRIBUTE WiMAX-Termination-Action 12 byte ATTRIBUTE WiMAX-Pool-Id 13 integer ATTRIBUTE WiMAX-Pool-Multiplier 14 integer ATTRIBUTE WiMAX-Requested-Action 15 byte ATTRIBUTE WiMAX-Check-Balance-Result 16 byte # # 4 octets - integer representing 1/10's of lowest currency (e.g. cents) # 4 octets - currency code as in ISO-4217 # 1+ - UTF8 string containing text like "cost is $1 per minute" # ATTRIBUTE WiMAX-Cost-Information-AVP 17 octets VALUE WiMAX-Update-Reason Pre-Initialization 1 VALUE WiMAX-Update-Reason Initial-Request 2 VALUE WiMAX-Update-Reason Threshold-Reached 3 VALUE WiMAX-Update-Reason Quota-Reached 4 VALUE WiMAX-Update-Reason TITSU-Approaching 5 VALUE WiMAX-Update-Reason Remote-Forced-Disconnect 6 VALUE WiMAX-Update-Reason Client-Service-Termination 7 VALUE WiMAX-Update-Reason Access-Service-Terminated 8 VALUE WiMAX-Update-Reason Service-Not-Established 9 VALUE WiMAX-Update-Reason One-Time-Charging 10 VALUE WiMAX-Termination-Action Terminate 1 VALUE WiMAX-Termination-Action Request-More-Quota 2 VALUE WiMAX-Termination-Action Redirect-Or-Filter 3 VALUE WiMAX-Requested-Action Balance-Check 1 VALUE WiMAX-Requested-Action Price-Enquiry 2 END-TLV WiMAX-PPAQ ATTRIBUTE WiMAX-Prepaid-Tariff-Switching 38 tlv BEGIN-TLV WiMAX-Prepaid-Tariff-Switching ATTRIBUTE WiMAX-Prepaid-Quota-Identifier 1 string ATTRIBUTE WiMAX-Volume-Used-After 2 integer #1k ATTRIBUTE WiMAX-Tariff-Switch-Interval 3 integer #s ATTRIBUTE WiMAX-Time-Interval-After 4 integer #s END-TLV WiMAX-Prepaid-Tariff-Switching ATTRIBUTE WiMAX-Active-Time-Duration 39 integer ATTRIBUTE WiMAX-DHCP-RK 40 octets encrypt=2 ATTRIBUTE WiMAX-DHCP-RK-Key-Id 41 integer ATTRIBUTE WiMAX-DHCP-RK-Lifetime 42 integer ATTRIBUTE WiMAX-DHCP-Msg-Server-IP 43 ipaddr ATTRIBUTE WiMAX-Idle-Mode-Transition 44 byte ATTRIBUTE WiMAX-NAP-Id 45 octets # 3 octets of NAP Id # 3 octets of base-station Id ATTRIBUTE WiMAX-BS-Id 46 octets ATTRIBUTE WiMAX-Location 47 octets # Number of times Acct-Input-Packets rolled over 2^32. ATTRIBUTE WiMAX-Acct-Input-Packets-Gigaword 48 integer ATTRIBUTE WiMAX-Acct-Output-Packets-Gigaword 49 integer # Formatted as per IP Filter rule specification. ATTRIBUTE WiMAX-Uplink-Flow-Description 50 string ATTRIBUTE WiMAX-Blu-Coa-IPv6 51 ipv6addr ATTRIBUTE WiMAX-DNS-Server 52 combo-ip ATTRIBUTE WiMAX-Hotline-Profile-Id 53 string # Formatted as per IP Filter rule specification. ATTRIBUTE WiMAX-HTTP-Redirection-Rule 54 string # Formatted as per IP Filter rule specification. ATTRIBUTE WiMAX-IP-Redirection-Rule 55 string ATTRIBUTE WiMAX-Hotline-Session-Timer 56 integer # 3 octets ATTRIBUTE WiMAX-NSP-Id 57 octets ATTRIBUTE WiMAX-HA-RK-Key-Requested 58 integer VALUE WiMAX-HA-RK-Key-Requested No 0 VALUE WiMAX-HA-RK-Key-Requested Yes 1 ATTRIBUTE WiMAX-Count-Type 59 byte ATTRIBUTE WiMAX-DM-Action-Code 60 integer VALUE WiMAX-DM-Action-Code Deregister-MS 0 VALUE WiMAX-DM-Action-Code Suspend-MS-Traffic 1 VALUE WiMAX-DM-Action-Code Suspend-User-Traffic 2 VALUE WiMAX-DM-Action-Code Resume-Traffic 3 VALUE WiMAX-DM-Action-Code MS-Terminate 4 VALUE WiMAX-DM-Action-Code MS-Idle 5 VALUE WiMAX-DM-Action-Code MS-Completed-IPv6-Handover 6 VALUE WiMAX-DM-Action-Code BS-Sends-RES-Cmd 0xffff # FA-RK-SPI = SPI-CMIP4 = MIP-SPI ATTRIBUTE WiMAX-FA-RK-SPI 61 integer # Formatted as per IP Filter rule specification. ATTRIBUTE WiMAX-Downlink-Flow-Description 62 string # Same as QoS-Descriptor... dang. ATTRIBUTE WiMAX-Downlink-Granted-QoS 63 tlv # More MIP keys, calculated as above... but in different packets. # Why, oh why? ATTRIBUTE WiMAX-vHA-IP-MIP4 64 ipaddr ATTRIBUTE WiMAX-vHA-IP-MIP6 65 ipv6addr ATTRIBUTE WiMAX-vHA-MIP4-Key 66 octets encrypt=2 ATTRIBUTE WiMAX-vHA-RK-Key 67 octets encrypt=2 ATTRIBUTE WiMAX-vHA-RK-SPI 68 integer ATTRIBUTE WiMAX-vHA-RK-Lifetime 69 integer ATTRIBUTE WiMAX-MN-vHA-MIP6-Key 70 octets encrypt=2 ATTRIBUTE WiMAX-MN-vHA-MIP4-SPI 71 integer ATTRIBUTE WiMAX-MN-vHA-MIP6-SPI 72 integer ATTRIBUTE WiMAX-vDHCPv4-Server 73 ipaddr ATTRIBUTE WiMAX-vDHCPv6-Server 74 ipv6addr ATTRIBUTE WiMAX-vDHCP-RK 75 octets encrypt=2 ATTRIBUTE WiMAX-vDHCP-RK-Key-ID 76 integer ATTRIBUTE WiMAX-vDHCP-RK-Lifetime 77 integer -----Original Message----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: Friday, January 14, 2011 5:43 PM To: David Peterson-WirelessConnections; FreeRadius users mailing list Subject: Re: Sub-TLV's David Peterson wrote:
Let me append this (with corrected proper syntax), the issue is not one sub-tlv but one sub and one sub-sub-tlv
ATTRIBUTE TLV-1 1 tlv BEGIN-TLV TLV-1 ATTRIBUTE SUBTLV1 1 tlv BEGIN-TLV SUBTLV1 ATTRIBUTE SUB-SUB-TLV 1 tlv BEGIN-TLV SUB-SUB-TLV1 END-TLV SUB-SUB-TLV END-TLV SUBTLV1 END-TLV TLV1
Sub-TLVs are only supported for WiMAX. If you're updating a WiMAX dictionary, post it here so everyone else can use it. If it's a secret dictionary that you're not willing to share, then we have no reason to share, either. Go fix it yourself. Alan DeKok.
David Peterson wrote:
Understood. Here is the dictionary I am working with:
The changes start at line 168.
Ah. Nested TLV's aren't supported in 2.1.x. Instead, see the git "stable" branch for massive changes to allow all of the WiMAX "goodness". It has many updates to the dictionary parser, a re-written attribute encoder/decoder, unit tests, changed internal API, etc. These are all the required in order to support the nested WiMAX TLVs, and *cannot* be back-ported to 2.1.x. I can add checks for 2.1.11 which produce a more useful error message describing why the dictionary can't be loaded. Alan DeKok.
OK that makes sense. I am using the "Master" branch per the git instructions. I am receiving this error during compile: make[4]: Entering directory `/usr/src/freeradius-server/src/main' /bin/sh /usr/src/freeradius-server/libtool --mode=compile gcc -g -O2 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wall -D_GNU_SOURCE -g -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -W -Wredundant-decls -Wundef -I/usr/src/freeradius-server/src -DHOSTINFO=\"i686-pc-linux-gnu\" -DRADIUSD_VERSION=\"2.4.0\" -DOPENSSL_NO_KRB5 -c auth.c libtool: compile: gcc -g -O2 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -Wall -D_GNU_SOURCE -g -Wshadow -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -W -Wredundant-decls -Wundef -I/usr/src/freeradius-server/src -DHOSTINFO=\"i686-pc-linux-gnu\" -DRADIUSD_VERSION=\"2.4.0\" -DOPENSSL_NO_KRB5 -c auth.c -fPIC -DPIC -o .libs/auth.o In file included from /usr/src/freeradius-server/src/freeradius-devel/radiusd.h:107, from auth.c:28: /usr/src/freeradius-server/src/freeradius-devel/smodule.h:144: error: expected specifier-qualifier-list before 'RADCLIENT' Am I using the right code? David -----Original Message----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: Monday, January 17, 2011 11:26 AM To: David Peterson-WirelessConnections; FreeRadius users mailing list Subject: Re: Sub-TLV's David Peterson wrote:
Understood. Here is the dictionary I am working with:
The changes start at line 168.
Ah. Nested TLV's aren't supported in 2.1.x. Instead, see the git "stable" branch for massive changes to allow all of the WiMAX "goodness". It has many updates to the dictionary parser, a re-written attribute encoder/decoder, unit tests, changed internal API, etc. These are all the required in order to support the nested WiMAX TLVs, and *cannot* be back-ported to 2.1.x. I can add checks for 2.1.11 which produce a more useful error message describing why the dictionary can't be loaded. Alan DeKok.
OK figured out the "Stable" thing and have it compiled and running. I like the changes in the dictionary.wimax file, but one question. How can I add the following: To: ATTRIBUTE WiMAX-Packet-Flow-Descriptor 28 tlv: (note that the numbering is per the previous dictionary.wimax) ATTRIBUTE WiMAX-Classifier 11 tlv BEGIN-TLV WiMAX-Classifier ATTRIBUTE WiMAX-ClassifierID 1 integer ATTRIBUTE WiMAX-Classifer-Priority 2 integer ATTRIBUTE WiMAX-Classifer-Protocol 3 integer ATTRIBUTE WiMAX-Classifer-Direction 4 byte VALUE WiMAX-Classifer-Direction Reserved-0 0 VALUE WiMAX-Classifer-Direction IN 1 VALUE WiMAX-Classifer-Direction OUT 2 VALUE WiMAX-Classifer-Direction Bi-Directional 3 VALUE WiMAX-Classifer-Direction FF 4 ATTRIBUTE WiMAX-Source-Specification 5 tlv BEGIN-TLV WiMAX-Source-Specification ATTRIBUTE WiMAX-Source-IPAddress 1 ipaddr ATTRIBUTE WiMAX-Source-IPAddressRange 2 combo-ip ATTRIBUTE WiMAX-Source-IPAddressMask 3 octets ATTRIBUTE WiMAX-Source-Port 4 octets ATTRIBUTE WiMAX-Source-Port-Range 5 octets ATTRIBUTE WiMAX-Source-Inverted 6 octets ATTRIBUTE WiMAX-Source-Assigned 7 octets END-TLV WiMAX-Source-Specification ATTRIBUTE WiMAX-Destination-Specification 6 tlv BEGIN-TLV WiMAX-Destination-Specification ATTRIBUTE WiMAX-Destination-IPAddress 1 ipaddr ATTRIBUTE WiMAX-Destination-IPAddressRange 2 combo-ip ATTRIBUTE WiMAX-Destination-IPAddressMask 3 octets ATTRIBUTE WiMAX-Destination-Port 4 octets ATTRIBUTE WiMAX-Destination-Port-Range 5 octets ATTRIBUTE WiMAX-Destination-Inverted 6 octets ATTRIBUTE WiMAX-Destination-Assigned 7 octets END-TLV WiMAX-Destination-Specification ATTRIBUTE WiMAX-IP-TOS/DSCP-Range-and-Mask 7 octets ATTRIBUTE WiMAX-VLAN-ID 8 integer ATTRIBUTE WiMAX-802.1p 9 octets END-TLV WiMAX-Classifier Or would I add the attributes at the end of the file. David -----Original Message----- From: Alan DeKok [mailto:aland@deployingradius.com] Sent: Monday, January 17, 2011 12:52 PM To: David Peterson-WirelessConnections; FreeRadius users mailing list Subject: Re: Sub-TLV's David Peterson wrote:
OK that makes sense. I am using the "Master" branch per the git instructions.
Uh... no. My email said the "stable" branch. I'll get around to fixing the web page and/or git in the next while. Alan DeKok.
David Peterson wrote:
OK figured out the "Stable" thing and have it compiled and running. I like the changes in the dictionary.wimax file, but one question. How can I add the following:
To: ATTRIBUTE WiMAX-Packet-Flow-Descriptor 28 tlv: (note that the numbering is per the previous dictionary.wimax)
ATTRIBUTE WiMAX-Classifier 11 tlv
Use "28.11" instead of "11", because it's a nested TLV.
BEGIN-TLV WiMAX-Classifier
Delete that.
ATTRIBUTE WiMAX-ClassifierID 1 integer
Similarly, use "28.11.1" instead of "1".
ATTRIBUTE WiMAX-Classifer-Priority 2 integer ATTRIBUTE WiMAX-Classifer-Protocol 3 integer ATTRIBUTE WiMAX-Classifer-Direction 4 byte
And so on... "28.11.*"
VALUE WiMAX-Classifer-Direction Reserved-0 0
These are based on names, and don't need to be changed.
VALUE WiMAX-Classifer-Direction IN 1 VALUE WiMAX-Classifer-Direction OUT 2 VALUE WiMAX-Classifer-Direction Bi-Directional 3 VALUE WiMAX-Classifer-Direction FF 4
ATTRIBUTE WiMAX-Source-Specification 5 tlv
Again "28.11.5"
BEGIN-TLV WiMAX-Source-Specification
Delete that.
ATTRIBUTE WiMAX-Source-IPAddress 1 ipaddr
And use "28.11.5.1" instead of "5". Isn't this fun?
Or would I add the attributes at the end of the file.
Add them anywhere. If you use the "dotted number" notation, you don't need begin/end TLVs. Alan DeKok.
participants (4)
-
Alan DeKok -
Ben Wiechman -
David Peterson -
Gary Gatten