From: Rob Brewer <ipfire-devel@grantura.co.uk>
To: development@lists.ipfire.org
Subject: Logging Locationblock packets
Date: Sat, 09 Nov 2024 14:00:25 +0000 [thread overview]
Message-ID: <vgnptp$2pbe3$1@tuscan4.grantura.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1230 bytes --]
As a contributor to the SANS ISC, I email my IPTABLES logs hourly to
the
Dshield database, however the default IPFire IPTABLES logs are incomplete
since packets dropped by Locationblock are not logged to syslog.
As a workaround I edit the locationblock function of rules.pl to add a
IPTABLES rule to log the dropped packets. This edit does not of course
survive any Core-Updates that upgrade rules.pl and the edit needs to be
re-applied.
In addition, unless the Locationblock packets are logged to syslog the
data
displayed in the Firewall logs sections are incomplete as the packets
dropped by Location Block are not displayed.
I understand that the original intension of the Location Block feature
was
to reduce the amount of log messages on installations running on
extremely
cheap flash storage. I suspect that these installations are now almost
zero
especially since IPFire no longer supports 32 bit versions.
The obvious solution to this to make Location Block logging selectable as
a
firewall option and my quick look at making a patches for this would seem
to
be fairly simple task to rules.pl and and optionsfw.cgi.
I would be happy to provide the necessary patches should this be
acceptable.
next reply other threads:[~2024-11-09 14:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 14:00 Rob Brewer [this message]
2024-11-19 17:10 ` Michael Tremer
2024-11-20 13:36 ` Rob Brewer
2024-11-20 14:13 ` Adolf Belka
2024-11-20 15:21 ` Michael Tremer
2024-11-20 23:08 ` Rob Brewer
2024-11-22 15:36 ` Logging Locationblock packets [PATCH] Rob Brewer
2024-11-22 16:04 ` Rob Brewer
2024-11-23 9:26 ` Logging Locationblock packets Michael Tremer
2024-11-23 14:36 ` Rob Brewer
2024-11-23 14:47 ` Adolf Belka
2024-11-25 9:49 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='vgnptp$2pbe3$1@tuscan4.grantura.co.uk' \
--to=ipfire-devel@grantura.co.uk \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox