Hi, Is it possible to proxy based on a group the user belongs to? Or attribute? Or based on NAS from where the request was received? Aside from REALM, is there any other criteria that can be used to decide whether or not to proxy a request? Thanks, Det
From: "det.explorer@yahoo.com" <det.explorer@yahoo.com> Date: September 1, 2011 9:51:33 PM GMT+08:00 To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org>
Hi,
Is it possible to proxy based on a group the user belongs to? Or attribute? Or based on NAS from where the request was received?
Aside from REALM, is there any other criteria that can be used to decide whether or not to proxy a request?
Thanks, Det
On 01/09/11 14:53, det.explorer@yahoo.com wrote:
Hi,
Is it possible to proxy based on a group the user belongs to? Or attribute? Or based on NAS from where the request was received?
Aside from REALM, is there any other criteria that can be used to decide whether or not to proxy a request?
There are two attributes: 1. "Realm"; added to the request by e.g. the "suffix" module. Doesn't actually do anything; just used for logging. 2. "Proxy-To-Realm"; added to the "control" items by the "suffix" module, or by other config. This is what actually controls proxying. So for example you can do this: authorize { ... if (NAS-IP-Address == 192.0.2.1) { update control { Proxy-To-Realm := OTHERSERVER } } ... } As you can see, you can therefore proxy on any attribute you like, or even on the output of a script, SQL query, etc.
Hey thanks! :) ________________________________ From: Phil Mayers <p.mayers@imperial.ac.uk> To: freeradius-users@lists.freeradius.org Sent: Thursday, September 1, 2011 10:04 PM Subject: Re: Proxying Based on Criteria Other Than REALM On 01/09/11 14:53, det.explorer@yahoo.com wrote:
Hi,
Is it possible to proxy based on a group the user belongs to? Or attribute? Or based on NAS from where the request was received?
Aside from REALM, is there any other criteria that can be used to decide whether or not to proxy a request?
There are two attributes: 1. "Realm"; added to the request by e.g. the "suffix" module. Doesn't actually do anything; just used for logging. 2. "Proxy-To-Realm"; added to the "control" items by the "suffix" module, or by other config. This is what actually controls proxying. So for example you can do this: authorize { ... if (NAS-IP-Address == 192.0.2.1) { update control { Proxy-To-Realm := OTHERSERVER } } ... } As you can see, you can therefore proxy on any attribute you like, or even on the output of a script, SQL query, etc. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 1 Sep 2011, at 15:51, det.explorer@yahoo.com wrote:
Hi,
Is it possible to proxy based on a group the user belongs to? Or attribute? Or based on NAS from where the request was received?
Aside from REALM, is there any other criteria that can be used to decide whether or not to proxy a request?
Yes. The control attribute Proxy-To-Realm can set the realm a request is proxied to. Read man unlang for further details. Arran Cudbard-Bell a.cudbardb@freeradius.org RADIUS - Half the complexity of Diameter
participants (4)
-
Arran Cudbard-Bell -
Det Det -
det.explorer@yahoo.com -
Phil Mayers