From owner-freebsd-isp Wed Apr 24 14:38:25 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA28143 for isp-outgoing; Wed, 24 Apr 1996 14:38:25 -0700 (PDT) Received: from okjunc.junction.net (okjunc.junction.net [199.166.227.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA28118 for ; Wed, 24 Apr 1996 14:38:12 -0700 (PDT) Received: from sidhe.memra.com (sidhe.memra.com [199.166.227.105]) by okjunc.junction.net (8.6.11/8.6.11) with SMTP id OAA07603 for ; Wed, 24 Apr 1996 14:48:35 -0700 Date: Thu, 25 Apr 1996 14:34:04 -0700 (PDT) From: Michael Dillon To: freebsd-isp@FreeBSD.ORG Subject: Re: Bandwidth limited FTP server In-Reply-To: <199604241718.NAA00894@etinc.com> Message-ID: Organization: Memra Software Inc. - Internet consulting MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Apr 1996, dennis wrote: > >Still no practical ideas about bandwidth limiting? > > One interesting way would be to get a frame-relay line with 2 DLCIs and > assign one of them to the FTP server. Use our bandwidth limiting > software to limit traffic on the FTP server DLCI. this would effectively > do what you want for virtually no additonal cost. > > Or you could run a separate server using a NM cable locally. Does a Frame Relay switch need to be in the loop? Or can you run two FreeBSD boxes back to back with ET cards in them to accomplish the same thing, i.e. a T1 link with multiple DLCI's eah one with a different bandwidth limit? Michael Dillon Voice: +1-604-546-8022 Memra Software Inc. Fax: +1-604-546-3049 http://www.memra.com E-mail: michael@memra.com