From owner-freebsd-isp Wed Sep 10 11:02:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16414 for isp-outgoing; Wed, 10 Sep 1997 11:02:15 -0700 (PDT) Received: from dream.future.net (root@future.net [204.130.134.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA16404 for ; Wed, 10 Sep 1997 11:02:12 -0700 (PDT) Received: from dream.future.net (tomthai@future.net [204.130.134.1]) by dream.future.net (8.8.6/8.6.10) with SMTP id NAA01331; Wed, 10 Sep 1997 13:01:24 -0500 (CDT) Date: Wed, 10 Sep 1997 13:01:24 -0500 (CDT) From: "Tom T. Thai" To: Chris Shenton cc: xenub@boisfrancs.qc.ca, isp@freebsd.org Subject: Re: Limiting users connect time (+ another little question) In-Reply-To: <199709101742.NAA03655@absinthe.i3inc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 10 Sep 1997, Chris Shenton wrote: > On Wed, 10 Sep 1997 12:12:35 -0500 (CDT) > "Tom T. Thai" wrote: > > tomthai> if you are under RADIUS then you can limit each login to one. > > Oh? What Attribute/Value? I haven't seen this in the docs for Livingston > RADIUS. At least not for POTS dial-in, though there is one for ISND to > allow/deny bonding. If this works on some other RADIUS implementation > I'd be interested to hear, too. is use ESVA+n2h2 patch on Livingston RADIUS. http://www.n2h2.com/radius/ thom Password = "password", Sessions = 3 you can set sessions to what ever you want (in your case 1) > > I am unsure how RADIUS would be able to do this, since it has no idea > who's currently on -- no state. So how would RADIUS be able to > accept/reject authentication based on munber of logins? > > Thanks. > .............. .................................... Thomas T. Thai Infomedia Interactive Communications tom@iic.net TEL 612.376.9090 * FAX 612.376.9087