You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In high load scenarios, where we have lots of NATs being created/destroyed/logged there can be lost of messages by syslog daemon. This happens because PFNATTRACK wait for PFTM_INTERVAL (default 15s) and then send all log messages at once, overloading the syslog server.
Maybe it would be better to split the log messages into small peaces of data.
Regards, Italo
The text was updated successfully, but these errors were encountered:
Hello,
In high load scenarios, where we have lots of NATs being created/destroyed/logged there can be lost of messages by syslog daemon. This happens because PFNATTRACK wait for PFTM_INTERVAL (default 15s) and then send all log messages at once, overloading the syslog server.
Maybe it would be better to split the log messages into small peaces of data.
Regards, Italo
The text was updated successfully, but these errors were encountered: