Large scale NAT with PF - some weird problem
Milan Obuch
freebsd-pf at dino.sk
Sun Jun 21 17:58:05 UTC 2015
On Sun, 21 Jun 2015 08:38:04 -0400
Ian FREISLICH <ian.freislich at capeaugusta.com> wrote:
[ snip ]
> > One observation, on pfctl -vs info output - when src-limit counters
> > rises to 30 or so, I am getting first messages someone has problem.
> > Is it only coincidence or is there really some relation to my
> > problem?
>
> Perhaps. These are the options I had set. You probably don't want
> the if-bound one.
>
Well, it hit me again, and I am not sure there is any relation. Anyway,
I tried pfctl -F with various classes, even all, but nothing helped.
Only after /etc/rc.d/pf restart affected clients begun to work again.
> # Options
> # ~~~~~~~
> set timeout { \
> adaptive.start 900000, \
> adaptive.end 1800000 \
> }
> set block-policy return
> set state-policy if-bound
> set optimization normal
> set ruleset-optimization basic
> set limit states 1500000
> set limit frags 40000
> set limit src-nodes 150000
>
> --- /etc/sysctl.conf ---
> net.inet.ip.fastforwarding=1
> ---
>
I think I have set it up similarly. I think there could be some bug
hitting me, but no idea how to check and what.
> I also had some other settings regarding interrupt moderation on
> the NIC, netisr threads, queue depth and dispatch. I disabled
> entropy harvesting on interrupts, and the network path. Some of
> these settings are loader.conf settings, some are runtime sysctls.
>
> I still think that if it's possible, you should give 10-STABLE a
> try.
>
This will take some time to do. Unfortunatelly, I did not think about
possibilities to test various version when the system was installed. My
bad. Now it is not easy, but I am trying to find usable way to do it.
Regards,
Milan
More information about the freebsd-pf
mailing list