Re: (RADIATOR) MaxSessions issue, still a problem

2001-07-16 Thread Hugh Irvine
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 str

RE: (RADIATOR) MaxSessions issue, still a problem

2001-07-16 Thread Kitabjian, Dave
Hello, I didn't read the entire thread, but couldn't you just do this: # strip off realm: RewriteUsername s/^([^@]+).*/$1/ ? If I neglected to read something, I apologize in advance. Dave > On Friday 13 July 2001 20:58, Dmitry Kopylov wrote: > > Hello, > > > > and the

Re: (RADIATOR) MaxSessions issue, still a problem

2001-07-13 Thread Hugh Irvine
quot;. The question here is if it'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:

RE: (RADIATOR) MaxSessions issue, still a problem

2001-07-13 Thread Dmitry Kopylov
- 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 m

Re: (RADIATOR) MaxSessions issue, still a problem

2001-07-12 Thread Hugh Irvine
Hello Dmitry - Here is what I get with this configuration file (copied from your mail): Foreground Trace 4 Secret mysecret RewriteUsername s/^([^@]+).*/$1/ MaxSessions 1 Filename ./bbeyond.users AcctLogFileName %L/bbeyond/details PasswordLogFileName %L/bbeyo

Re: (RADIATOR) MaxSessions issue, still a problem

2001-07-12 Thread Hugh Irvine
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 S

Re: (RADIATOR) MaxSessions issue, still a problem

2001-07-12 Thread Vangelis Kyriakakis
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 P

(RADIATOR) MaxSessions issue, still a problem

2001-07-12 Thread Dmitry Kopylov
Hi, I upgraded to the 18.2.2 but the problem with MaxSession still exists. Here is part of config and trace 4 output: RewriteUsername s/^([^@]+).*/$1/ MaxSessions 1 AcctLogFileName %L/bbeyond/details PasswordLogFileName %L/bbeyond/uunet-password