Hiya Graeme,
If you are using an SQL database backend it is very easy to implement
this...
You setup group names in the radgroupreply table with the attributes to be
returned to the NAS for that group - you can have multiple records with the
same group name to allow multiple attributes. Each
Hiya,
We are adding rate limiting attributes to our radius entries on a per
customer basis, however the rates imposed will be one of 4 predefined
rates. Each rate also has a burst value which is pre determined, and
may be changed as we tweak.
Ideally we would like to store a lookup of
Hiya,
Cheers for that, I have been pondering this (but in a different way).
As we have to perform 2 radius lookups per customer if they are
delivered via a specific pipe (thanks BT :/ ) we are already using a
form of mangled radius that uses huntgroup name to read additional
params from
On Tue, 2004-07-20 at 11:48, jesk wrote:
Hiya,
We are adding rate limiting attributes to our radius entries on a per
customer basis, however the rates imposed will be one of 4 predefined
rates. Each rate also has a burst value which is pre determined, and
may be changed as we tweak.
4 matches
Mail list logo
