Sub-TLVs how to have the same kind of descriptor twice
Hello, I am running version 3.0.0 and have a question about sub-tlvs: I am looking at: WiMAX-QoS-Descriptor as it is defined in dictionary.wimax.alvarion (the standard dictionary.wimax does not get included/is commented out) This is the situation: My reply has to contain two QoS profiles. testingstuff@internet.ao Cleartext-Password := "sven" Alvarion-R3-IF-Name+=cpe_mgnt_sg, Alvarion-PDFID+=1, WiMAX-Packet-Data-Flow-Id+=1, WiMAX-Direction+=3, WiMAX-Transport-Type+=1, WiMAX-Uplink-QOS-Id+=2, WiMAX-Downlink-QOS-Id+=3, WiMAX-ClassifierID+=1, WiMAX-Classifier-Priority+=2, WiMAX-Classifier-Direction+=3, WiMAX-IP-TOS-DSCP-Range-and-Mask+=0x1818FF, WiMAX-QoS-Id+=2, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000, WiMAX-QoS-Id+=3, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000 I checked the debug output and could see this: Alvarion-R3-IF-Name += "cpe_mgnt_sg" 01 0d 63 70 65 5f 6d 67 6e 74 5f 73 67 ..(skipped some attributes).. WiMAX-Uplink-QOS-Id += 2 07 03 02 WiMAX-Downlink-QOS-Id += 3 08 03 03 WiMAX-ClassifierID += 1 01 03 01 WiMAX-Classifier-Priority += 2 02 03 02 WiMAX-Classifier-Direction += Bi-Directional 04 03 03 WiMAX-IP-TOS-DSCP-Range-and-Mask += 0x1818ff 07 05 18 18 ff WiMAX-Classifier = ... 0b 10 01 03 01 02 03 02 04 03 03 07 05 18 18 ff WiMAX-Packet-Flow-Descriptor = ... 1a 29 000060b5 (24757) 1c 23 00 01 04 00 01 04 03 03 06 03 01 07 03 02 08 03 03 0b 10 01 03 01 02 03 02 04 03 03 07 05 18 18 ff WiMAX-QoS-Id += 2 01 03 02 WiMAX-Schedule-Type += Best-Effort 04 03 02 WiMAX-Traffic-Priority += 1 05 03 01 WiMAX-Maximum-Sustained-Traffic-Rate += 128000 06 06 00 01 f4 00 WiMAX-QoS-Id += 3 01 03 03 WiMAX-Schedule-Type += Best-Effort 04 03 02 WiMAX-Traffic-Priority += 1 05 03 01 WiMAX-Maximum-Sustained-Traffic-Rate += 128000 06 06 00 01 f4 00 WiMAX-QoS-Descriptor = ... 1a 27 000060b5 (24757) 1d 21 00 01 03 02 04 03 02 05 03 01 06 06 00 01 f4 00 01 03 03 04 03 02 05 03 01 06 06 00 01 f4 00 You can see that the 2 QoS profiles are both contained in the created WiMAX-QoS-Descriptor. What I need is to have two WiMAX-QoS-Descriptors. One for each QoS definition. I can archive that by putting another attribute between the QoS attributes: xnewstuff@internet.ao Cleartext-Password := "sven" Alvarion-R3-IF-Name+=cpe_mgnt_sg, ...(skipped some attributes)... WiMAX-QoS-Id+=2, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000, added-> Acct-Interim-Interval+=60, WiMAX-QoS-Id+=3, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000 The debug output now looks like this: (and is pretty close to what I expect) Alvarion-R3-IF-Name += "cpe_mgnt_sg" 01 0d 63 70 65 5f 6d 67 6e 74 5f 73 67 ...(some attributes skipped).... WiMAX-QoS-Id += 2 01 03 02 WiMAX-Schedule-Type += Best-Effort 04 03 02 WiMAX-Traffic-Priority += 1 05 03 01 WiMAX-Maximum-Sustained-Traffic-Rate += 128000 06 06 00 01 f4 00 WiMAX-QoS-Descriptor = ... 1a 18 000060b5 (24757) 1d 12 00 01 03 02 04 03 02 05 03 01 06 06 00 01 f4 00 Acct-Interim-Interval += 60 55 06 00 00 00 3c WiMAX-QoS-Id += 3 01 03 03 WiMAX-Schedule-Type += Best-Effort 04 03 02 WiMAX-Traffic-Priority += 1 05 03 01 WiMAX-Maximum-Sustained-Traffic-Rate += 128000 06 06 00 01 f4 00 WiMAX-QoS-Descriptor = ... 1a 18 000060b5 (24757) 1d 12 00 01 03 03 04 03 02 05 03 01 06 06 00 01 f4 00 Somehow the freeradius now sees that the first QoS flow is finished and creates the WiMAX-QoS-Descriptor out of the values. Then it puts in the newly introduced value (Acct-Interim-Interval+=60). And at the end it created the second WiMAX-QoS-Descriptor out of the definition for the second QoS flow. In case it is not clear: I would like to have the two QoS flows to create two WiMAX-QoS-Descriptors, instead of one that combines the two. How does freeradius know when a 'sub-TLV' definition is finished? What am I missing? I hope that this request is somehow understandable. Please let me know in case you need further clarification or if you want me to include more information or debug output. Thanks for your good work. Best regards, Sven -- Internet Technologies Angola / Systems Department Tel: +244 (227) 286 000 / (924) 770 290 / (924) 770 291 Skype: internet-technologies-angola Mobile: +244 931 696413 Mail: sven@internet.ao
You follow the dictionary in the order set inside of it. Once you hit the end of your list of attributes the QoS profile is complete. Keep in mind that each service flow starts with: Alvarion-R3-IF-Name+=cpe_mgnt_sg, Alvarion-PDFID+=1, WiMAX-Packet-Data-Flow-Id+=1, If you want a second flow, you would start with the following: Alvarion-R3-IF-Name+=cpe_data_sg, Alvarion-PDFID+=21, WiMAX-Packet-Data-Flow-Id+=21, .... etc. The += allows you to reuse an attribute in your response. Hit me offlist if you have specific Alvarion ASN/AAA questions. | David Peterson | Senior Engineer | Wireless Connections | | 4077 | www.wirelessconnections.net | -----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 Sven Tantau Sent: Thursday, December 20, 2012 9:13 AM To: freeradius-users@lists.freeradius.org Subject: Sub-TLVs how to have the same kind of descriptor twice Hello, I am running version 3.0.0 and have a question about sub-tlvs: I am looking at: WiMAX-QoS-Descriptor as it is defined in dictionary.wimax.alvarion (the standard dictionary.wimax does not get included/is commented out) This is the situation: My reply has to contain two QoS profiles. testingstuff@internet.ao Cleartext-Password := "sven" Alvarion-R3-IF-Name+=cpe_mgnt_sg, Alvarion-PDFID+=1, WiMAX-Packet-Data-Flow-Id+=1, WiMAX-Direction+=3, WiMAX-Transport-Type+=1, WiMAX-Uplink-QOS-Id+=2, WiMAX-Downlink-QOS-Id+=3, WiMAX-ClassifierID+=1, WiMAX-Classifier-Priority+=2, WiMAX-Classifier-Direction+=3, WiMAX-IP-TOS-DSCP-Range-and-Mask+=0x1818FF, WiMAX-QoS-Id+=2, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000, WiMAX-QoS-Id+=3, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000 I checked the debug output and could see this: Alvarion-R3-IF-Name += "cpe_mgnt_sg" 01 0d 63 70 65 5f 6d 67 6e 74 5f 73 67 ..(skipped some attributes).. WiMAX-Uplink-QOS-Id += 2 07 03 02 WiMAX-Downlink-QOS-Id += 3 08 03 03 WiMAX-ClassifierID += 1 01 03 01 WiMAX-Classifier-Priority += 2 02 03 02 WiMAX-Classifier-Direction += Bi-Directional 04 03 03 WiMAX-IP-TOS-DSCP-Range-and-Mask += 0x1818ff 07 05 18 18 ff WiMAX-Classifier = ... 0b 10 01 03 01 02 03 02 04 03 03 07 05 18 18 ff WiMAX-Packet-Flow-Descriptor = ... 1a 29 000060b5 (24757) 1c 23 00 01 04 00 01 04 03 03 06 03 01 07 03 02 08 03 03 0b 10 01 03 01 02 03 02 04 03 03 07 05 18 18 ff WiMAX-QoS-Id += 2 01 03 02 WiMAX-Schedule-Type += Best-Effort 04 03 02 WiMAX-Traffic-Priority += 1 05 03 01 WiMAX-Maximum-Sustained-Traffic-Rate += 128000 06 06 00 01 f4 00 WiMAX-QoS-Id += 3 01 03 03 WiMAX-Schedule-Type += Best-Effort 04 03 02 WiMAX-Traffic-Priority += 1 05 03 01 WiMAX-Maximum-Sustained-Traffic-Rate += 128000 06 06 00 01 f4 00 WiMAX-QoS-Descriptor = ... 1a 27 000060b5 (24757) 1d 21 00 01 03 02 04 03 02 05 03 01 06 06 00 01 f4 00 01 03 03 04 03 02 05 03 01 06 06 00 01 f4 00 You can see that the 2 QoS profiles are both contained in the created WiMAX-QoS-Descriptor. What I need is to have two WiMAX-QoS-Descriptors. One for each QoS definition. I can archive that by putting another attribute between the QoS attributes: xnewstuff@internet.ao Cleartext-Password := "sven" Alvarion-R3-IF-Name+=cpe_mgnt_sg, ...(skipped some attributes)... WiMAX-QoS-Id+=2, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000, added-> Acct-Interim-Interval+=60, WiMAX-QoS-Id+=3, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000 The debug output now looks like this: (and is pretty close to what I expect) Alvarion-R3-IF-Name += "cpe_mgnt_sg" 01 0d 63 70 65 5f 6d 67 6e 74 5f 73 67 ...(some attributes skipped).... WiMAX-QoS-Id += 2 01 03 02 WiMAX-Schedule-Type += Best-Effort 04 03 02 WiMAX-Traffic-Priority += 1 05 03 01 WiMAX-Maximum-Sustained-Traffic-Rate += 128000 06 06 00 01 f4 00 WiMAX-QoS-Descriptor = ... 1a 18 000060b5 (24757) 1d 12 00 01 03 02 04 03 02 05 03 01 06 06 00 01 f4 00 Acct-Interim-Interval += 60 55 06 00 00 00 3c WiMAX-QoS-Id += 3 01 03 03 WiMAX-Schedule-Type += Best-Effort 04 03 02 WiMAX-Traffic-Priority += 1 05 03 01 WiMAX-Maximum-Sustained-Traffic-Rate += 128000 06 06 00 01 f4 00 WiMAX-QoS-Descriptor = ... 1a 18 000060b5 (24757) 1d 12 00 01 03 03 04 03 02 05 03 01 06 06 00 01 f4 00 Somehow the freeradius now sees that the first QoS flow is finished and creates the WiMAX-QoS-Descriptor out of the values. Then it puts in the newly introduced value (Acct-Interim-Interval+=60). And at the end it created the second WiMAX-QoS-Descriptor out of the definition for the second QoS flow. In case it is not clear: I would like to have the two QoS flows to create two WiMAX-QoS-Descriptors, instead of one that combines the two. How does freeradius know when a 'sub-TLV' definition is finished? What am I missing? I hope that this request is somehow understandable. Please let me know in case you need further clarification or if you want me to include more information or debug output. Thanks for your good work. Best regards, Sven -- Internet Technologies Angola / Systems Department Tel: +244 (227) 286 000 / (924) 770 290 / (924) 770 291 Skype: internet-technologies-angola Mobile: +244 931 696413 Mail: sven@internet.ao - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi David, thanks for your quick reply. On 12/20/2012 03:35 PM, David Peterson wrote:
You follow the dictionary in the order set inside of it.
The dictionary: ATTRIBUTE WiMAX-QoS-Descriptor 29 tlv ATTRIBUTE WiMAX-QoS-Id 29.1 byte ATTRIBUTE WiMAX-Global-Service-Class-Name 29.2 string # 6 octets ATTRIBUTE WiMAX-Service-Class-Name 29.3 string ATTRIBUTE WiMAX-Schedule-Type 29.4 byte ATTRIBUTE WiMAX-Traffic-Priority 29.5 byte ATTRIBUTE WiMAX-Maximum-Sustained-Traffic-Rate 29.6 integer ATTRIBUTE WiMAX-Minimum-Reserved-Traffic-Rate 29.7 integer ATTRIBUTE WiMAX-Maximum-Traffic-Burst 29.8 integer ATTRIBUTE WiMAX-Tolerated-Jitter 29.9 integer ATTRIBUTE WiMAX-Maximum-Latency 29.10 integer ATTRIBUTE WiMAX-Reduced-Resources-Code 29.11 byte ATTRIBUTE WiMAX-Media-Flow-Type 29.12 byte ATTRIBUTE WiMAX-Unsolicited-Grant-Interval 29.13 short ATTRIBUTE WiMAX-SDU-Size 29.14 short ATTRIBUTE WiMAX-Unsolicited-Polling-Interval 29.15 short ATTRIBUTE WiMAX-Media-Flow-Description-SDP 29.16 string One of my QoS flows:
WiMAX-QoS-Id+=2, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000,
Since I get good results if I use only one QOS profile, I assume that I can skip attributes and that I'm not required to use them all. (Please correct me if I'm wrong.)
Once you hit the end of your list of attributes the QoS profile is complete.
And this is the part that I do not understand: If I continue by using a second QoS profile:
WiMAX-QoS-Id+=3, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000
I expected freeradius to see that WiMAX-QoS-Id is an element of a new tlv. And then create a new WiMAX-QoS-Descriptor for it. (Instead of combining the data for the two QoS profiles into one WiMAX-QoS-Descriptor.) Is my ASN violating some standard by not accepting one WiMAX-QoS-Descriptor containing data from two QoS profiles? If that is the case, is there another workaround beside putting something between the two QoS profiles? (This is what I did by adding "Acct-Interim-Interval+=60".) Thanks, best regards, Sven -- Internet Technologies Angola / Systems Department Tel: +244 (227) 286 000 / (924) 770 290 / (924) 770 291 Skype: internet-technologies-angola Mobile: +244 931 696413 Mail: sven@internet.ao
Sven Tantau wrote:
The dictionary:
Yes... there's no need to re-post it here. We all have access to it.
Since I get good results if I use only one QOS profile, I assume that I can skip attributes and that I'm not required to use them all. (Please correct me if I'm wrong.)
You don't need to use them all.
If I continue by using a second QoS profile:
WiMAX-QoS-Id+=3, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000
I expected freeradius to see that WiMAX-QoS-Id is an element of a new tlv. And then create a new WiMAX-QoS-Descriptor for it. (Instead of combining the data for the two QoS profiles into one WiMAX-QoS-Descriptor.)
IIRC, it should create two descriptors. Which version are you using? For a lot of the weirder WiMAX stuff, you'll need to use the "master" branch.
Is my ASN violating some standard by not accepting one WiMAX-QoS-Descriptor containing data from two QoS profiles?
No idea. The WiMAX specs are thousands of pages long. It's a miracle it works at all.
If that is the case, is there another workaround beside putting something between the two QoS profiles? (This is what I did by adding "Acct-Interim-Interval+=60".)
If that works... do it. Note that you *can* use a non-packet attribute. e.g. Tmp-String-0 += "blah" It doesn't have to be a "real" attribute. Alan DeKok.
Yeah he is trying to use VPLS with an Alvarion ASN. He is going to have to use the master branch. David -----Original Message----- From: freeradius-users-bounces+davidp=wirelessconnections.net@lists.freeradius.org [mailto:freeradius-users-bounces+davidp=wirelessconnections.net@lists.freera dius.org] On Behalf Of Alan DeKok Sent: Thursday, December 20, 2012 2:15 PM To: FreeRadius users mailing list Subject: Re: Sub-TLVs how to have the same kind of descriptor twice Sven Tantau wrote:
The dictionary:
Yes... there's no need to re-post it here. We all have access to it.
Since I get good results if I use only one QOS profile, I assume that I can skip attributes and that I'm not required to use them all. (Please correct me if I'm wrong.)
You don't need to use them all.
If I continue by using a second QoS profile:
WiMAX-QoS-Id+=3, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000
I expected freeradius to see that WiMAX-QoS-Id is an element of a new tlv. And then create a new WiMAX-QoS-Descriptor for it. (Instead of combining the data for the two QoS profiles into one WiMAX-QoS-Descriptor.)
IIRC, it should create two descriptors. Which version are you using? For a lot of the weirder WiMAX stuff, you'll need to use the "master" branch.
Is my ASN violating some standard by not accepting one WiMAX-QoS-Descriptor containing data from two QoS profiles?
No idea. The WiMAX specs are thousands of pages long. It's a miracle it works at all.
If that is the case, is there another workaround beside putting something between the two QoS profiles? (This is what I did by adding "Acct-Interim-Interval+=60".)
If that works... do it. Note that you *can* use a non-packet attribute. e.g. Tmp-String-0 += "blah" It doesn't have to be a "real" attribute. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 12/20/2012 08:14 PM, Alan DeKok wrote:
I expected freeradius to see that WiMAX-QoS-Id is an element of a new tlv. And then create a new WiMAX-QoS-Descriptor for it. (Instead of combining the data for the two QoS profiles into one WiMAX-QoS-Descriptor.)
IIRC, it should create two descriptors.
At least in my version the data gets combined into one descriptor. (See debug output of my first mail.)
Which version are you using? For a lot of the weirder WiMAX stuff, you'll need to use the "master" branch.
I do. But I fetched the code in early March. Perhaps something changed.
If that is the case, is there another workaround beside putting something between the two QoS profiles? (This is what I did by adding "Acct-Interim-Interval+=60".)
If that works... do it. Note that you *can* use a non-packet attribute.
e.g. Tmp-String-0 += "blah"
It doesn't have to be a "real" attribute.
I just tested this. Works like expected. Thanks a lot. Regards, Sven -- Internet Technologies Angola / Systems Department Tel: +244 (227) 286 000 / (924) 770 290 / (924) 770 291 Skype: internet-technologies-angola Mobile: +244 931 696413 Mail: sven@internet.ao
Here is an example of two flows, one for management of the CPE and one for data: Alvarion-R3-IF-Name += MGMT_PrivateIP Alvarion-PDFID += 1 WiMAX-Packet-Data-Flow-Id += 1 WiMAX-Service-Data-Flow-Id += 1 WiMAX-Direction += 3 WiMAX-Transport-Type += 1 WiMAX-Uplink-QOS-Id += 1 WiMAX-Downlink-QOS-Id += 1 WiMAX-ClassifierID += 1 WiMAX-Classifier-Priority += 1 WiMAX-Classifier-Direction += 1 WiMAX-IP-TOS-DSCP-Range-and-Mask += 0x1818FF WiMAX-Transport-Type += 1 WiMAX-ClassifierID += 2 WiMAX-Classifier-Priority += 1 WiMAX-Classifier-Direction += 2 WiMAX-IP-TOS-DSCP-Range-and-Mask += 0x0000FF WiMAX-QoS-Id += 1 WiMAX-Schedule-Type += 2 WiMAX-Traffic-Priority += 1 WiMAX-Maximum-Sustained-Traffic-Rate += 1024000 Alvarion-R3-IF-Name += VPLS Alvarion-PDFID += 21 Alvarion-PDFID += 22 WiMAX-Packet-Data-Flow-Id += 21 WiMAX-Service-Data-Flow-Id += 21 WiMAX-Direction += 1 WiMAX-Transport-Type += 3 WiMAX-Uplink-QOS-Id += 2 WiMAX-Downlink-QOS-Id += 2 WiMAX-ClassifierID += 3 WiMAX-Classifier-Priority += 1 WiMAX-Classifier-Direction += 1 WiMAX-VLAN-ID += 25 WiMAX-QoS-Id += 2 WiMAX-Schedule-Type += 2 WiMAX-Traffic-Priority += 1 WiMAX-Maximum-Sustained-Traffic-Rate += 10240000 WiMAX-Packet-Data-Flow-Id += 22 WiMAX-Service-Data-Flow-Id += 21 WiMAX-Direction += 2 WiMAX-Transport-Type += 3 WiMAX-Uplink-QOS-Id += 3 WiMAX-Downlink-QOS-Id += 3 WiMAX-ClassifierID += 4 WiMAX-Classifier-Priority += 1 WiMAX-Classifier-Direction += 2 WiMAX-VLAN-ID += 25 WiMAX-QoS-Id += 3 WiMAX-Schedule-Type += 2 WiMAX-Traffic-Priority += 1 WiMAX-Maximum-Sustained-Traffic-Rate += 25000000 -----Original Message----- From: freeradius-users-bounces+davidp=wirelessconnections.net@lists.freeradius.org [mailto:freeradius-users-bounces+davidp=wirelessconnections.net@lists.freera dius.org] On Behalf Of Sven Tantau Sent: Thursday, December 20, 2012 2:04 PM To: freeradius-users@lists.freeradius.org Subject: Re: Sub-TLVs how to have the same kind of descriptor twice Hi David, thanks for your quick reply. On 12/20/2012 03:35 PM, David Peterson wrote:
You follow the dictionary in the order set inside of it.
The dictionary: ATTRIBUTE WiMAX-QoS-Descriptor 29 tlv ATTRIBUTE WiMAX-QoS-Id 29.1 byte ATTRIBUTE WiMAX-Global-Service-Class-Name 29.2 string # 6 octets ATTRIBUTE WiMAX-Service-Class-Name 29.3 string ATTRIBUTE WiMAX-Schedule-Type 29.4 byte ATTRIBUTE WiMAX-Traffic-Priority 29.5 byte ATTRIBUTE WiMAX-Maximum-Sustained-Traffic-Rate 29.6 integer ATTRIBUTE WiMAX-Minimum-Reserved-Traffic-Rate 29.7 integer ATTRIBUTE WiMAX-Maximum-Traffic-Burst 29.8 integer ATTRIBUTE WiMAX-Tolerated-Jitter 29.9 integer ATTRIBUTE WiMAX-Maximum-Latency 29.10 integer ATTRIBUTE WiMAX-Reduced-Resources-Code 29.11 byte ATTRIBUTE WiMAX-Media-Flow-Type 29.12 byte ATTRIBUTE WiMAX-Unsolicited-Grant-Interval 29.13 short ATTRIBUTE WiMAX-SDU-Size 29.14 short ATTRIBUTE WiMAX-Unsolicited-Polling-Interval 29.15 short ATTRIBUTE WiMAX-Media-Flow-Description-SDP 29.16 string One of my QoS flows:
WiMAX-QoS-Id+=2, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000,
Since I get good results if I use only one QOS profile, I assume that I can skip attributes and that I'm not required to use them all. (Please correct me if I'm wrong.)
Once you hit the end of your list of attributes the QoS profile is complete.
And this is the part that I do not understand: If I continue by using a second QoS profile:
WiMAX-QoS-Id+=3, WiMAX-Schedule-Type+=2, WiMAX-Traffic-Priority+=1, WiMAX-Maximum-Sustained-Traffic-Rate+=128000
I expected freeradius to see that WiMAX-QoS-Id is an element of a new tlv. And then create a new WiMAX-QoS-Descriptor for it. (Instead of combining the data for the two QoS profiles into one WiMAX-QoS-Descriptor.) Is my ASN violating some standard by not accepting one WiMAX-QoS-Descriptor containing data from two QoS profiles? If that is the case, is there another workaround beside putting something between the two QoS profiles? (This is what I did by adding "Acct-Interim-Interval+=60".) Thanks, best regards, Sven -- Internet Technologies Angola / Systems Department Tel: +244 (227) 286 000 / (924) 770 290 / (924) 770 291 Skype: internet-technologies-angola Mobile: +244 931 696413 Mail: sven@internet.ao - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (3)
-
Alan DeKok -
David Peterson -
Sven Tantau