Hello Matt -
As always I will need to see a copy of the configuration file together
with a trace 4 debug from Radiator showing what is happening.
regards
Hugh
On Thursday, Jun 26, 2003, at 20:36 Australia/Melbourne, Matt Taylor
wrote:
Hi,
We seem to have developed an issue along the way
Hello William -
On Thursday, Feb 13, 2003, at 11:06 Australia/Melbourne, William Taylor
wrote:
OK heres what I want to do:
I would like to use Simultaneous-Use to limit ports to users.
I read that you are supposed to use it as a check item.
Im using a PostAuthHook called addReply to add
Hello Michael -
To do what you describe, you will need to specify a
DefaultSimultaneousUse 1 in your AuthBy clause, then add different
Simultaneous-Use check items for those users with different limits
(Note: do *not* specify MaxSessions ..).
regards
Hugh
On Thursday, Jan 2, 2003, at
I didn't know PM3's supported SNMP. You might want to find out whether SNMP
or Finger works with your equipment. If SNMP, you might want to specify an
SNMPCommunity entry for the Client.
Also, look in /var/log/radiator/radius.log and it will show you what
Radiator tries to do when it should be
Hello Jonathon -
I will need to see the trace debug from Radiator to see what is going on.
thanks
Hugh
At 9:34 -0700 01/7/6, Jonathon Lindbo wrote:
Hi,
I have been trying for the past 4 days to get my Simultaneous Login
restrictions to work. I am currently working with PM3's and have
Hello James -
Use different Handlers, one for your news server and one for your other
authentication with appropriate AuthBy's and DefaultSimultaneousUse.
hth
Hugh
On Friday 11 May 2001 12:15, James Laszko wrote:
We use authentication on our news servers for our customers. When a
Hello Janet -
What you are trying to do below will not work. Two different session
databases are for two different populations of users, and the same username
can exist in both, but subject to different limits.
If you want to check both session databases, you will have to write some
custom
Hello David -
On Tue, 21 Nov 2000, David Moya wrote:
Hi,
I have an DBM session database and I'm having problems with Simultaneous-Use
parameter.
I have configured Simultaneous-Use = 1 in the main Realm and user by user too,
but it doesn't works. Where's the problem? It's possible to
Hello Philip -
I replied to this mail last week.
I have some question regarding the entire radius system what =
creates the session-id is it the radius daemon or the terminal servers.
The terminal server (NAS) creates the session-id.
Another question, I have a problem
Hello Charlie -
There are a number of options, depending on what exactly you want to do.
Basically, Radiator can use a session database to control individual
simulataneous use, or it can use the AuthBy PORTLIMITCHECK clause to do much
more sophisticated port limit checking. You should have a
ilable. Simultaneous use is not per
NAS, i.e.,
simultaneous use must be checked for on all 12 of the NAS'S.
Thanks for your help,
William
-Original Message-
From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 20, 2000 3:48 AM
To: William Hernandez; Radiator
Subjec
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 20, 2000 10:37 PM
To: William Hernandez; Radiator
Subject: RE: (RADIATOR) Simultaneous-use in 2.15
Hello William -
What you are describing below can be accomplished very easily by
using a
Session Database. I have posted several responses
:
[EMAIL PROTECTED]
Date: Thu, 20 Jul 2000 12:20:52 -0600
To: [EMAIL PROTECTED]
From: Chris M [EMAIL PROTECTED]
Subject: Re: (RADIATOR) Simultaneous-Use Problems - IMPORTANT
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
On Thu, 20 Jul 2000, Hugh Irvine wrote:
References:
[EMAIL PROTECTED]
0007210935034Z.00896@hugo
Date: Thu, 20 Jul 2000 19:27:12 -0600
To: [EMAIL PROTECTED]
From: Chris M [EMAIL PROTECTED]
Subject: Re: (RADIATOR) Simultaneous-Use Problems - IMPORTANT
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Hello
Hello Chris -
On Thu, 20 Jul 2000, Hugh Irvine wrote:
A better approach to maintaining session database coherency is to use
strict checking of the NAS. This is what the NasType parameter is used
for in the Client clauses (see section 6.4.5 in the Radiator 2.16.1
reference
Hello Chris -
On Fri, 21 Jul 2000, David Lloyd wrote:
On Thu, 20 Jul 2000, Hugh Irvine wrote:
A better approach to maintaining session database coherency is to use
strict checking of the NAS. This is what the NasType parameter is used
for in the Client clauses (see section
Hello everyone -
Thanks to the other members of the list who have posted follow ups to this
message. I thought I might take this opportunity to address the
Simultaneous-Use issue again.
The thing to keep in mind here is that Radiator can only go on what it sees
reported by the NAS equipment
lixto" was already logged in on max3 at
Wed Jul 19 12:11:59 2000: Login OK: [hmcalixto] (max3)
Thanks in advance.
William
-Original Message-
From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 18, 2000 7:32 PM
To: William Hernandez; Radiator
Subject: Re:
3:48 AM
To: William Hernandez; Radiator
Subject: RE: (RADIATOR) Simultaneous-use in 2.15
Hello William -
Thanks for sending the log file.
The log shows that the user is indeed being rejected by the first AuthBy
clause, but your configuration file has an AuthByPolicy of
ContinueUntilAccept,
so it
On Thu, 20 Jul 2000, Hugh Irvine wrote:
A better approach to maintaining session database coherency is to use
strict checking of the NAS. This is what the NasType parameter is used
for in the Client clauses (see section 6.4.5 in the Radiator 2.16.1
reference manual). Note that there is a new
Hello David -
On Fri, 21 Jul 2000, David Lloyd wrote:
On Thu, 20 Jul 2000, Hugh Irvine wrote:
A better approach to maintaining session database coherency is to use
strict checking of the NAS. This is what the NasType parameter is used
for in the Client clauses (see section 6.4.5 in the
Hello,
I have this problem occasinality with my dial-up users. It seems Radiator
some times does not erase the user from the current logged table (used to
check the simultaneous use). So, I shutdown the server and start it again
and all works fine.
I change my Radiator setup to use a database
y 18, 2000 7:32 PM
To: William Hernandez; Radiator
Subject: Re: (RADIATOR) Simultaneous-use in 2.15
Hello William -
I will need to see a trace 4 debug as well as what you have sent this time.
thanks
Hugh
On Wed, 19 Jul 2000, William Hernandez wrote:
Hello everyone,
I'm having proble
On Wed, 19 Jul 2000, Jeremy Gault wrote:
Hi,
We are running Radiator (its either the 2.13 series or 2.14) and
3Com Total Control HiPer ARC terminal servers. We're having a problem
with the Simultaneous-Use feature.
Our regular dialup customers (and 64K ISDN) accounts are
Hello William -
I will need to see a trace 4 debug as well as what you have sent this time.
thanks
Hugh
On Wed, 19 Jul 2000, William Hernandez wrote:
Hello everyone,
I'm having problems getting the simultaneous-use check item to work. I've
tried using the internal SessionDatabase and
Hello Jason -
I am using Radiator-2.14.1 w/ Platypus using the RadiusNT extension and
using AuthByEmerald in Radiator.
I would like to make it so most AccountTypes are limited to 1 simultaneous
login, while others are 2 or more simultaneous.
(In the RadiusNT portion of Plat, an
Hello Sean -
Anyone,
Is there a way to completely turn off any session checking in radiator 2.15?
According to the docs, if you leave out the SessionDatabase tags, radiator
still uses an internal hash to track simultaneous logins. Is it as simple
as excluding the Simultaneous-Use in
Hello -
On Thu, 25 May 2000, Le Anh Tuan wrote:
Hello,
I'm planning to use a NT 2000 Advance Server as a Remote Access
Server, authenticated by Radiator. Every thing works fine, a client can dialup
to NT 2000 with an attached multiport, authenticates and receives IP address
from Radiator.
: Hugh Irvine [EMAIL PROTECTED]
To: Clement [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, May 18, 2000 12:24 PM
Subject: Re: (RADIATOR) Simultaneous use - Using ping test
Hi Clement -
On Thu, 18 May 2000, Clement wrote:
We are renting some ports from another ISP who
Hello Raju -
On Fri, 14 Apr 2000, Raju M. Daryanani wrote:
Is it possible to set up Radiator so that maxsessions can be enforced across
iPass as well as local dial-up?
Sure. Use either MaxSessions in the realm, or DefaultSimultaneousUse in the
AuthBy.
hth
Hugh
--
Radiator: the most
Hello John -
On Sat, 08 Jan 2000, [EMAIL PROTECTED] wrote:
I'm having a problem with the new version of radiator
such that it is rejecting more than one usage of the same
username in a handler even though there are no limits
on how many of this particular username can login. I have
had
I am having the similar problem, Is there a way to check/flush the contents
of the internal sessions list which stores all the current calls online?
Radiator says that the that the Simultaneous-Use=1 has been exceeded, but in
fact there are no logins for that user on our NAS.
-Original
Hello Sergio -
On Wed, 03 Nov 1999, Sergio Gonzalez wrote:
*This message was transferred with a trial version of CommuniGate(tm) Pro*
Hi there. Somebody can tell me how to make a flush of the internal user
table radiator maintains when using simultaneous-use?.. I got someone
hooked and I
Hello Dawn -
On Fri, 15 Oct 1999, Dawn Lovell wrote:
We've had two problems with concurrent login checking that I wanted to run
by everyone. We're running 2.13.1 on a mix of Solaris 2.5.1 and Solaris 7
boxes; we have the snmpget from UCD SNMP (v3.6). Please pardon my ignorance
on some of
.
On Fri, 18 Jun 1999, Mike McCauley wrote:
Hi James.
On Jun 17, 12:41pm, James H. Thompson wrote:
Subject: Re: (RADIATOR) Simultaneous use
On Mon, 14 Jun 1999, Mike McCauley wrote:
Hi James.
On Jun 11, 2:21am, James H. Thompson wrote:
Subject: Re: (RADIATOR) Simultaneous use
On Mon, 14 Jun 1999, Mike McCauley wrote:
Hi James.
On Jun 11, 2:21am, James H. Thompson wrote:
Subject: Re: (RADIATOR) Simultaneous use
Since the NAS reply items are different for each NAS, I'd have to setup
3 full sets of check/reply items for each user. That sounds like
too much
Hi James.
On Jun 17, 12:41pm, James H. Thompson wrote:
Subject: Re: (RADIATOR) Simultaneous use
On Mon, 14 Jun 1999, Mike McCauley wrote:
Hi James.
On Jun 11, 2:21am, James H. Thompson wrote:
Subject: Re: (RADIATOR) Simultaneous use
Since the NAS reply items are different
the Auth request has already been denied?
Perhaps this clean up should happen on the auth request or on both
auth and acct?
Jim
On Fri, 18 Jun 1999, Mike McCauley wrote:
Hi James.
On Jun 17, 12:41pm, James H. Thompson wrote:
Subject: Re: (RADIATOR) Simultaneous use
On Mon, 14 Jun 1999,
Hi James.
On Jun 12, 1:58am, James H. Thompson wrote:
Subject: Re: (RADIATOR) Simultaneous use
In the Radiator manual at:
http://www.open.com.au/radiator/ref.html#pgfId=330971
in Section 14 it says:
14.0 Rewriting user names
You can change the User-Name attribute in each request
Hi James.
For complicated reasons, that wont work the way you expect, even if you use the
DefaultSimultaneousUse parameter I mentioned recently. I think you will have to
set up a full set of check and reply items for each special user. There are
other ways to tackle this, involving chaining FILE
Since the NAS reply items are different for each NAS, I'd have to setup
3 full sets of check/reply items for each user. That sounds like
too much work. How would I do it by chaining the File authentications?
Since I'm using SQL Auth, Would this work?
Set DefaultSimultaneousUse to 1
Create a
On Thu, 25 Mar 1999, Mike McCauley wrote:
OK, due to popular demand I have added a new parameter to AuthBy.
DefaultSimultaneousUse specifies a sim-use limit that will apply if there is no
user-specific Simultaneous-Use check item.
Would the interested people like to download a new
On Tue, 23 Mar 1999, Mike McCauley wrote:
Im thinking of doing exactly that, but Im toying with whether or not
DefaultSessionMax (or whatever I call it) should be a Handler/realm parameter
or an AuthBy parameter?
MaxSession (for better or worse) is a Handler/Realm parameter.
Views?
At
On Mon, 22 Mar 1999, True Communications Corp. wrote:
defined to 1 as the default for all users in the users file. I was under the
impression
that you can override the default for any of the users by using the
Simultaneous-Use
attribute in the users file. Which is exactly what I did.
01
Subject: Re: (RADIATOR) Simultaneous-Use question
I believe that which ever is lowest, takes affect. So if your Maxsessions
is 1, and your Sim-Use is 2, it will only alow 1. However, in your users
file, you can put Sim-Use = 1 for the DEFAULT users, and SIm-Use = x for
ones that you want
On Feb 20, 1:10pm, Ricardo Freire wrote:
Subject: Re: (RADIATOR) Simultaneous-Use question
Thanks to all!
Now I understand this check item clearly.
But I'm still in trouble:
If I comment MaxSessions line, everyone can connect more than once at a
time.
Since all my users
46 matches
Mail list logo
