RE: Repeating same TLV in a given VSA Issue

Thanks a lot Alan for the quick response and change again :-). The new fix works like charm :-). We see the 2 classifier in the same AVP. Here is the packet capture: AVP: l=125 t=Vendor-Specific(26) v=WiMAX(24757) VSA: l=119 t=WiMAX-Packet-Flo

Re: Repeating same TLV in a given VSA Issue

Cholleti, Hanumantha wrote: > Thanks a lot for the quick response and putting in the fix under 2.x.x branch. It's what I do. :) > 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.

RE: Repeating same TLV in a given VSA Issue

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):

Re: Repeating same TLV in a given VSA Issue

Cholleti, Hanumantha wrote: > Version 2.1.2 and 2.20 > > -- > > In both FreeRadius versions 2.1.2 and 2.20 on RedHat, the 2^nd > Uplink-Classifier (permit in ip src any dst any 69-65535 priority 3) is > showing up in a separate VSA on its own as shown below; Yeah, that'

Re: Repeating same TLV in a given VSA Issue

Hi, >If we configure the FreeRadius using the "Master" branch, we get the 2nd >Uplink-Classifier in the same VSA as expected (as shown in the first >packet capture) so likely a bug fixed >For our production implementation, don't want to go to the "master" branch >if possible.