Repeating same TLV in a given VSA Issue

Alan DeKok aland at deployingradius.com
Wed May 1 15:02:13 CEST 2013


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's an issue.

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

  Yes.

> Wondering if the behavior in versions 2.1.2 and 2.20 is a bug and was
> fixed in the “master” branch or are we missing any configuration in
> 2.1.2/2.20 which is causing the undesired behavior?

  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.

  The code in master has been *completely* re-written.

> For our production implementation, don’t want to go to the “master”
> branch if possible.

  That's OK.

> Sorry for the last email, but want to provide as much details as possible.

  You provided exactly the correct information to find and fix the problem.

  Alan DeKok.


More information about the Freeradius-Users mailing list