From owner-freebsd-isp Tue Sep 10 10:07:55 1996 Return-Path: owner-isp Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA27640 for isp-outgoing; Tue, 10 Sep 1996 10:07:55 -0700 (PDT) Received: from mail.calweb.com (mail.calweb.com [165.90.138.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA27635 for ; Tue, 10 Sep 1996 10:07:52 -0700 (PDT) Received: from web1.calweb.com (rdugaue@web1.calweb.com [165.90.138.10]) by mail.calweb.com (8.7.5/8.7.3) with SMTP id KAA01612; Tue, 10 Sep 1996 10:00:55 -0700 (PDT) Date: Tue, 10 Sep 1996 10:00:54 -0700 (PDT) From: Robert Du Gaue To: Greg Wiley cc: FreeBSD ISP List Subject: Re: T1 offc. resell config In-Reply-To: <199609101530.IAA01068@patty.loop.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Why not take a look at the product from emerging technologies (on their website). It's about $500, you put a second nic in your FreeBSD box, and then your able to throttle traffic coming from any IP through that Nic. On Tue, 10 Sep 1996, Greg Wiley wrote: > Date: Tue, 10 Sep 1996 08:31:27 +0000 > From: Greg Wiley > To: FreeBSD ISP List > Subject: Re: T1 offc. resell config > > If you fractionalize your T-span, you'll need a routing port or > switched virtual circuit port for each fraction you sell. Why not, > instead, create an ethernet backbone resource for the building and > charge tenants to hang on to that? You'll be capitalizing on the > bursty nature of Inet traffic and so maintaining higher throughput > for individual transactions. > > If you want differentiate usage levels, you could set up some kind > of IP accounting but it might not be worth it. > > -greg > -------------------------------------------------------------------------- Robert Du Gaue - rdugaue@calweb.com http://www.calweb.com President, CalWeb Internet Services Inc. (916) 641-9320 --------------------------------------------------------------------------