https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #17 from Max ---
(In reply to Kristof Provost from comment #15)
You are right. It is not the problem. But it looks quite similar.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #16 from Max ---
(In reply to noah.bergbauer from comment #14)
I'll try to reproduce the problem. But I need some starting point. Rules, dead
connections state entries... Anything?
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #15 from Kristof Provost ---
(In reply to noah.bergbauer from comment #14)
Given the nature of your workaround and what we've seen from Dtrace I don't
think that #217997 is the problem.
I'm also pretty sure
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #14 from noah.bergba...@tum.de ---
(In reply to Max from comment #13)
Maybe, maybe not. The point of my workaround is to get a mostly functioning
machine. However, the reboot right before this period was necessary because for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #13 from Max ---
(In reply to noah.bergbauer from comment #12)
> Status: Enabled for 1 days 14:44:53
Have you had any issues during this period?
And do you know which rule produces expired states?
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222126
--- Comment #12 from noah.bergba...@tum.de ---
set limit { states 10, src-nodes 1 }
One of my first attempts to fix this was increasing both limits 10x - didn't
help though.
# pfctl -vsi
No ALTQ support in kernel
ALTQ related