On Thu, Jun 06, 2024 at 10:04:49AM +0200, Marco Moock wrote:
Am 06.06.2024 um 10:39:25 Uhr schrieb Andrei Borzenkov:
Dropped packet information comes from the kernel, not from the firewalld. [...]
But firewalld has no influence on where these messages go.
What is the proper way to control the logging of the kernel/dmesg? dmesg is bad because that shows up on the virtual consoles by default and messes them up.
There is currently no way to log dropped packets to anything other than dmesg. This has been discussed many times. In the semi recent past we decided this should be done by depending on ulogd2. Firewalld will use a well known NFLOG group then ulogd2 can then send the log to syslog.
Issue: https://github.com/firewalld/firewalld/issues/1094#issuecomment-1468065266 stale draft PR: https://github.com/firewalld/firewalld/pull/1316