Red Hat Bugzilla – Bug 1147951
firewall-cmd should support a default logging option.
Last modified: 2016-11-03 17:00:24 EDT
In many cases, you want to log any connection that is not allowed through your firewall. firewall-cmd should have a built-in option for adding this capability. This should, by default, exclude multicast and other broadcast traffic but options should be included for enabling logging for such. Suggestion: firewall-cmd --log-dropped --zone <zone> [--log-broadcast] [--log-custom <port>]
Fixed upstream: https://github.com/t-woerner/firewalld/commit/5cb1ce169448d601b5b024ee4d31a77cf1808636
Fixed upstream: https://github.com/t-woerner/firewalld/commit/014d3345e7fb6436df94f0bad22c5166a4d0e157 New LogDenied support If LogDenied is enabled, logging rules right before reject and drop rules in the INPUT, FORWARD and OUTPUT chains for the default rules and also final reject and drop rules in zones. Possible values for LogDenied are: all, unicast, broadcast, multicast and off. Fixes issue #59
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune@redhat.com with any questions
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2016-2597.html