dynamic clients and nas-type
I'm trying to setup my dynamic clients and specify a nas-type. In my dynamic-clients I have: server dynamic_client_server { authorize { FreeRADIUS-Client-Shortname = "Cisco" FreeRADIUS-Client-NAS-Type = "other" ... Then in my sites-enabled/default in the authorize section I have: update request { # NAS-Vendor is a local custom dict addition FreeRADIUS-Client-Shortname := "%{Client-Shortname}" FreeRADIUS-Client-NAS-Type := "%{FreeRADIUS-Client-NAS-Type}" } To see what my Client-Shortname and NasType are set to using unlang. But in the debug output I get: ++[request] returns notfound expand: %{Client-Shortname} -> Cisco expand: %{FreeRADIUS-Client-NAS-Type} -> ++[request] returns notfound What field should I be trying to lookup to find out what value I set my NAS-Type to in Dynamic Clients while in the Authorize section in my default?? And as per the docs: http://wiki.freeradius.org/Clients.conf Are the list of permitted nastypes valid, or can I use any string and do further checks for it later?
Peter Lambrechtsen wrote:
I'm trying to setup my dynamic clients and specify a nas-type.
In my dynamic-clients I have: ... Then in my sites-enabled/default in the authorize section I have:
A completely independent virtual server. The only way for the two virtual servers to communicate is by having one store attributes in a database, and then the other reads the database.
What field should I be trying to lookup to find out what value I set my NAS-Type to in Dynamic Clients while in the Authorize section in my default??
Use a database.
And as per the docs: http://wiki.freeradius.org/Clients.conf
Are the list of permitted nastypes valid, or can I use any string and do further checks for it later?
You can use any string. The valid values are there only for the "checkrad.pl" script. Alan DeKok.
On Wed, Oct 6, 2010 at 6:35 PM, Alan DeKok <aland@deployingradius.com>wrote:
Peter Lambrechtsen wrote:
I'm trying to setup my dynamic clients and specify a nas-type.
In my dynamic-clients I have: ... Then in my sites-enabled/default in the authorize section I have:
A completely independent virtual server. The only way for the two virtual servers to communicate is by having one store attributes in a database, and then the other reads the database.
Ahh ok, thanks for that. I was wondering why I could use the %Client-Shortname, and not the NAS-Type. That explains it. I'll stick with just using Client-Shortname, as that gives me all I need so far. Cheers again. Peter
participants (2)
-
Alan DeKok -
Peter Lambrechtsen