I looked at debug again:
rad_recv: Access-Request packet from host 62.*.*.5:1641, id=20, length=45
User-Name = test
CHAP-Password = 0x6bdd1b91c37533a5**
Processing the authorize section of radiusd.conf
searchin = packet know only %{User-Name} and %{CHAP-Password}
Zdenek Svarc [EMAIL PROTECTED] wrote:
searchin = packet know only %{User-Name} and %{CHAP-Password}
attributes. That's why I can't use attr_rewrite to add NAS-identifier
or Called-Station-Id sufix to User-Name.
Do you know any way how to do it?
If it's not in the RADIUS packet, you can't
Yes, I understand that I can´t use attr_rewrite function for it. Do
you know any other way how to add NAS-Identifier or Called-Station-Id
suffix to User-Name before authorize occur? As I said we have users
stored as [EMAIL PROTECTED] format.
Zdenek Svarc
On Mon, 20 Sep 2004 12:07:26 -0400, Alan
I am sorry. I was slow on the uptake :-)
On Mon, 20 Sep 2004 13:21:47 -0400, Alan DeKok [EMAIL PROTECTED] wrote:
Zdenek Svarc [EMAIL PROTECTED] wrote:
Yes, I understand that I can't use attr_rewrite function for it.
That's not what I said.
Do you know any other way how to add
Because of my NAS-Identifier as a part of stored user name message I tryed:
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
}
but
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
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
7 matches
Mail list logo
