From owner-freebsd-hackers@FreeBSD.ORG Fri Jan 2 18:40:53 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E92AD67; Fri, 2 Jan 2015 18:40:53 +0000 (UTC) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 067341C91; Fri, 2 Jan 2015 18:40:52 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.9/8.14.9) with ESMTP id t02IepIX017135; Fri, 2 Jan 2015 13:40:51 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <54A6E60B.5060000@sentex.net> Date: Fri, 02 Jan 2015 13:40:11 -0500 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: [FreeBSD 11 Wishlist] Replacing an OpenBSD Firewall References: <1419995051.3716640.208176841.1676669A@webmail.messagingengine.com> <1420213273.622796.208841861.04300699@webmail.messagingengine.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.75 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jan 2015 18:40:53 -0000 On 1/2/2015 11:53 AM, Adrian Chadd wrote: > On 2 January 2015 at 07:41, Mark Felder wrote: >> UPDATE: >> >> I have everything working except QoS, so thanks for the 6rd gif tunnel >> workaround Nathan. ALTQ being absent from GENERIC is another sore spot >> that should be investigated. > > I'm waiting for Gleb to do up his ifnet changes so we can do ninja > replacements of altq with something that won't cause massive normal > performance problems even if it's not being used. What is to replace pf+altq ? pf+DUMMYNET ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/