From: George Alexandru Dragoi <waruiinu@gmail.com>
To: Netfilter users list <netfilter@lists.netfilter.org>
Subject: Re: Tracing the passage of packets thru the various chains
Date: Sat, 6 Nov 2004 16:26:33 +0200 [thread overview]
Message-ID: <3063e504110606267f3b4981@mail.gmail.com> (raw)
In-Reply-To: <1099749214.2116.34.camel@localhost>
There is a patch in patch-o-matic which add a target called TRACE
http://www.netfilter.org/patch-o-matic/pom-extra.html#pom-extra-TRACE
On Sat, 06 Nov 2004 08:53:34 -0500, John A. Sullivan III
<jsullivan@opensourcedevelopmentcorp.com> wrote:
> On Sat, 2004-11-06 at 07:19, Taso Hatzi wrote:
>
>
> > The subject says what I want to do. Is there any way I can get a
> > stock kernel (Mdk 9.1 in this case) to show me what's going on?
> Yes, we do it all the time when trouble shooting in the ISCS network
> security management project (http://iscs.sourceforge.net). Simply use
> the LOG target. What the LOG rule should look like and where it should
> be placed depends on what you want to do but that's what we generally
> use to troubleshoot problems between wire in and wire out! Hope that
> sends you in the right direction - John
> --
> John A. Sullivan III
> Open Source Development Corporation
> Financially sustainable open source development
> http://www.opensourcedevel.com
>
>
--
Bla bla
next prev parent reply other threads:[~2004-11-06 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-06 12:19 Tracing the passage of packets thru the various chains Taso Hatzi
2004-11-06 13:53 ` John A. Sullivan III
2004-11-06 14:26 ` George Alexandru Dragoi [this message]
2004-11-06 15:18 ` For Mailers Mangesh Rakhunde
2004-11-06 16:53 ` Alistair Tonner
2004-11-06 18:18 ` unknown config key 'Repository:' Roger Villavicencio
2004-11-08 17:11 ` Roger Villavicencio
2004-11-07 17:50 ` For Mailers Leonardo Rodrigues Magalhães
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=3063e504110606267f3b4981@mail.gmail.com \
--to=waruiinu@gmail.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 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.