From owner-freebsd-stable@freebsd.org Fri Aug 21 00:40:26 2020 Return-Path: Delivered-To: freebsd-stable@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 47DEB3AE1ED for ; Fri, 21 Aug 2020 00:40:26 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BXjNT6C0rz4Frx for ; Fri, 21 Aug 2020 00:40:25 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 07L0eJdJ041184 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Thu, 20 Aug 2020 17:40:25 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 From: Chris Reply-To: bsd-lists@BSDforge.com To: freebsd-stable Subject: net.pf.request_maxcount: UNDESIRABLE_OID Date: Thu, 20 Aug 2020 17:40:25 -0700 Message-Id: <54a0a1c4da6d5add83ecdf2668cf2f7b@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4BXjNT6C0rz4Frx X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Aug 2020 00:40:26 -0000 We've been developing an appliance/server based on FreeBSD && pf(4)=2E We started some time ago, and have been using a very early version of 12=2E We're now collecting some 20,000,000 IP's /mos=2E So we're satisfied we're close to releasing=2E As such, we needed to bring the release up to a supported (freebsd) version (12-STABLE)=2E We would have done so sooner=2E But we need a stable (unchanging) testbed to evaluate what we're working on=2E We built and deployed a copy of 12-STABLE @r363918 that contained our work with pf(4)=2E Booting into it failed unexpectedly with: cannot define table nets: too many elements=2E Consider increasing net=2Epf=2Erequest_maxcount=2E pfctl: Syntax error in config file: pf rules not loaded OK this didn't happen on our testbed prior to the upgrade with a combined count of ~97,000,900 IPs=2E In fact the OID mentioned didn't exist=2E For reference; our testbed provides DNS, www, mail for ~60 domains/hosts, as well as our pf(4) testing=2E We can happily load our tables, and run these services w/8Gb RAM=2E This OID is more a problem than a savior=2E Why not simply return ENOMEM? Isn't that what it used to do? pf=2Econf(5) already facilitates thresholds, and they aren't _read only_=2E Is there any way to turn this OID off; like using a -1 value? Or will we need to simply back out the commit? Thanks in advance for any advice=2E --Chris