Re: stripping the prefixes for accounting
Bobi [EMAIL PROTECTED] wrote: Is there simple way to use Stripped-User-Name for accounting. Yes... if it exists, it will go into the detail record. I'm trying to do something like: DEFAULT Prefix == pref User-Name := %{Stripped-User-Name} in acct_users file Uh, why? If acct_users works only with existing attributes Yes. It only uses attributes which already exist in the request. there should be other way to strip prefixes for accounting ? Why do you want to strip the prefixes only for accounting? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: stripping the prefixes for accounting
Hi Alan, I'm migrating from heavy patched by me Livingston radius. Freeradius is most configurable one I managed to find and it was really easy (with 2-3 slight patches like %{raw:Attr-Name} in xlat anyway :) to switch it for all my needs. One of the very few things i still need to do is sql accounting for one type of prefix to be done with stripped User-Name. It will be nice sql accounting to be configurable as easy as sql authentication. Possibility for calling different sql accounting sub functions just like calling different sql authentication subfunctions will be very handy. One more thing I think isn't configurable enough in rlm_sql: Only plain text and unix style encrypted passwords can be checked. Maybe it's good idea to add external password checking. Someone may be using sql password() or (like me) it's own password encrypting function. Regards, B. [cut] If acct_users works only with existing attributes Yes. It only uses attributes which already exist in the request. there should be other way to strip prefixes for accounting ? Why do you want to strip the prefixes only for accounting? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html