(RADIATOR) MaxSessions issue, still a problem

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

RE: (RADIATOR) AuthBy Radius, limiting Calling ID stations

--- Forwarded mail from [EMAIL PROTECTED] From: [EMAIL PROTECTED] Date: Wed, 11 Jul 2001 19:36:25 -0500 To: [EMAIL PROTECTED] Subject: BOUNCE [EMAIL PROTECTED]:Non-member submission from [Harrison Ng <[EMAIL PROTECTED]>] >From [EMAIL PROTECTED] Wed Jul 11 19:36:25 2001 Received: from lsm01.

Re: (RADIATOR) MaxSessions issue, still a problem

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) radpwtst -noacct -noauth -code Disconnect-Request NAS-Port=xxx

Title: radpwtst -noacct -noauth -code Disconnect-Request NAS-Port=xxx Hi, i need to disconnect an user. When i use radpwtst -noacct -noauth -code Disconnect-Request NAS-Port= logfile tell me: Thu Jul 12 20:35:30 2001: DEBUG: Check if Handler Realm= should be used to handle this

(RADIATOR) not working on HPUX 11i =/

Hey all, I've checked through the mail archives, and tried everything listed, but I still can't get syslog to work for the life of me =/ This is whats in the config: FacilityINFO Trace 4 I've tried DEBUG, LOG_DEBUG, LOG_INFO, etcetcetc. There

Re: (RADIATOR) not working on HPUX 11i =/

Is this 2.18.2? If so, I think I am having the same or similar issues. Chris > From: Jon Nistor <[EMAIL PROTECTED]> > Date: Thu, 12 Jul 2001 17:36:01 -0400 (EDT) > To: <[EMAIL PROTECTED]> > Subject: (RADIATOR) not working on HPUX 11i =/ > > Hey all, > > I've checked through the mail archives

Re: (RADIATOR) not working on HPUX 11i =/

[nistor@outpost2] /opt/radiator/bin: ./radiusd -v This is Radiator 2.18 on outpost2 Copyright Open System Consultants http://www.open.com.au/radiator On Thu, 12 Jul 2001, Chris M wrote: :::Is this 2.18.2? If so, I think I am having the same or similar issues. ::: :::Chris ::: :::> From: Jo

Re: (RADIATOR) radpwtst -noacct -noauth -code Disconnect-Request NAS-Port=xxx

Hello Alain - As the error message in the log file says, you will need a Realm or Handler clause to deal with the Disconnect-Request. You will also need software on the NAS that understands Disconnect-Request. Also note that when the NAS is configured to process Disconnect-Request it is acti

Re: (RADIATOR) MaxSessions issue, still a problem

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) not working on HPUX 11i =/

Hello John, Hello Chris - What platform are you running on? Note that some syslog systems need to be run with the -r flag. >From http://www.open.com.au/radiator/faq.html#66: Recent versions of Linux syslogd do not by default listen to the UDP port that the Perl Sys::Syslog module uses. In or

(RADIATOR) variable question (realm)

Hello guys, Is there a variable that can be used, to log the realm, that the user went through, in an AuthLog SuccessFormat ? Thanks, -Andy -- *** DISCLAIMER *** This e-mail and any attachments thereto may contain information, which is confidential and/or protected by intellectual property ri

Re: (RADIATOR) MaxSessions issue, still a problem

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