Hello,
I didn't read the entire thread, but couldn't you just do this:
Handler Request-Type = Accounting-Request
# strip off realm:
RewriteUsername s/^([^@]+).*/$1/
/Handler
? If I neglected to read something, I apologize in advance.
Dave
On Friday 13 July 2001 20:58,
Hello Dave, Hello Dmitry -
The problem is that Radiator does a delete on reception of an access request
as well as when it gets an accounting stop. This in addition to the fact that
by default, Radiator always uses the username string received from the NAS
(which it must do if it is to do
Hello Vangelis -
Actually, an internal session database is exactly that - a session database
held entirely in memory. The username in each request is what is used, as
follows: Access-Request - check current sessions and reject if limit
exceeded, Accounting Start - add new record, Accounting
Hello Dmitry -
Here is what I get with this configuration file (copied from your mail):
Foreground
Trace 4
Client DEFAULT
Secret mysecret
/Client
Handler Realm=bbeyond.nl
RewriteUsername s/^([^@]+).*/$1/
MaxSessions 1
AuthBy FILE
Filename ./bbeyond.users
/AuthBy
From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 13, 2001 8:43 AM
To: Vangelis Kyriakakis; [EMAIL PROTECTED]
Subject: Re: (RADIATOR) MaxSessions issue, still a problem
Hello Vangelis -
Actually, an internal session database is exactly that - a session database
held entirely in me
s possible to rewrite the User-Name
in Accounting request? Or maybe there is another solution?
regards,
Dmitry Kopylov
-Original Message-
From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 13, 2001 8:43 AM
To: Vangelis Kyriakakis; [EMAIL PROTECTED]
Subject: Re: (RADI
I think the problem when you use the Internal session database is that it
uses the username from the Accounting file to count the number of sessions. When
a new user logs in it checks the rewritten username against the session
database. So it checks with the name uunoc and not with the [EMAIL
