Sub-TLVs how to have the same kind of descriptor twice

Alan DeKok aland at
Thu Dec 20 20:14:35 CET 2012

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.

More information about the Freeradius-Users mailing list