Hi Alan, Thanks a lot for the quick response and putting in the fix under 2.x.x branch. We configured the FreeRadius using this new 2.x.x branch from git; The length of the AVP comes correct, but the 2nd classifier is showing in a separate AVP. Here is the packet capture (2.x.x git branch): AVP: l=125 t=Vendor-Specific(26) v=WiMAX(24757) VSA: l=119 t=WiMAX-Packet-Flow-Descriptor(28) C=0x00: TLV: l=4 t=WiMAX-Packet-Data-Flow-Id(1): 111 WiMAX-Packet-Data-Flow-Id: 111 TLV: l=4 t=WiMAX-Service-Data-Flow-Id(2): 101 WiMAX-Service-Data-Flow-Id: 101 TLV: l=3 t=WiMAX-Direction(4): Uplink(1) WiMAX-Direction: Uplink (1) TLV: l=3 t=WiMAX-Activation-Trigger(5): 4 WiMAX-Activation-Trigger: 4 TLV: l=3 t=WiMAX-Transport-Type(6): IPv4-CS(1) WiMAX-Transport-Type: IPv4-CS (1) TLV: l=3 t=WiMAX-Uplink-QOS-Id(7): 111 WiMAX-Uplink-QOS-Id: 111 TLV: l=46 t=WiMAX-Uplink-Classifier(9): permit in ip src any dst any 0-66 priority 3 WiMAX-Uplink-Classifier: permit in ip src any dst any 0-66 priority 3 [TLV too short: length 0 < 2] AVP: l=59 t=Vendor-Specific(26) v=WiMAX(24757) VSA: l=53 t=WiMAX-Packet-Flow-Descriptor(28) C=0x00: 1 TLV(s) inside TLV: l=50 t=WiMAX-Uplink-Classifier(9): permit in ip src any dst any 69-65535 priority 3 WiMAX-Uplink-Classifier: permit in ip src any dst any 69-65535 priority 3 Alan DeKok wrote:
It's a minor bug in v2.2.0. I've pushed a fix to the v2.x.x branch from "git". It will go into the 2.2.1 release.
Thanks -Hanu