From owner-freebsd-pf@freebsd.org  Mon Jul 29 18:22:55 2019
Return-Path: <owner-freebsd-pf@freebsd.org>
Delivered-To: freebsd-pf@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 987D7B1A23
 for <freebsd-pf@mailman.nyi.freebsd.org>; Mon, 29 Jul 2019 18:22:55 +0000 (UTC)
 (envelope-from mike@sentex.net)
Received: from pyroxene.sentex.ca (unknown [IPv6:2607:f3e0:0:3::18])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "pyroxene.sentex.ca",
 Issuer "Let's Encrypt Authority X3" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 776A18E330;
 Mon, 29 Jul 2019 18:22:55 +0000 (UTC) (envelope-from mike@sentex.net)
Received: from [IPv6:2607:f3e0:0:4:346a:6987:6201:ec77]
 ([IPv6:2607:f3e0:0:4:346a:6987:6201:ec77])
 by pyroxene.sentex.ca (8.15.2/8.15.2) with ESMTPS id x6TIMsEr063315
 (version=TLSv1.2 cipher=AES128-SHA bits=128 verify=NO);
 Mon, 29 Jul 2019 14:22:55 -0400 (EDT) (envelope-from mike@sentex.net)
Subject: Re: pf and dummynet
To: Kristof Provost <kp@freebsd.org>,
 Paul Webster <paul.g.webster@googlemail.com>
Cc: "freebsd-pf@freebsd.org" <freebsd-pf@freebsd.org>
References: <d68129cd-40a4-e065-32c3-3f574eca537e@sentex.net>
 <5d3f305f.1c69fb81.90047.531f@mx.google.com>
 <20190729175134.GE10541@vega.codepro.be>
From: mike tancsa <mike@sentex.net>
Message-ID: <8e58346b-5540-b47e-e446-1a5bb11743d3@sentex.net>
Date: Mon, 29 Jul 2019 14:22:54 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <20190729175134.GE10541@vega.codepro.be>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Rspamd-Queue-Id: 776A18E330
X-Spamd-Bar: ------
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-6.97 / 15.00];
 NEURAL_HAM_MEDIUM(-1.00)[-1.000,0];
 NEURAL_HAM_SHORT(-0.97)[-0.975,0];
 NEURAL_HAM_LONG(-1.00)[-1.000,0]; TAGGED_RCPT(0.00)[];
 REPLY(-4.00)[]
X-BeenThere: freebsd-pf@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Technical discussion and general questions about packet filter
 \(pf\)" <freebsd-pf.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-pf>,
 <mailto:freebsd-pf-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-pf/>
List-Post: <mailto:freebsd-pf@freebsd.org>
List-Help: <mailto:freebsd-pf-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-pf>,
 <mailto:freebsd-pf-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2019 18:22:55 -0000

On 7/29/2019 1:51 PM, Kristof Provost wrote:
>
> Also beware of gotchas with things like IPv6 fragment handling or
> route-to.
>
> I do not consider mixing firewalls to be a supported configuration. If
> it breaks you get to keep the pieces.

Thanks, I was worried about that!  Is there a way to get altq to limit
inbound traffic directed to a server ?  I would prefer not mixing and
matching, but I dont see any other way other than going to ipfw which I
would rather not

    ---Mike