And to make it even more complicated, On some Cisco-AVPair we want to do reg exp matching. And some other's we want to add by default, but they all share the same key name.. Is this possible within freeradius? Ivo On Apr 20, 2012, at 6:14 PM, Ivo Vastert wrote:
Hi,
We have the regexp's working properly now. The trick was removing the / / (in the front and at the end of the line). The only issue we have left is that we want to set multiple values for the same key in the attrs file, normally we set:
Cisco-AVPair = "value1" Cisco-AVPair += "value2" Cisco-AVPair += "valu3"
But i only see the operator := to set a value independent of the upstream proxy. Is there a limitation that we can only enforce 1 value per key? Or os there another way to do this?
When we use the operator := multiple times our router can't handle the reponse properly.
Best regards,
Ivo Vastert
On Apr 19, 2012, at 9:31 AM, Phil Mayers wrote:
On 04/18/2012 07:04 PM, Ivo Vastert wrote:
Hi Phil,
Thank you for your answer. I just try'd your rule but this one is refused aswell (Freeradius won't start with it, giving a parse error).
Framed-IP-Address =~ /^172\.(1[6-9]|2[0-9]|3[01])\./ I still have the feeling ( ) is not accepted, when we don't use themthe grouping characters, the line is accepted. Do you have any other suggestions we can try?
I don't know what to tell you; we use regexp with () for grouping locally, and it works fine; FreeRADIUS can start, and the regexp match as expected.
FreeRADIUS doesn't handle the regexp itself; it uses your system regexp library. If the regexp fails to parse, it must be a problem with your system regexp library.
Just in case, please supply the output of "radiusd -X" as it fails to start up. Maybe there's something else wrong. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html