ipfw Logging Verbosity
- Reply: Dewayne Geraghty : "Re: ipfw Logging Verbosity"
- Reply: Michael Sierchio : "Re: ipfw Logging Verbosity"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Mon, 22 Sep 2025 01:08:41 UTC
Is there some middle ground between ipfw 'log' options between
silent and garden house.
I have a rule that looks like this:
deny ip from table(10) to any via ${INTERFACE}
Table 10 is biiiig - lots and lots of entries in it.
This results in nothing whatsoever being written to /var/log/security
when a table entry is rejected.
But, if I add the verb "log" to the above command, it writes a
continuous stream of rejected connection attempts matching one
of the table rules - presumably because these many entries are
still trying (which I why I blacklisted them in the first place).
Is there a way to get a more summarized view of the rejections
so that the logging isn't so noisy, but still capture a sense of
what is being stopped?
TIA