Hello Steve -
On Wednesday 10 January 2001 09:50, Delanet Administration wrote:
> > Ok I understand how it works now. Why is there an option for special
> characters at all in the addquery if it uses the value passed to accounting
> reardless? And is there a way to remove the realm or rewrite the username
> *after* the insert into accounting?
>
Note that it is the construction of your configuration that is the reason for
this happening. If you were using a single, simple AuthBy SQL clause for both
authentication and accounting, the RewriteUsername would work correctly for
both types of packets. Because you have different processing for your
authentication (with RewriteUsernames) and accounting (without
RewriteUsernames), you have a problem. Note that you could add the identical
RewriteUsernames to your accounting, but as I have mentioned, it is probably
easier to use the Class attribute as temporary storage for all your cases.
> Reason I need this is that my billing system needs to know which users log
> on with realms for our roaming users (via megapop which forwards radius
> requests based on realm supplied from it's pops). This way we can track
> usage of our national dailups. However, if the customers login name is x
> and he logs in as [EMAIL PROTECTED], then [EMAIL PROTECTED] is put in the session table. The
> problem with this is the customer can then login again from another
> location as [EMAIL PROTECTED] and successfully login, bypassing simultaneous use
> limits because the compare is done based on the user@realm contained in the
> session table, and of course, [EMAIL PROTECTED] does not match [EMAIL PROTECTED] and thus they
> are allowed in.
>
I understand what you want to do, but as you have discovered, its a bit
tricky. If you would like me to help you with a custom configuration, please
send me a detailed specification and I will quote you a number of hours of
consulting time to build a suitable configuration file. Then you can send us
a purchase order and I'll do it for you.
regards
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
