From owner-freebsd-ipfw@FreeBSD.ORG Fri Mar 4 22:53:04 2005 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13AEA16A4CE for ; Fri, 4 Mar 2005 22:53:04 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id A854143D31 for ; Fri, 4 Mar 2005 22:53:03 +0000 (GMT) (envelope-from jsimola@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so826301wri for ; Fri, 04 Mar 2005 14:53:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=loRP4qsjMKjD3ilC+mRvH9IsYdx8ND2s9CfabsotXENNTWAMHNKdsRgyuvXrEzUlzpJFM3jpylsKMch3kb7hMXmFa5WbAIq4XStWSzM3ZTE395TPmulYUF9H03nYQZAW+ckhnlXotYrQUHi4U0+63p/ni5RZ4bqsCc8EfcVn3Ao= Received: by 10.54.63.8 with SMTP id l8mr10992wra; Fri, 04 Mar 2005 14:53:03 -0800 (PST) Received: by 10.54.39.34 with HTTP; Fri, 4 Mar 2005 14:53:02 -0800 (PST) Message-ID: <8eea0408050304145319ffcecd@mail.gmail.com> Date: Fri, 4 Mar 2005 14:53:02 -0800 From: Jon Simola To: Kris McElroy In-Reply-To: <200503041547125.SM01228@KrisLaptop> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <8eea040805030413431f2c1b03@mail.gmail.com> <200503041547125.SM01228@KrisLaptop> cc: freebsd-ipfw@freebsd.org Subject: Re: ipfw+dummynet X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jon@abccomm.com List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Mar 2005 22:53:04 -0000 On Fri, 4 Mar 2005 15:46:34 -0600, Kris McElroy wrote: > So I can not throttle there upload speed, only download? Do you recommend > something else to use besides the above combo? You can throttle their upload speed as it passes through your traffic shaper, but not as they send traffic onto your wireless network. Cust <-> CustRadio <-> BaseRadio <-> Shaper <-> Internet If the customer saturates the wireless link between the radios with traffic, you can't do anything about that at the shaper. But you can control how fast traffic to or from the customer leaves the shaper in either direction. If you're trying to prevent saturation of the wireless link, you need a traffic shaper at each end of it to control traffic across the wireless shot. If you're just trying to keep track of customers bandwidth and not worried about your wireless shot (maybe you've got a full-duplex 100Mbps OFDM shot) then a single shaper would work. Depends a lot on your wireless network. Full mesh, one to many, one to one, etc... -- Jon Simola Systems Administrator ABC Communications