From owner-freebsd-net@freebsd.org  Sun Oct 28 02:57:00 2018
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 330FC10DFDE2
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sun, 28 Oct 2018 02:57:00 +0000 (UTC)
 (envelope-from pz-freebsd-net@ziemba.us)
Received: from osmtp.ziemba.us (osmtp.ziemba.us [208.106.105.149])
 (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 970A56BC40
 for <freebsd-net@freebsd.org>; Sun, 28 Oct 2018 02:56:59 +0000 (UTC)
 (envelope-from pz-freebsd-net@ziemba.us)
Received: from hairball.ziemba.us (localhost.ziemba.us [127.0.0.1])
 by hairball.ziemba.us (8.15.2/8.15.2) with ESMTP id w9S2mXwn043741
 for <freebsd-net@freebsd.org>; Sat, 27 Oct 2018 19:48:33 -0700 (PDT)
 (envelope-from pz-freebsd-net@ziemba.us)
Received: (from mailnull@localhost)
 by hairball.ziemba.us (8.15.2/8.15.2/Submit) id w9S2mXDD043740
 for freebsd-net@freebsd.org; Sat, 27 Oct 2018 19:48:33 -0700 (PDT)
 (envelope-from pz-freebsd-net@ziemba.us)
X-Authentication-Warning: hairball.ziemba.us: mailnull set sender to
 pz-freebsd-net@ziemba.us using -f
Received: (from news@localhost)
 by usenet.ziemba.us (8.14.5/8.14.5/Submit) id w9S2mVw3001828
 for treehouse-mail-freebsd-net@hairball.ziemba.us;
 Sat, 27 Oct 2018 19:48:31 -0700 (PDT) (envelope-from news)
From: "G. Paul Ziemba" <pz-freebsd-net@ziemba.us>
To: freebsd-net@freebsd.org
Subject: bridge interface vs. altq
Date: Sun, 28 Oct 2018 02:48:31 +0000 (UTC)
Message-id: <pr381v$1p3$1@usenet.ziemba.us>
Reply-to: unp@ziemba.us
Errors-to: "G. Paul Ziemba" <unp@ziemba.us>
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Oct 2018 02:57:00 -0000

I recently upgraded a system from FreeBSD 9.2 to 12.1-BETA1 and found
that pf on the new system complained that my bridge interface did not
support ALTQ (worked fine on 9.2)

The new kernel is built with

    OPtions         ALTQ
    options         ALTQ_CBQ
    options         ALTQ_CODEL
    options         ALTQ_RED
    options         ALTQ_RIO
    options         ALTQ_HFSC
    options         ALTQ_CDNR
    options         ALTQ_PRIQ
    options         ALTQ_FAIRQ
    options         ALTQ_NOPCC

and it seems to have no issues configuring altq on "re" and "dc"
interfaces.

I searched but could not find any mention of removal of altq support
from "bridge," and in fact the current handbook seems to indicate
it is supported [www.freebsd.org/doc/handbook/network-bridging.html]:

    Note: Packet filtering can be used with any firewall package
    that hooks into the pfil(9) framework. The bridge can be used
    as a traffic shaper with altq(4) or dummynet(4).

What am I missing?

thanks!
-- 
G. Paul Ziemba
FreeBSD unix:
 7:46PM  up  4:50, 9 users, load averages: 0.52, 0.41, 0.32