From owner-freebsd-doc@FreeBSD.ORG Sat Feb 26 16:04:57 2005 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8BEA16A4CE; Sat, 26 Feb 2005 16:04:57 +0000 (GMT) Received: from ender.liquidneon.com (ender.liquidneon.com [64.78.150.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E30443D58; Sat, 26 Feb 2005 16:04:57 +0000 (GMT) (envelope-from so14k@so14k.com) Received: from localhost (localhost [127.0.0.1]) by ender.liquidneon.com (Postfix) with ESMTP id 548D3440B; Sat, 26 Feb 2005 09:04:56 -0700 (MST) Received: from ender.liquidneon.com ([127.0.0.1]) by localhost (ender.liquidneon.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13081-07; Sat, 26 Feb 2005 09:04:55 -0700 (MST) Received: by ender.liquidneon.com (Postfix, from userid 1000) id A8D5B43E8; Sat, 26 Feb 2005 09:04:55 -0700 (MST) Date: Sat, 26 Feb 2005 09:04:55 -0700 From: Brad Davis To: Tom Rhodes , FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org Message-ID: <20050226160455.GA559@ender.liquidneon.com> Mail-Followup-To: Tom Rhodes , FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org References: <20050226012034.0021ebb4@mobile.pittgoth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050226012034.0021ebb4@mobile.pittgoth.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at ender.liquidneon.com Subject: Re: docs/78096: Add info on setting up ATLQ X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2005 16:04:57 -0000 After going over it again with remko@, here is a new diff. Brad --- doc-ori/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml Fri Feb 25 13:31:41 2005 +++ doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml Sat Feb 26 08:54:37 2005 @@ -198,7 +198,7 @@ - The Packet Filter (PF) Firewall + The OpenBSD Packet Filter (PF) and ALTQ firewall @@ -211,12 +211,13 @@ contained PF as an integrated part of the base system was &os; 5.3 in November 2004. PF is a complete, fully featured firewall - that contains ALTQ for bandwidth usage - management in a way similar to what DUMMYNET provides in - IPFW. The OpenBSD project does an - outstanding job of maintaining the PF users' guide that it will - not be made part of this handbook firewall section as that would - just be duplicated effort. + that has optional support for ALTQ (Alternate + Queuing). ALTQ provides Quality of Service + (QoS) bandwidth shaping that allows guaranteeing bandwidth to + different services based on filtering rules. The OpenBSD + project does an outstanding job of maintaining the PF User's + Guide that it will not be made part of this handbook firewall + section as that would just be duplicated effort. The availability of PF for the various &os; releases and versions is summarized below: @@ -356,6 +357,57 @@ enable the following option as well: gateway_enable="YES" # Enable as Lan gateway + + + + Enabling ALTQ + + ALTQ is only available by compiling the + options into the &os; Kernel. ALTQ is not + supported by all of the available network card drivers. Please + see the &man.altq.4; manual page for a list of drivers that are + supported in your release of &os;. The following options will + enable ALTQ and add additional functionality. + + + options ALTQ +options ALTQ_CBQ # Class Bases Queuing (CBQ) +options ALTQ_RED # Random Early Detection (RED) +options ALTQ_RIO # RED In/Out +options ALTQ_HFSC # Hierarchical Packet Scheduler (HFSC) +options ALTQ_PRIQ # Priority Queuing (PRIQ) +options ALTQ_NOPCC # Required for SMP build + + options ALTQ enables the ALTQ framework. + + options ALTQ_CBQ enables Class Based + Queuing (CBQ). CBQ allows you to divide a connection's + bandwidth into different classes or queues to prioritize + traffic based on filter rules. + + options ALTQ_RED enables Random Early + Detection (RED). RED is used to avoid network congestion. RED + does this by measuring the length of the queue and comparing + it to the minimum and maximum thresholds for the queue. If the + queue is over the maximum all new packets will be dropped. True + to its name, RED drops packets from different connections + randomly. + + options ALTQ_RIO enables Random Early + Detection In and Out. + + options ALTQ_HFSC enables the + Hierarchical Fair Service Curve Packet Scheduler. For more + information about HFSC see: . + + + options ALTQ_PRIQ enables Priority + Queuing (PRIQ). PRIQ will always pass traffic that is in a + higher queue first. + + options ALTQ_NOPCC enables SMP support + for ALTQ. This option is required on SMP systems.