Interestingly one of our machines in the office was doing it. Havent bothered
to find out why yet.
Decided that I would push up the default conntrack size as per below anyway.
Thanks for all your help guys.
Regards
Michael Knill
On 7/10/20, 5:07 pm, "Michael Knill" wrote:
Thanks guys
Thanks guys
Not sure why this would be happening on this system as I have much busier ones
that are fine but I will have a look next time it happens.
Regards
Michael Knill
On 7/10/20, 12:23 pm, "Lonnie Abelbeck" wrote:
Thanks Darrick,
If you have a very busy (network) system, you ca
Thanks Darrick,
If you have a very busy (network) system, you can set in your user.conf
--
CONNTRACK=65536
--
or some higher power of 2 ... that will survive a reboot. Though higher values
will use more RAM.
BTW, CONNTRACK is a firewall variable.
Lonnie
> On Oct 6, 2020, at 7:19 PM, darric
Hi Michael,
I have seen this error on our system from time to time. If you are on a
relatively busy network, you could exceed the 16384 value potentially. You can
echo a larger value to that setting in /proc/sys/net but it will not survive a
reboot.
If you have a relatively small network, Lo
Hi Michael,
I have never personally witnessed this error, but I am aware it can happen if
the conntrack state table is full.
By default CONNTRACK=16384 which sets the conntrack state table size.
View the number states:
System tab -> Firewall States
--
NNN Total Firewall States
--
Look to see
