Contextual mapping of LDAP attributes

[Enrico Polesel]

Hello everyone,

maybe a bit off-topic, but another way to this would be to define
nasType in the clients.conf file and then refer to it with
%{client:nasType}. So something like this

client something {
       ipaddr = 1.2.3.4
       secret = hereiam
       nasType = xdsl
}
...
update {
       reply:ERX-Virtual-Router-Name := "%{client:nasType}virtualrouter"
}

(of course this won't work if the same intermediate server proxies
requests from different types of NAS)

Cheers,
Enrico

On Wed, Jul 06, 2016 at 01:22:53PM +0200, Adamczak Krzysztof wrote:
> Yeah I thought so. Another approach would be (specific to my
> configuration) to map directly in ldap module update like this:
> update {
>     reply:ERX-Virtual-Router-Name   := "%{control:nasType}virtualrouter"
> }
> 
> Where control:nasType was set earlier (authorize section) based on
> e.g. NAS-IP-Address (NAS-IP-Address -> "xdsl" | "adsl" " ...)
> 
> thanks for the reply,
> Krzysztof
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20160707/7a3d41ab/attachment.sig>