From owner-freebsd-isp Thu Apr 25 07:23:16 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA12555 for isp-outgoing; Thu, 25 Apr 1996 07:23:16 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA12545 for ; Thu, 25 Apr 1996 07:23:14 -0700 (PDT) Received: from dialup-usr11.etinc.com (dialup-usr11.etinc.com [204.141.95.132]) by etinc.com (8.6.12/8.6.9) with SMTP id KAA02623; Thu, 25 Apr 1996 10:28:41 -0400 Date: Thu, 25 Apr 1996 10:28:41 -0400 Message-Id: <199604251428.KAA02623@etinc.com> X-Sender: dennis@etinc.com X-Mailer: Windows Eudora Version 2.0.3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Michael Dillon From: dennis@etinc.com (dennis) Subject: Re: Bandwidth limited FTP server Cc: freebsd-isp@freebsd.org 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? Yes, this can be done back to back. Dennis ---------------------------------------------------------------------------- Emerging Technologies, Inc. http://www.etinc.com Synchronous Communications Cards and Routers For Discriminating Tastes. 56k to T1 and beyond. Frame Relay, PPP, HDLC, and X.25 for BSD/OS, FreeBSD and LINUX