From owner-freebsd-pf@freebsd.org Tue Jul 18 09:40:54 2017 Return-Path: Delivered-To: freebsd-pf@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62FD5CFD8BD for ; Tue, 18 Jul 2017 09:40:54 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2ACF267C63 for ; Tue, 18 Jul 2017 09:40:54 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1dXOzu-00048L-26; Tue, 18 Jul 2017 11:40:54 +0200 Date: Tue, 18 Jul 2017 11:40:54 +0200 From: Kurt Jaeger To: Goran Meki Cc: freebsd-pf@freebsd.org Subject: Re: ALTQ in GENERIC Message-ID: <20170718094053.GH39925@home.opsec.eu> References: <20170718091346.pptwadhexsrkrqwv@hal9000.meka.no-ip.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170718091346.pptwadhexsrkrqwv@hal9000.meka.no-ip.org> X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 18 Jul 2017 09:40:54 -0000 Hi! > I was wondering, why is ALTQ not compiled in GENERIC? ALTQ was imported from OpenBSD, and OpenBSD decided to remove ALTQ a while ago. So FreeBSD plans to drop ALTQ, too. http://bsdly.blogspot.de/2011/07/anticipating-post-altq-world.html with some update in 2015 explains a bit. Then there's https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409 which has some details -- if you ask around, maybe the people from that PR can explain more about it. -- pi@opsec.eu +49 171 3101372 3 years to go !