Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Chris Shepherd <chriss@whstuart.com>
To: "Randall J. Parr" <RParr@TemporalArts.COM>
Cc: netfilter@lists.netfilter.org
Subject: Re: how to configure iptables / syslog to log to separate file
Date: Wed,  8 Jan 2003 15:37:34 -0500	[thread overview]
Message-ID: <1042058254.3e1c8c0e93c83@mail.whstuart.com> (raw)
In-Reply-To: <3E1C89D7.7000706@TemporalArts.com>

Quoting "Randall J. Parr" <RParr@TemporalArts.COM>:

> Can I, and if so how can I, configure iptables (esp using GuardDog which
> I use to configure iptables) and/or syslog (ie /etc/syslog.conf, ...) so
> that my firewall messages are logged into a file other than
> /var/log/messages?
> 
> I have searched, looked at tutorial, etc. and found this question asked
> many times but without ever finding a decent answer.
> 
> If it just can not be done, could someone who knows this please state so?

Configure Syslog to log a certain log-level to an alternate file, and then just 
use  "-j LOG --log-level <level>". ie: if you wanted it to log as a notice, 
just setup Syslog to log notices to another file, and drop in a line that reads 
like:

iptables -A LOGGING_TABLE -j LOG --log-level notice --log-prefix="NF: "

I'm not too up on Syslog myself, so you should read the docs for that, but I do 
believe it is possible to log specific log-levels to an alternate file.

-- 
Chris Shepherd

-------------------------------------------------
This email may contain confidential information. Use of any such information
is strictly prohibited without express written consent of the sender




  reply	other threads:[~2003-01-08 20:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 20:28 how to configure iptables / syslog to log to separate file Randall J. Parr
2003-01-08 20:37 ` Chris Shepherd [this message]
2003-01-08 22:09   ` Athan

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=1042058254.3e1c8c0e93c83@mail.whstuart.com \
    --to=chriss@whstuart.com \
    --cc=RParr@TemporalArts.COM \
    --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