Phil Mayers [EMAIL PROTECTED] a écrit: Mitaine Yoann wrote: */Michael Mitchell <[EMAIL PROTECTED]>/* a écrit : Client-IP-Address is an internal freeRADIUS attribute, and is not defined in the RFC's. Hence it is never proxied to another server.Yes, I am aware of that. I said that, in
Mitaine Yoann wrote:
the only problem is that preprocess is present in the authorize
section in the radiusd.conf file of the radius server A
You should check also the config of the radius server B.
And please stop posting with HTML to the mailing list.
--
Nicolas Baradakis
-
List
Mitaine Yoann wrote:
Dear everybody,
I've installed the radius 's CVS version of 08-23-06.
I've this architecture :
client AP Radius A Radius B
802.1X
proxying
The client does not have adress of IP, it
Dear everybody,In my previous email , I forgot to say that when I received a proxing packet, I tried to match a rule on the radius server B like :DEFAULT Huntgroup-Name == "foo", Autz-Type := Ldapwhere foo is defining in huntgroups file as : foo Client-IP-Address == x.x.x.xin the users file.But
Phil Mayers wrote:
Mitaine Yoann wrote:
When I proxied the request from to server A to the server B, there
wasn't
Client-IP-Address in the packet.
Client-IP-Address is added by the preprocess module. Have you removed
this from authorize? If so, don't do that.
Client-IP-Address is an
Mitaine Yoann wrote:
*/Michael Mitchell [EMAIL PROTECTED]/* a écrit :
Client-IP-Address is an internal freeRADIUS attribute, and is not
defined in the RFC's. Hence it is never proxied to another server.
Yes, I am aware of that. I said that, in fact.
In fact, the
Mitaine Yoann wrote:
In my previous email , I forgot to say that when I received a proxing
packet, I tried to match a rule on the radius server B like :
DEFAULT Huntgroup-Name == foo, Autz-Type := Ldap
where foo is defining in huntgroups file as :
foo Client-IP-Address == x.x.x.x
in the
7 matches
Mail list logo
