the included docs and examples don't use the atrrs_filter module with the
pre-proxy{} section in radiusd.conf.
there is a post-proxy{} and that works fine.
i have different instatiations (with different config files) for each pre-
and post-proxy. having no replies from the list i decided to go ahead and
test.
for you information it seems to work. (freereadius 1.0.2).
is there a reason why this might be lucky? is this not the intended
behaviour? did it only work because i have simple test configs?
see below for the configs:
-------
post-proxy attrs:
DEFAULT
Service-Type =* ANY,
Framed-IP-Address =* ANY,
Framed-IP-Netmask =* ANY,
Reply-Message =* ANY
---------
pre-proxy attrs:
DEFAULT
User-Name =* ANY,
User-Password =* ANY
------------
home server (proxy target) confirm the pre-processing works from the logs:
rad_recv: Access-Request packet from host 217.204.125.202:1814, id=1,
length=67
User-Name = "[EMAIL PROTECTED]"
User-Password = "******"
Processing the authorize section of radiusd.conf
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
