There are two reasons for my approach:
1) The radius server is also serving other requests that DO have a
username password it is only certain logins I need to process
differently - those where the caller ID matches a pattern.
2) On those that do match I do want per session settings - ie to return
a IP address.
This way seems to achieve that mix easily and seems to work.
I'm happy for suggestions as ever ...
On 16/02/2012 7:57 AM, Alan DeKok wrote:
Joe Holden wrote:
How will that work if for example all my attributes are in a database
and are per user?
I thought you said there was no user name... how can the attributes be
per user if there is no user name?
There is essentially *no* username for these sessions, so how does FR
lookup the correct records without replacing the username before?
The SQL queries are editable for precisely this reason. You edit them.
This is NOT a commercial product, where the SQL qeuries&& other
configuration is hidden inside of a binary blob. If you don't like what
FreeRADIUS does, change it.
It's YOUR responsibility to figure out how.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
