(RADIATOR) Force Disconnect

Sun Mar 10 15:53:11 CST 2002

Hello Ross -

You will have to check with your NAS vendors. The Disconnect-Request is 
relatively recent and you will only find support for it in later releases of 
software (if its supported at all).

regards

Hugh

On Sat, 9 Mar 2002 13:25, Ross Kusler wrote:
> Hugh or anyone else,
>
>     What NAS types are known to implement the Radius Disconnect-Request ?
> Does anyone know how to enable it for 3com and/or Ascend equipment?
>
> Ross Kusler
> Senior Database Administrator
> InReach Internet Communications LLC
> ross at inreach.com
>
> ----- Original Message -----
> From: "Hugh Irvine" <hugh at open.com.au>
> To: "Ross Kusler" <ross at inreach.com>; <radiator at open.com.au>
> Sent: Sunday, February 24, 2002 9:59 PM
> Subject: Re: (RADIATOR) Force Disconnect
>
> > Hello Ross -
> >
> > In general it is a bad idea to use SNMP for this sort of thing because it
>
> is
>
> > too easy to hack. You are much better off using the specific radius
> > Disconnect-Request that is now supported in most recent releases of NAS
> > software. Otherwise you can write a script that will log in to the NAS
> > and issue whatever command is required to disconnect a session.
> >
> > regards
> >
> > Hugh
> >
> > On Mon, 25 Feb 2002 14:35, Ross Kusler wrote:
> > > Hello everyone,
> > >
> > >     I've got a network with modems from several different vendors. 
> > > I've noticed that in Radiator's Nas.pm there is a disconnect function
> > > for the Ascends.  disconnectUser calls disconnectUserAscend which
> > > issues an snmp call to reset the port.
> > >
> > >     Is there a similiar way to disconnect users from non-Ascend NAS's?
> > > Does anyone know the OID's?  In particular I'm looking for 3com
> > > TotalControls.  We've also got a few old Netservers, but I suspect I'll
> > > have to modify pmwho to issue a disconnect when it telnets.
> > >
> > >     Has anyone done this?
> > >
> > > Ross Kusler
> > > ross at inreach.com
> >
> > --
> > 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.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.

-- 
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, extensibFrom owner-radiator at open.com.au Sun Mar 10 14:29:00 2002
Received: (from majordomo at localhost)
	by server1.open.com.au (8.11.0/8.11.0) id g2AKT0A01310
	for radiatorzz-list; Sun, 10 Mar 2002 14:29:00 -0600
X-Authentication-Warning: server1.open.com.au: majordomo set sender to owner-radiator at open.com.au using -f
Received: from entoo.connect.com.au (entoo.connect.com.au [192.189.54.8])
	by server1.open.com.au (8.11.0/8.11.0) with ESMTP id g2AKSw301302
	for <radiator at open.com.au>; Sun, 10 Mar 2002 14:28:58 -0600
Received: from there (acc22-ppp15.mel.dialup.connect.net.au [210.10.141.15])
	by entoo.connect.com.au (Postfix) with SMTP
	id CFAF0E34C1; Mon, 11 Mar 2002 08:54:55 +1100 (EST)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Hugh Irvine <hugh at open.com.au>
Reply-To: hugh at open.com.au
Organization: Open System Consultants
To: "Barry Andersson" <barry at simplex.net.au>, radiator at open.com.au
Subject: Re: (RADIATOR) Restricting login by NAS
Date: Mon, 11 Mar 2002 08:56:58 +1100
X-Mailer: KMail [version 1.3.1]
References: <200203090357.g293vTW11460 at mail.simplex.net.au>
In-Reply-To: <200203090357.g293vTW11460 at mail.simplex.net.au>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <20020310215455.CFAF0E34C1 at entoo.connect.com.au>
Sender: owner-radiator at open.com.au
Precedence: bulk
List-Id: <radiator.list-id.open.com.au>

Hello Barry -

The best way to do this is by setting the Identifier tag in each of your 
Client clauses, then using the Client-Identifier check item.

For example:

<Client .....>
	Identifier xxxxx
	.....
</Client>

<Client .....>
	Identifier xxxxx
	.....
</Client>

<Client .....>
	Identifier yyyyy
	.....
</Client>

...etc...

Doing it this way is much easier to understand and you don't need regular 
expressions.

regards

Hugh

On Sat, 9 Mar 2002 14:57, Barry Andersson wrote:
> Hi,
>
> Can anyone help with the Check Item Perl expression to enable us to
> ensure that certain users cannot login via particular NAS?
>
> That is, we want some users to be able to dial in via any NAS except
> aaa.bbb.ccc.ddd and www.xxx.yyy.zzz .
>
> Barry Andersson
>
> ===
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.

-- 
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.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.
le,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.