I don�t know radius so deep but hope these attributes are here as well
as other initial details, aren�t?
Look at "radius -X" for
attr_rewrite add_realm {
attribute = User-Name
searchin = packet
searchfor = "[EMAIL PROTECTED]"
replacewith = ".%{NAS-Identifier}"
ignore_case = no
new_attribute = no
max_matches = 1
append = yes
}
There:
modcall: entering group authorize for request 1
radius_xlat: '[EMAIL PROTECTED]'
radius_xlat: '.'
rlm_attr_rewrite: Changed value for attribute User-Name from 'user' to 'user.'
modcall[authorize]: module "add_realm" returns ok for request 1
modcall[authorize]: module "preprocess" returns ok for request 1
There is no error or something.
Regards,
Zdenek Svarc
On Fri, 17 Sep 2004 13:17:11 -0400, Alan DeKok wrote:
> Zdenek Svarc <[EMAIL PROTECTED]> wrote:
> > but attr_rewrite doesn't know %{NAS-Identifier} as well as others NAS*
> > and Call* and points back only "user."
>
> Are those attributes in the RADIUS packet? If not, they don't
> exist, and can't be used.
>
> And yes, when you run in debug mode, you will not only see which
> attributes exist in the packet, but exactly how the %{...} strings are
> getting expanded.
>
> Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
