rfc6929 : combination extended-type/long-extended-type and TLV data type

Vereecke, Katrien (Katrien) katrien.vereecke at alcatel-lucent.com
Tue Nov 10 11:41:06 CET 2015


I am using freeradius server  version V3.0.x.
According to rfc6929 the combination of a extended or long-extended-type and tlv-data type is allowed.
The rfc states that the TLV-length must have a value between 3 and 255, but is this correct in case of an extended or long extended type , should it then not be respectively 252 and 251 max?

I was testing the TLV data type and long extended type, I defined in my dictionary the following:
ATTRIBUTE Test-Attr-261-11         246.11      tlv
ATTRIBUTE Test-Attr-261-11-1     246.11.1  octets

And in my users file I included
Test-Attr-261-11-1 = 0x00112233445566aabbccddeeff0011223344..........  => with a length more than 300 octets

In the wireshark I see that the attribute is fragmented but the length-attr and the tlv-length are both set to  ff and the second fragmented part does only contain the octets up till data length 255, not all octets specified in my users file.  Is this correct?

Wireshark output :
f6 ff 0b 80 01 ff 00 11 22 33 44 55 .....
f6 08 0b 00 99 aa bb cc ...

Kind regards,

More information about the Freeradius-Users mailing list