Problem with regular expression in huntgroups
Peter Balsianok
balsianok.peter at gmail.com
Tue Apr 21 12:53:18 CEST 2015
Great idea, clear from configuration perspective.
Peter
On Tue, Apr 21, 2015 at 12:13 PM, Arran Cudbard-Bell <
a.cudbardb at freeradius.org> wrote:
>
> > On 21 Apr 2015, at 11:06, Peter Balsianok <balsianok.peter at gmail.com>
> wrote:
> >
> > For example this works: LNS NAS-IP-Address =~ "213.151.23(1|2).*"
>
> Regular expressions against IP address type attributes are no longer
> supported in huntgroups or the users file.
>
> I'd seriously considering about moving way from huntgroups, they are
> extremely inefficient.
>
> If you want to associate data with a client, you can add arbitrary pairs
> to the client definitions, and access them with the "%{client:<attr>}" xlat.
>
> This works for bulk loaded clients from couchbase/ldap, and dynamically
> clients, as well as clients defined in the static clients.conf file.
>
> example:
>
> client loopback {
> ipaddr = 127.0.0.1
> secret = testing123
>
> arbitrary_attribute = 'testing'
> }
>
> authorize {
> update request {
> Tmp-String-0 := "%{client:arbitrary_attribute}"
> }
> }
>
> -Arran
>
> Arran Cudbard-Bell <a.cudbardb at freeradius.org>
> FreeRADIUS development team
>
> FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
More information about the Freeradius-Users
mailing list