Re: net.pf.request_maxcount not working after upgrading from 12.1-RELEASE to 12.2 RELEASE.

2020-12-13 Thread Segreteria
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

Re: net.pf.request_maxcount not working after upgrading from 12.1-RELEASE to 12.2 RELEASE.

2020-12-12 Thread Kristof Provost
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 abou

Re: net.pf.request_maxcount not working after upgrading from 12.1-RELEASE to 12.2 RELEASE.

2020-12-12 Thread Franco Fichtner
> 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". :) Cheers, Franco ___ freebsd-pf@freebsd.org mailing list https://lis

Re: net.pf.request_maxcount not working after upgrading from 12.1-RELEASE to 12.2 RELEASE.

2020-12-12 Thread Dimitry Andric
On 12 Dec 2020, at 10:55, Segreteria wrote: > > I can no longer load pf at boot without workarounds as after upgrade to > 12.2-RELEASE net.pf.request_maxcount=30 in /boot/loader.conf is not > loaded before pf starts. > > Can somebody explain exactly why is this happening? Is this a new pol

net.pf.request_maxcount not working after upgrading from 12.1-RELEASE to 12.2 RELEASE.

2020-12-12 Thread Segreteria
Hi everybody, I can no longer load pf at boot without workarounds as after upgrade to 12.2-RELEASE net.pf.request_maxcount=30 in /boot/loader.conf is not loaded before pf starts. Can somebody explain exactly why is this happening? Is this a new policy of this kernel parameter? What is