Date: Sat, 12 Dec 2020 14:42:18 +0100 From: Dimitry Andric <dimitry@andric.com> To: freebsd-pf@freebsd.org Subject: Re: net.pf.request_maxcount not working after upgrading from 12.1-RELEASE to 12.2 RELEASE. Message-ID: <E8A0855A-CDC7-432B-8F79-46602948C657@andric.com> In-Reply-To: <7394e747-7741-daa8-cf07-4aed2eee76d1@delluomo-morettin.com> References: <02311a9b-e669-0071-f47e-fc1701749213@delluomo-morettin.com> <7394e747-7741-daa8-cf07-4aed2eee76d1@delluomo-morettin.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12 Dec 2020, at 10:55, Segreteria <segreteria@delluomo-morettin.com> = wrote: >=20 > I can no longer load pf at boot without workarounds as after upgrade = to 12.2-RELEASE net.pf.request_maxcount=3D300000 in /boot/loader.conf is = not loaded before pf starts. >=20 > Can somebody explain exactly why is this happening? Is this a new = policy of this kernel parameter? It seems to have changed with = https://svnweb.freebsd.org/changeset/base/364456: ------------------------------------------------------------------------ r364456 | kp | 2020-08-21 15:11:33 +0200 (Fri, 21 Aug 2020) | 7 lines MFC r355744: pf: Make request_maxcount runtime adjustable There's no reason for this to be a tunable. It's perfectly safe to change this at runtime. ------------------------------------------------------------------------ > What is the suggested way to face this change? I believe it must be set in sysctl.conf(5) after this change. -Dimitry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E8A0855A-CDC7-432B-8F79-46602948C657>