Date: Sun, 13 Dec 2020 10:37:01 +0100 From: Segreteria <segreteria@delluomo-morettin.com> To: Kristof Provost <kp@FreeBSD.org>, franco@lastsummer.de Cc: freebsd-pf@freebsd.org Subject: Re: net.pf.request_maxcount not working after upgrading from 12.1-RELEASE to 12.2 RELEASE. Message-ID: <0487b724-8e53-8fc5-58c7-182ca33c4071@delluomo-morettin.com> In-Reply-To: <F26268C1-2B32-42C5-9294-585D848EDD0D@FreeBSD.org> References: <02311a9b-e669-0071-f47e-fc1701749213@delluomo-morettin.com> <7394e747-7741-daa8-cf07-4aed2eee76d1@delluomo-morettin.com> <E8A0855A-CDC7-432B-8F79-46602948C657@andric.com> <83A03723-37EE-4462-B9A9-2F9B48114F7A@lastsummer.de> <F26268C1-2B32-42C5-9294-585D848EDD0D@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you both Franco and Kristof. I was not able to make pf work with big tables without workarounds of some kind. Tuning net.pf.request_maxcount in sysctl.conf was not working because this kernel parameter was raised after pf started: so, after boot, I had pf not enabled (because table was too big and this lead to an error) but with kernel parameter set as I meant. Best regards. Nicola Il 12/12/20 21:15, Kristof Provost ha scritto: > On 12 Dec 2020, at 15:07, Franco Fichtner wrote: >>> There's no reason for this to be a tunable. It's perfectly safe to >>> change this at runtime. >> >> Well, RWTUN would have enabled both boot and runtime which is also >> "perfectly safe". :) >> > Good idea. Done in 368588. > > I expect to be bothering people about an EN for the vnet/epair issue > next week, I’ll see if I can include this in the bothering. > > Best regards, > Kristof > _______________________________________________ > freebsd-pf@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-pf > To unsubscribe, send any mail to "freebsd-pf-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0487b724-8e53-8fc5-58c7-182ca33c4071>