There is no "Calling-Station-Id" attribute in access-requests sent in response to radius challenge from pam_radius-1.3.17-2.el6.x86_64 (CentOS release 6.5)

[Dmitry Saratsky]

Hi Alan,

I'm not talking about Access-Challenge message...
I'm talking about 2nd Access-Request message which is sent by radius client as result for Access-Challenge and user-input...

BR,
Dmitry.

-----Original Message-----
From: freeradius-users-bounces+simpot=simpot.com at lists.freeradius.org [mailto:freeradius-users-bounces+simpot=simpot.com at lists.freeradius.org] On Behalf Of A.L.M.Buxey at lboro.ac.uk
Sent: 01 Sep 2014 14:30
To: FreeRadius users mailing list
Subject: Re: There is no "Calling-Station-Id" attribute in access-requests sent in response to radius challenge from pam_radius-1.3.17-2.el6.x86_64 (CentOS release 6.5)

Hi,


as per the config files:

#	This configuration file is used to remove almost all of the
#	attributes From an Access-Challenge message.  The RFC's say
#	that an Access-Challenge packet can contain only a few
#	attributes.  We enforce that here.
#
DEFAULT
	EAP-Message =* ANY,
	State =* ANY,
	Message-Authenticator =* ANY,
	Reply-Message =* ANY,
	Proxy-State =* ANY,
	Session-Timeout =* ANY,
	Idle-Timeout =* ANY


...so, why do you think ANY of these other things should be in challenge datagrams?

alan

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html