From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: netfilter logging
Date: Wed, 08 Jun 2005 12:14:01 -0500 [thread overview]
Message-ID: <42A72759.7000906@gmx.co.uk> (raw)
In-Reply-To: <5885.212.100.225.55.1118237133.squirrel@webmail.*>
Jimmy wrote:
> I have just started to log my iptables drops. As seen with this line in my
> iptables-save output.
IMO a big mistake. Well, it's not so much a mistake as it is an
important exercise to show you how much useless logging netfilter can
produce. My firewalls now generally do very little logging, logging only
for specific purposes.
> -A INPUT -j LOG --log-level 1
> -A INPUT -j LOG --log-prefix "Dropped: "
Ouch!!
> What I would like to know is how I can get iptables to NOT log to console
> only to the message logs. Currently it goes into /var/log/syslog
First, understand that this is more a syslogd question than a netfilter
one. Second, understand what --log-level 1 is! Of course that logs to
console:
> Here is my syslog configuration. I cant see whats wrong with it.
(It's typical. You could have cut out the comments, BTW.)
> # /etc/syslog.conf
> [snip]
> # Emergency level messages go to all users:
> *.emerg *
From iptables(8):
--log-level level
Level of logging (numeric or see syslog.conf(5)).
The pointer is incorrect, at least for my Slackware: numeric levels are
listed in syslog(2), not in syslog.conf(5). If you meant debug, I think
that is "--log-level 8" (or just "--log-level debug").
Finally, and this IS your iptables issue: you have two LOG target lines,
thus the aforementioned "ouch". You're logging first with --log-level 1
and again with the --log-prefix "Dropped: ".
Delete all those log files. Have fun. :)
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next prev parent reply other threads:[~2005-06-08 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 13:25 netfilter logging Jimmy
2005-06-08 13:34 ` Vincent Lenouvel
2005-06-08 17:26 ` /dev/rob0
2005-06-08 15:52 ` Georgi Alexandrov
2005-06-08 17:14 ` /dev/rob0 [this message]
2005-06-10 18:02 ` Jason Opperisano
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=42A72759.7000906@gmx.co.uk \
--to=rob0@gmx.co.uk \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox