Hello !
Another possible solution:
Make authorization via SQL, and external program. External program
called
in configuration from users file. External program will make auth&acct
for prepaid
cards, and if it determine that authorization or accounting packet is
for contract
client, then it will no append any attributes except Fall-Through = Yes.
When external program does billing for cards itself, it will return
all necessary
attributes in addition to Fall-Through = No. Is this alrotithm
correct and
implementable in FreeRadius ?
Thanks
Ruslan A Dautkhanov wrote:
Hello !
Short question:
Please point me how to make startup changes in huntgroup to
configure FR to use two different sql-modules for auth&acct, based
on some criterias?... Examples are most welcome.
Explanation:
We have contract subscribers and want to use the same RADIUS-
server for auth&acct of prepaid cards. Contact users enters their
login+realm
and password, but cards users enter card number and PIN-code. That is
the difference, that make difference. We need use another SQL module
instance for card users...
How to configure huntgroups for this situation?
Conditions can be
(1) if no '@' char in the User-Name attribute, then use
'sql-cards' instance
for auth&acct. Otherwise, use 'sql-contracts'.
(2) if User-Name attribute have (determ. via regex) exact 14
digits, then
use 'sql-cards' instance for auth&acct. Otherwise, use
'sql-contracts'.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
