From owner-freebsd-pf@FreeBSD.ORG Thu Nov 17 15:50:42 2005 Return-Path: X-Original-To: freebsd-pf@freebsd.org Delivered-To: freebsd-pf@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA28116A41F for ; Thu, 17 Nov 2005 15:50:42 +0000 (GMT) (envelope-from mt@smtp.top.net.ua) Received: from smtp.top.net.ua (smtp.top.net.ua [193.109.60.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A6A143D46 for ; Thu, 17 Nov 2005 15:50:42 +0000 (GMT) (envelope-from mt@smtp.top.net.ua) Received: from smtp.top.net.ua (localhost [127.0.0.1]) by smtp.top.net.ua (Postfix) with ESMTP id BBA4E5FF78F for ; Thu, 17 Nov 2005 17:50:40 +0200 (EET) Received: by smtp.top.net.ua (Postfix, from userid 1012) id 9E8D15FF78E; Thu, 17 Nov 2005 17:50:40 +0200 (EET) Date: Thu, 17 Nov 2005 17:50:40 +0200 From: Maxim Tuliuk To: freebsd-pf@freebsd.org Message-ID: <20051117155040.GB86099@top.net.ua> References: <437BB031.9090504@seton.org> <200511162319.58857.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511162319.58857.max@love2party.net> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: Traffic Shaping with pf ... X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2005 15:50:42 -0000 On Wed, Nov 16, 2005 at 23:19 +0100, Max Laier wrote: > > on an interface. Since most of the traffic passing through my firewall > > is http and ftp traffic, the inbound direction is the path being > > saturated. Did I read the ALTQ documentation wrong or is there another > > mechanism available for use with pf that could help me prioritize > > bandwidth usage? > > You can not control inbound traffic! You can not control what other people > sent to you! It's impossible. The only way to do it is to limit *outbound* > traffic on an upstream router. But if I'm an ISP, I have to control inbound traffic (botnets, contract agreements etc); in this case rate limit is the simplist and cheapest way -- Maxim Tuliuk WWW: http://primats.org.ua/~mt/ ICQ: 21134222 The bike is absolute freedom of moving