From owner-freebsd-isp Wed Apr 24 10:14:51 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id KAA02319 for isp-outgoing; Wed, 24 Apr 1996 10:14:51 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA02312 for ; Wed, 24 Apr 1996 10:14:50 -0700 (PDT) Received: from etinc.com (etinc.com [204.141.244.98]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id KAA28227 for ; Wed, 24 Apr 1996 10:14:41 -0700 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 NAA00894; Wed, 24 Apr 1996 13:18:20 -0400 Date: Wed, 24 Apr 1996 13:18:20 -0400 Message-Id: <199604241718.NAA00894@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: ishort@pcm.co.za 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 >Hi Again > >Well, I did look at wu-ftpd. That is fine for limiting users in a >class. > >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. 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