From: Robbie Dinn <robbie@microbus.com>
To: netfilter-devel@lists.netfilter.org
Subject: Re: Question, my modifed -j LOG
Date: Sun, 21 Aug 2005 15:16:47 +0100 [thread overview]
Message-ID: <43088CCF.6050401@microbus.com> (raw)
In-Reply-To: <20050820172824.GE5638@aaricia.csbnet.se>
Joakim Axelsson wrote:
> The --log-prefix is way to short only allowing 30 characters. I have a huge
> firewall with over 10000 rules (of couse not every packet using every rule).
> Its impossible to keep track on where the packet is unless i supply the
> table (filter,nat,mangle,raw) and the chain name in --log-prefix. Even if i
> try to keep this short there is very little, if no room, left for a reason
> to fit in --log-prefix. Simple solution for me is to modify -j LOG to handle
> a longer --log-prefix.
How about using an unmodified iptables --log-prefix , but instead of
using the long string with the full information in it, substitute
that string with it's (fixed length) hash. You could then postprocess
the logfiles to replace the hash with the original text.
i.e. change the problem from a kernel hacking exercise into a boring
scripting/text filtering exercise.
I suspect this isn't the answer you are looking for, but it might do
the job.
prev parent reply other threads:[~2005-08-21 14:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 17:28 Question, my modifed -j LOG Joakim Axelsson
2005-08-20 20:01 ` Jan Engelhardt
2005-08-20 20:25 ` Joakim Axelsson
2005-08-20 22:14 ` Joakim Axelsson
2005-08-20 22:38 ` Jan Engelhardt
2005-08-21 0:27 ` Carl-Daniel Hailfinger
2005-08-21 2:41 ` Peter Surda
2005-08-21 4:37 ` Joakim Axelsson
2005-08-21 8:36 ` Jan Engelhardt
2005-08-21 18:30 ` Carl-Daniel Hailfinger
2005-08-21 19:12 ` Joakim Axelsson
2005-08-21 14:16 ` Robbie Dinn [this message]
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=43088CCF.6050401@microbus.com \
--to=robbie@microbus.com \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.